cloudflare.com
Data from Aug 23, 2026, 12:38 PM UTC 9h old
Web Hosts #15 · 3 measurements · since Aug 21, 2026
Core Web Vitals field data, url-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.36 s | 4.15 s | ↓ -787 ms (-19%) | 3.06 s | 4.15 s | |
| CLS Cumulative Layout Shift | 0 | 0 | → no change | 0 | 0 | |
| TBT Total Blocking Time | 1.10 s | 953 ms | ↑ +147 ms (+15.4%) significant | 953 ms | 1.10 s | |
| FCP First Contentful Paint | 2.75 s | 2.78 s | ↓ -34 ms (-1.2%) | 2.69 s | 2.78 s | |
| Speed Index | 3.57 s | 2.78 s | ↑ +787 ms (+28.3%) significant | 2.69 s | 3.57 s | |
| TTFB Time to First Byte | 494 ms | 470 ms | ↑ +24 ms (+5.1%) | 470 ms | 494 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.36 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, url-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 | 2.48 s | good | 75.1% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 278 ms | needs-improvement | 65.5% good |
| CLS CWV | 0 | good | 96.9% good |
| FCP | 1.88 s | needs-improvement | 73.3% good |
| TTFB | 525 ms | good | 83.3% good |
Lab vs field
Lab LCP 3.36 s · field p75 2.48 s · real users are 0.74× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 2026-08-15 | 2.47 s | 274 ms | 0 | 1.88 s | 520 ms |
| 2026-08-08 | 2.48 s | 270 ms | 0 | 1.89 s | 520 ms |
| 2026-08-01 | 2.49 s | 265 ms | 0 | 1.90 s | 534 ms |
| 2026-07-25 | 2.50 s | 264 ms | 0 | 1.91 s | 643 ms |
| 2026-07-18 | 2.50 s | 262 ms | 0 | 1.90 s | 720 ms |
| 2026-07-11 | 2.57 s | 261 ms | 0 | 1.89 s | 779 ms |
| 2026-07-04 | 2.65 s | 263 ms | 0 | 1.93 s | 816 ms |
| 2026-06-27 | 2.79 s | 266 ms | 0 | 1.99 s | 826 ms |
| 2026-06-20 | 2.90 s | 269 ms | 0 | 2.06 s | 847 ms |
| 2026-06-13 | 2.93 s | 274 ms | 0 | 2.10 s | 847 ms |
| 2026-06-06 | 2.95 s | 294 ms | 0 | 2.12 s | 864 ms |
| 2026-05-30 | 2.92 s | 343 ms | 0 | 2.16 s | 858 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 2.55 MB | 2.60 MB | ↓ -48.3 kB (-1.9%) | 2.55 MB | 2.60 MB | |
| Requests | 175 | 160 | ↑ +15 (+9.4%) | 160 | 175 | |
| Third-party Weight | 248 kB | 311 kB | ↓ -61.0 kB (-20.1%) | 248 kB | 311 kB | |
| Third-party CPU | 88 ms | 79 ms | ↑ +9 ms (+11.2%) | 65 ms | 88 ms | |
| Unused JS | 894 kB | 962 kB | ↓ -67.2 kB (-7.1%) | 894 kB | 962 kB | |
| Unused CSS | 0 B | 0 B | → no change | 0 B | 0 B |
By resource type
Third parties 12 entities
248 kB transferred, 88 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 | 50.06 s | 8.79 s | ↑ +41277 ms (+469.7%) | 8.79 s | 50.06 s | |
| Long Tasks | 20 | 20 | → no change | 20 | 20 | |
| DOM Elements | 3,003 | 2,986 | ↑ +17 (+0.6%) | 2,986 | 3,003 | |
| A11y Failures | 1 | 1 | → no change | 1 | 1 | |
| A11y Failing Nodes | 8 | 8 | → no change | 8 | 8 |
Main thread work
Axe violations axe-core , full rule set
The axe run failed: Navigation timeout of 120000 ms exceeded
Accessibility failures 1 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. 8 nodes
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, 12:38 PM UTC | 63 | 3.36 s | 0 | 1.10 s | 2.55 MB | 3/3 | ±14 | 2,453 | 374.4s |
| Aug 22, 2026, 12:36 PM UTC | 61 | 4.15 s | 0 | 953 ms | 2.60 MB | 3/3 | ±13 | 2,420 | 306.1s |
| Aug 21, 2026, 11:31 AM UTC | 68 | 3.06 s | 0 | 975 ms | 2.55 MB | 3/3 | ±4 | 2,467 | 309.6s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
cloudflare.com'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/"></speedlify2-score>