---
title: "Frontend Observability: Is it right for you | Grafana Labs"
description: "Decide whether Frontend Observability fits your user experience and consolidation goals."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## Is it right for you?

Frontend Observability meets your needs when you:

- Are already using Grafana Cloud for backend observability and the frontend is a blind spot
- Have backend dashboards that look healthy but users are still reporting slow pages or broken flows, with no way to see what they’re actually experiencing
- Have frontend issues that only surface in production. They don’t reproduce in staging, and they vary by browser, device, geography, or network condition.
- Are paying for a separate RUM tool and want to consolidate to one platform, one login
- Want frontend instrumentation built on open standards, not a proprietary agent that only works with one vendor’s backend

## Real results from real teams

- [**River Island**](/success/riverisland/)
  
  > “Just before Easter, we noticed a small increase — around 3% to 5% — in page load times in the basket. At the same time, we saw order value starting to drop. We investigated and found a backend process causing additional load on the front end. It was a bug. We were able to fix it and deploy a change within 30 minutes.”