# Track the speed of your pages

Your site measures the speed of its pages with your real visitors. This article explains the measures and their verdicts, then how to read them in the dashboard and in the **Web performance** tab of your statistics to find the page that slows your site down.

## Before you start

- Speed is measured in the browser of your real visitors, on their devices and their connections, on every page they load. You have nothing to install.
- Each number is a P75: three loads out of four were that fast or faster.
- The verdicts **Good**, **Needs improvement** and **Poor** follow the thresholds that Google publishes for its Core Web Vitals.

## Understand the measures

| Measure | Definition | Good | Needs improvement | Poor |
| --- | --- | --- | --- | --- |
| **LCP** | The time before the largest visible element is displayed, often the main image or heading. | 2.5 s or less | 4 s or less | Beyond |
| **INP** | How long the page takes to react to a click or a keystroke. | 200 ms or less | 500 ms or less | Beyond |
| **CLS** | The layout jumps during loading, as a unitless score. | 0.1 or less | 0.25 or less | Beyond |
| **FCP** | The time before the first display. | 1.8 s or less | 3 s or less | Beyond |
| **TTFB** | The time before the first byte of the page. | 800 ms or less | 1.8 s or less | Beyond |

LCP, INP and CLS are the three Core Web Vitals. The overall verdict is that of the worst of the three. Two labels describe the state of the measure.

| Note | Meaning |
| --- | --- |
| **Insufficient data** | The measure rests on too few loads to be judged. No verdict is shown. |
| **Partial** | The LCP or the CLS is still missing. The verdict rests on the other measures. |

**Note:** The INP needs the visitor to click or type. On a showcase site, it often stays at **Insufficient data** without this being a problem.

## Read the speed in the dashboard

On the card of each site, in the Lovely Render **Dashboard**, the **Web performance** line sums up the last 30 days. It gives the verdict, then the LCP, the INP and the CLS, each in the color of its verdict.

![A site’s card in the dashboard, with the Web performance line at the bottom: the verdict Good, LCP 1.62 s, INP 96 ms and CLS 0.040, then over 24 h the verdict Good, LCP 1.48 s, INP 88 ms and CLS 0.030.](https://static.lovelyrender.com/uploads/2026/10/246-hebergement-carte.png)

- The verdict of the line needs enough loads measured over the last days. Otherwise, the line shows **Insufficient data**.
- The label **24 h** followed by a verdict gives the last 24 hours, when they hold enough measures.
- The label **Stale** flags a measure that the site has not renewed for several hours.

Hovering the line opens the detail.

![The tooltip of the Web performance line: LCP, INP, CLS, FCP, TTFB and Origin, each with its value over the previous 30 days, then 6,912 page views measured, that is 15.7% of the total, then the date of the measure.](https://static.lovelyrender.com/uploads/2026/10/1026-doc-trouve-perf-bulle.png)

- Each measure, followed by its value over the 30 days before, for example **LCP 1.62 s (vs 1.71 s before)**. **Origin** is the time your server takes to produce the page.
- The number of page views measured and their share of the total.
- The date of the measure, after **Measured**.

## Read the Web performance tab

1. In the **Statistics** menu of the administration, open the **Web performance** tab.
2. Choose the period at the top of the screen. The filters of the screen apply, for example **Screen format** or **Country**.
3. Read the three cards **Core Web Vitals**, **Loading** and **Pages**.

Each card gives the **P75** of each measure and its **Loads**, the number of loads measured that the figure rests on. In this tab, a measure has its verdict when enough loads were measured over the period.

### Core Web Vitals

The overall verdict shows next to the title. Each line carries its verdict, a bar filled with the share of loads judged good and an arrow showing the change against the previous period. A green arrow pointing down flags a time going down.

![The Core Web Vitals card, verdict Good: LCP 1.59 s, INP 111 ms and CLS 0.031, all going down and judged good, with their measured loads.](https://static.lovelyrender.com/uploads/2026/10/173-stats-vitesse.png)

Hovering a bar gives the share of good, needs improvement and poor loads.

### Loading

The card gives the TTFB and the FCP with their verdict, then the browser stages: **DOM interactive**, **DOMContentLoaded** and **Loading**. The **Server response** is the time your site takes to produce the page, before the trip over the network. Google publishes no threshold for these last four: they have no verdict.

![The Loading card: TTFB 183 ms and FCP 917 ms judged good, DOM interactive 1.14 s, DOMContentLoaded 1.17 s, Loading 1.72 s and Server response 68 ms, each with its measured loads.](https://static.lovelyrender.com/uploads/2026/10/1022-doc-trouve-chargement.png)

### Pages

The card lists your pages, the most viewed first, with their **Views**, their LCP, their INP and their CLS. A value takes the color of its verdict when the page has enough loads measured. A page under this threshold is grayed out.

![The first lines of the Pages card: the home page, /tarifs/, /fonctionnalites/ and the following pages, each with its views, its LCP, its INP and its CLS judged good.](https://static.lovelyrender.com/uploads/2026/10/1024-doc-trouve-perf-pages.png)

Hovering a line gives its views, its measured loads, the dominant device, the time spent and the scroll. Clicking a page opens its detail, where the **Web performance** card repeats its measures in two views, **Core Web Vitals** and **Loading**.

## Find the page that slows your site down

1. In the **Web performance** tab, open **Add a filter** and choose the value **Mobile** under **Screen format**.
2. Read the **Pages** card. Spot the most viewed page whose LCP is **Needs improvement** or **Poor**.
3. Open this page in the editor and lighten what shows first, most often a header image that is too heavy.
4. Publish the site, then follow the change arrow over the next period.

## Understand the limits of the measure

- The measure comes from the browser. A script blocker, an old browser or a visitor who objects to audience measurement report nothing. The page view count, for its part, stays complete.
- The measure adds no cookie and no request. It leaves with the signal that measures the time spent.
- Under a **Channel** or **Entry page** filter, the change arrows disappear: the previous period does not compare the same visitors.

**Note:** A test tool such as PageSpeed loads your page once, from a server, with a simulated connection. The **Web performance** tab measures your real visitors and keeps the P75, as Google does for its ranking. The two figures differ. The test tool helps to understand why a page is slow.

## See also

- [Read your analytics](https://lovelyrender.com/documentation/read-analytics/)
- [Read your dashboard](https://lovelyrender.com/documentation/read-dashboard/)
- [Upload your photos and videos](https://lovelyrender.com/documentation/upload-photos-videos/)