cloudflare.com/products/pages
https://www.cloudflare.com/products/pages
Data from Aug 23, 2026, 9:26 AM UTC 13h old
Web Hosts #3 · 4 measurements · since Aug 21, 2026
https://www.cloudflare.com/products/pages/.
A trailing slash only, so both forms are treated as one site rather than two — one history, measured once. Lighthouse follows the redirect, so the numbers below describe the canonical page; the only cost is an extra hop on each run.
https://pages.cloudflare.com/.
History from the previous URL is included below, with the move on Aug 23, 2026. A step-change around that point is likely the change of address rather than a regression.
Lighthouse benchmark index was 2022.5 against a baseline of 3031.5 (-33.300000000000004%). CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.
Core Web Vitals field data, origin-level
Real Chrome users, 28-day window (2026-07-25 → 2026-08-21). This is what Google measures you on.
Scores
Filmstrip Lighthouse, mobile
How the page drew during the measured load, at 8 points across 3.00 s.
-
375 ms
-
750 ms
-
1.13 s
-
1.50 s
-
1.88 s
-
2.25 s
-
2.63 s
-
3.00 s
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 3.56 s | 5.14 s | ↓ -1583 ms (-30.8%) significant | 3.56 s | 5.82 s | |
| CLS Cumulative Layout Shift | 0 | 0 | → no change | 0 | 0 | |
| TBT Total Blocking Time | 1.17 s | 537 ms | ↑ +631 ms (+117.5%) | 288 ms | 1.17 s | |
| FCP First Contentful Paint | 2.95 s | 4.13 s | ↓ -1178 ms (-28.5%) significant | 2.95 s | 4.13 s | |
| Speed Index | 3.71 s | 4.21 s | ↓ -499 ms (-11.9%) | 3.50 s | 4.21 s | |
| TTFB Time to First Byte | 475 ms | 625 ms | ↓ -150 ms (-24%) | 475 ms | 643 ms |
What LCP is made of observed, unthrottled
A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.
Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 3.56 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.
Field data Chrome UX Report, origin-level
Real Chrome users, 28-day trailing window (2026-07-25 → 2026-08-21). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 1.80 s | good | 86% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 184 ms | good | 77.2% good |
| CLS CWV | 0 | good | 98.4% good |
| FCP | 1.48 s | good | 82.1% good |
| TTFB | 609 ms | good | 82.3% good |
Lab vs field
Lab LCP 3.56 s · field p75 1.80 s · real users are 0.51× faster than the lab.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 3.95 MB | 4.11 MB | ↓ -152.4 kB (-3.8%) | 3.95 MB | 4.11 MB | |
| Requests | 173 | 153 | ↑ +20 (+13.1%) significant | 148 | 173 | |
| Third-party Weight | 92.9 kB | 249 kB | ↓ -152.7 kB (-62.7%) significant | 92.9 kB | 249 kB | |
| Third-party CPU | 64 ms | 50 ms | ↑ +13 ms (+26.6%) | 35 ms | 64 ms | |
| Unused JS | 930 kB | 1.03 MB | ↓ -100.6 kB (-10%) significant | 930 kB | 1.03 MB | |
| Unused CSS | 0 B | 0 B | → no change | 0 B | 0 B |
By resource type
Third parties 12 entities
92.9 kB transferred, 64 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 32.14 s | 26.23 s | ↑ +5903 ms (+22.5%) | 18.13 s | 32.14 s | |
| Long Tasks | 20 | 17 | ↑ +3 (+17.6%) | 10 | 20 | |
| DOM Elements | 2,015 | 2,013 | ↑ +2 (+0.1%) | 2,013 | 2,015 | |
| A11y Failures | 3 | 3 | → no change | 3 | 3 | |
| A11y Failing Nodes | 17 | 17 | → no change | 17 | 17 |
Main thread work
Axe violations axe-core , full rule set
The axe run failed: Navigation timeout of 120000 ms exceeded
Accessibility failures 3 of 26 audits
Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.
-
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 15 nodes -
heading-order— Heading elements are not in a sequentially-descending order 1 node -
label-content-name-mismatch— Elements with visible text labels do not have matching accessible names. 1 node
Hygiene
Changes rarely — which is exactly why a change is worth noticing.
Measurement log
Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.
| When | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 23, 2026, 9:26 AM UTC | 60 | 3.56 s | 0 | 1.17 s | 3.95 MB | 3/3 | ±13 | 2,023 | 290.5s |
| Aug 23, 2026, 7:32 AM UTC old URL | 57 | 5.14 s | 0 | 537 ms | 4.11 MB | 3/3 | ±24 | 3,032 | 338s |
| Aug 22, 2026, 6:39 AM UTC old URL | 52 | 5.82 s | 0 | 755 ms | 4.09 MB | 3/3 | ±4 | 2,489 | 290.4s |
| Aug 21, 2026, 5:40 AM UTC old URL | 68 | 4.86 s | 0 | 288 ms | 4.10 MB | 3/3 | ±30 | 3,608 | 227.3s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
cloudflare.com/products/pages's scores, updated whenever this instance
re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!
<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.cloudflare.com/products/pages"></speedlify2-score>