fastly.com
Data from Aug 21, 2026, 10:30 AM UTC — 8h old.
Web Hosts · 1 measurement · since Aug 21, 2026 · last attempt 8h
Stack
Detected on the same page load as the accessibility pass — the generator
from <meta name="generator"> or the shape of the page,
the host from response headers.
Core Web Vitals field data, url-level
Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 12.03 s | — | — | 12.03 s | 12.03 s | |
| CLS Cumulative Layout Shift | 0.055 | — | — | 0.055 | 0.055 | |
| TBT Total Blocking Time | 1.34 s | — | — | 1.34 s | 1.34 s | |
| FCP First Contentful Paint | 3.46 s | — | — | 3.46 s | 3.46 s | |
| Speed Index | 3.99 s | — | — | 3.99 s | 3.99 s | |
| TTFB Time to First Byte | 605 ms | — | — | 605 ms | 605 ms |
What LCP is made of
A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.
Field data Chrome UX Report, url-level
Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 2.95 s | needs-improvement | 66.3% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 290 ms | needs-improvement | 62.5% good |
| CLS CWV | 0.060 | good | 94.3% good |
| FCP | 2.44 s | needs-improvement | 52.6% good |
| TTFB | 787 ms | good | 75.2% good |
Lab vs field
Lab LCP 12.03 s · field p75 2.95 s · real users are 0.24× 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.84 s | 287 ms | 0.060 | 2.40 s | 763 ms |
| 2026-08-08 | 2.88 s | 290 ms | 0.060 | 2.42 s | 777 ms |
| 2026-08-01 | 2.85 s | 288 ms | 0.060 | 2.40 s | 747 ms |
| 2026-07-25 | 3.03 s | 286 ms | 0.050 | 2.63 s | 913 ms |
| 2026-07-18 | 3.39 s | 286 ms | 0.040 | 2.92 s | 1.05 s |
| 2026-07-11 | 3.54 s | 281 ms | 0.030 | 2.98 s | 1.07 s |
| 2026-07-04 | 3.54 s | 280 ms | 0.040 | 2.98 s | 1.10 s |
| 2026-06-27 | 3.50 s | 288 ms | 0.050 | 2.99 s | 1.13 s |
| 2026-06-20 | 3.45 s | 292 ms | 0.060 | 2.94 s | 1.17 s |
| 2026-06-13 | 3.40 s | 293 ms | 0.060 | 2.87 s | 1.16 s |
| 2026-06-06 | 3.44 s | 290 ms | 0.060 | 2.85 s | 1.12 s |
| 2026-05-30 | 3.18 s | 270 ms | 0.060 | 2.61 s | 860 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 3.07 MB | — | — | 3.07 MB | 3.07 MB | |
| Requests | 139 | — | — | 139 | 139 | |
| Third-party Weight | 707.5 kB | — | — | 707.5 kB | 707.5 kB | |
| Third-party CPU | 406 ms | — | — | 406 ms | 406 ms | |
| Unused JS | 550.0 kB | — | — | 550.0 kB | 550.0 kB | |
| Unused CSS | 75.5 kB | — | — | 75.5 kB | 75.5 kB |
By resource type
Third parties 24 entities
707.5 kB transferred, 406 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 | 5.85 s | — | — | 5.85 s | 5.85 s | |
| Long Tasks | 20 | — | — | 20 | 20 | |
| DOM Elements | 1,193 | — | — | 1,193 | 1,193 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 14 | — | — | 14 | 14 | |
| A11y Failures | 5 | — | — | 5 | 5 | |
| A11y Failing Nodes | 13 | — | — | 13 | 13 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
14 violating nodes across 7 rules, 1525 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.
-
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 4 nodes -
moderate
region— All page content should be contained by landmarks 4 nodes -
critical
button-name— Buttons must have discernible text 2 nodes -
moderate
heading-order— Heading levels should only increase by one 1 node -
serious
link-name— Links must have discernible text 1 node -
serious
nested-interactive— Interactive controls must not be nested 1 node -
serious
svg-img-alt— <svg> elements with an img or image role must have alternative text 1 node
Accessibility failures 5 of 33 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.
-
button-name— Buttons do not have an accessible name 6 nodes -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 4 nodes -
heading-order— Heading elements are not in a sequentially-descending order 1 node -
link-name— Links do not have a discernible name 1 node -
svg-img-alt— SVG elements with an `img` role do not have an accessible text alternative 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 21, 2026, 10:30 AM UTC | 41 | 12.03 s | 0.055 | 1.34 s | 3.07 MB | 3/3 | ±10 | 2,986 | 48.5s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
fastly.com's scores, updated whenever this instance
re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site!
<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://www.fastly.com/"></speedlify-score>