speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

theo-courant.com

https://theo-courant.com/

74 97 96 100 ✓CWV 45AXE

Data from Aug 21, 2026, 9:40 AM UTC — 9h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 9h

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.

Eleventy 2.0.1 Built with Eleventy 2.0.1
Cloudflare Hosted by Cloudflare

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 1.62 s good
INP 79 ms good
CLS 0 good

Scores

74
Performance
no change
97
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 7.86 s — — 7.86 s 7.86 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.03 s — — 2.03 s 2.03 s
Speed Index 2.03 s — — 2.03 s 2.03 s
TTFB Time to First Byte 475 ms — — 475 ms 475 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.

element render delay 87 ms
resource load duration 56 ms
time to first byte 37 ms
resource load delay 11 ms

Field data Chrome UX Report, origin-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 1.62 s good 89.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 79 ms good 95.6% good
CLS CWV 0 good 99.4% good
FCP 1.26 s good 87.6% good
TTFB 646 ms good 82.6% good

Lab vs field

Lab LCP 7.86 s · field p75 1.62 s · real users are 0.21× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.63 s 75 ms 0 1.26 s 644 ms
2026-08-08 1.59 s 73 ms 0 1.23 s 627 ms
2026-08-01 1.56 s 69 ms 0 1.18 s 606 ms
2026-07-25 1.52 s 69 ms 0 1.16 s 586 ms
2026-07-18 1.52 s 69 ms 0 1.15 s 578 ms
2026-07-11 1.51 s 69 ms 0 1.14 s 570 ms
2026-07-04 1.55 s 72 ms 0 1.18 s 584 ms
2026-06-27 1.53 s 75 ms 0 1.20 s 575 ms
2026-06-20 1.52 s 76 ms 0 1.21 s 573 ms
2026-06-13 1.54 s 75 ms 0 1.23 s 581 ms
2026-06-06 1.52 s 77 ms 0 1.20 s 576 ms
2026-05-30 1.54 s 73 ms 0 1.19 s 593 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.91 MB — — 1.91 MB 1.91 MB
Requests 53 — — 53 53
Third-party Weight 1.66 MB — — 1.66 MB 1.66 MB
Third-party CPU 11 ms — — 11 ms 11 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 1.78 MB · 38 req
font 71.2 kB · 3 req
script 26.1 kB · 5 req
stylesheet 12.6 kB · 2 req
document 8.6 kB · 1 req
other 3.5 kB · 3 req
third party 1.66 MB · 34 req

Third parties 7 entities

1.66 MB transferred, 11 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

wsrv.nl 1.13 MB · 0 ms CPU
Cloudinary 502.0 kB · 0 ms CPU
Cloudflare 11.5 kB · 3 ms CPU
zgo.at 4.4 kB · 2 ms CPU
Cloudflare CDN 4.2 kB · 1 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 685 ms — — 685 ms 685 ms
Long Tasks 1 — — 1 1
DOM Elements 279 — — 279 279
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 45 — — 45 45
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

other 350 ms
style layout 150 ms
script evaluation 112 ms
paint composite render 46 ms
parse HTML 24 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

45 violating nodes across 6 rules, 436 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 region — All page content should be contained by landmarks 29 nodes
  • minor image-redundant-alt — Alternative text of images should not be repeated as text 12 nodes
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 1 of 15 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.

  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3 1 console error

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 PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 21, 2026, 9:40 AM UTC 74 7.86 s 0 0 ms 1.91 MB 3/3 ±4 2,389 27.6s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show theo-courant.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://theo-courant.com/"></speedlify-score>