lookback.com
Data from Aug 21, 2026, 6:44 PM UTC — 29m old.
11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 29m
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 | 5.59 s | — | — | 5.59 s | 5.59 s | |
| CLS Cumulative Layout Shift | 0.051 | — | — | 0.051 | 0.051 | |
| TBT Total Blocking Time | 291 ms | — | — | 291 ms | 291 ms | |
| FCP First Contentful Paint | 2.49 s | — | — | 2.49 s | 2.49 s | |
| Speed Index | 2.49 s | — | — | 2.49 s | 2.49 s | |
| TTFB Time to First Byte | 631 ms | — | — | 631 ms | 631 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.23 s | good | 76.2% good |
| CLS CWV | 0.050 | good | 82.2% good |
| FCP | 1.91 s | needs-improvement | 72.3% good |
| TTFB | 773 ms | good | 75.7% good |
Lab vs field
Lab LCP 5.59 s · field p75 2.23 s · real users are 0.4× 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.82 s | — | 0.040 | 2.05 s | 881 ms |
| 2026-08-08 | 2.76 s | — | 0.030 | 1.98 s | 773 ms |
| 2026-08-01 | 2.74 s | 103 ms | 0.030 | 1.98 s | 819 ms |
| 2026-07-25 | 2.60 s | — | 0.010 | 1.93 s | 881 ms |
| 2026-07-18 | 2.36 s | — | 0.050 | 1.71 s | 808 ms |
| 2026-07-11 | 2.12 s | — | 0.010 | 1.73 s | 808 ms |
| 2026-07-04 | 2.05 s | — | 0.010 | 1.65 s | 774 ms |
| 2026-06-27 | 2.21 s | — | 0.050 | 1.78 s | 807 ms |
| 2026-06-20 | 2.21 s | — | 0.010 | 1.87 s | 822 ms |
| 2026-06-13 | 2.44 s | — | 0.050 | 1.91 s | 981 ms |
| 2026-06-06 | 2.80 s | — | 0.060 | 2.02 s | 1.06 s |
| 2026-05-30 | 2.85 s | — | 0.080 | 2.13 s | 1.22 s |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 54.50 MB | — | — | 54.50 MB | 54.50 MB | |
| Requests | 93 | — | — | 93 | 93 | |
| Third-party Weight | 476.5 kB | — | — | 476.5 kB | 476.5 kB | |
| Third-party CPU | 145 ms | — | — | 145 ms | 145 ms | |
| Unused JS | 77.4 kB | — | — | 77.4 kB | 77.4 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 5 entities
476.5 kB transferred, 145 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 | 3.77 s | — | — | 3.77 s | 3.77 s | |
| Long Tasks | 11 | — | — | 11 | 11 | |
| DOM Elements | 578 | — | — | 578 | 578 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 21 | — | — | 21 | 21 | |
| A11y Failures | 3 | — | — | 3 | 3 | |
| A11y Failing Nodes | 12 | — | — | 12 | 12 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
21 violating nodes across 8 rules, 1021 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.
-
moderate
heading-order— Heading levels should only increase by one 7 nodes -
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 -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 2 nodes -
serious
aria-hidden-focus— ARIA hidden element must not be focusable or contain focusable elements 1 node -
moderate
landmark-main-is-top-level— Main landmark should not be contained in another landmark 1 node -
moderate
landmark-no-duplicate-main— Document should not have more than one main landmark 1 node -
serious
link-name— Links must have discernible text 1 node
Accessibility failures 3 of 32 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.
-
heading-order— Heading elements are not in a sequentially-descending order 7 nodes -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 4 nodes -
link-name— Links do not have a discernible name 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, 6:44 PM UTC | 70 | 5.59 s | 0.051 | 291 ms | 54.50 MB | 3/3 | ±14 | 2,348 | 93s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
lookback.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.lookback.com/"></speedlify-score>