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 ·

cfam.es

https://cfam.es/

90 69 100 100 ✗CWV 19AXE

Data from Aug 20, 2026, 4:29 PM UTC — 26h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 26h

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 Built with Eleventy
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

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

LCP 3.59 s needs-improvement
INP 105 ms good
CLS 0 good

Scores

90
Performance
no change
69
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.12 s — — 3.12 s 3.12 s
CLS Cumulative Layout Shift 0.046 — — 0.046 0.046
TBT Total Blocking Time 57 ms — — 57 ms 57 ms
FCP First Contentful Paint 2.07 s — — 2.07 s 2.07 s
Speed Index 3.71 s — — 3.71 s 3.71 s
TTFB Time to First Byte 1.51 s — — 1.51 s 1.51 s

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.

time to first byte 1.51 s
element render delay 389 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 3.59 s needs-improvement 54.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 105 ms good 91.5% good
CLS CWV 0 good 98.2% good
FCP 3.65 s poor 46.1% good
TTFB 2.93 s poor 33.8% good

Lab vs field

Lab LCP 3.12 s · field p75 3.59 s · real users are 1.15× slower 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 3.56 s 96 ms 0 3.58 s 2.92 s
2026-08-08 3.53 s 105 ms 0 3.54 s 2.88 s
2026-08-01 3.54 s 119 ms 0 3.54 s 2.84 s
2026-07-25 3.55 s — 0 3.55 s 2.84 s
2026-07-18 — — — — —
2026-07-11 — — — — —
2026-07-04 — — — — —
2026-06-27 — — — — —
2026-06-20 3.62 s — 0 3.59 s 2.89 s
2026-06-13 3.62 s — 0 3.62 s 2.94 s
2026-06-06 3.62 s 111 ms 0 3.62 s 3.03 s
2026-05-30 3.61 s 106 ms 0 3.62 s 3.03 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.45 MB — — 4.45 MB 4.45 MB
Requests 38 — — 38 38
Third-party Weight 238.9 kB — — 238.9 kB 238.9 kB
Third-party CPU 55 ms — — 55 ms 55 ms
Unused JS 92.9 kB — — 92.9 kB 92.9 kB
Unused CSS 18.3 kB — — 18.3 kB 18.3 kB

By resource type

image 4.04 MB · 23 req
script 225.9 kB · 4 req
font 141.6 kB · 3 req
stylesheet 31.3 kB · 4 req
document 4.7 kB · 1 req
other 3.2 kB · 3 req
third party 238.9 kB · 6 req

Third parties 4 entities

238.9 kB transferred, 55 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Tag Manager 172.1 kB · 55 ms CPU
Google Fonts 65.5 kB · 0 ms CPU
WordPress 697 B · 0 ms CPU
Google Analytics 543 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.08 s — — 1.08 s 1.08 s
Long Tasks 4 — — 4 4
DOM Elements 263 — — 263 263
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 19 — — 19 19
A11y Failures 6 — — 6 6
A11y Failing Nodes 14 — — 14 14

Main thread work

other 539 ms
script evaluation 269 ms
style layout 125 ms
script parse compile 62 ms
paint composite render 59 ms
parse HTML 28 ms

Axe violations axe-core 4.13.0, full rule set

19 violating nodes across 7 rules, 575 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 link-name — Links must have discernible text 7 nodes
  • moderate region — All page content should be contained by landmarks 5 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
  • moderate heading-order — Heading levels should only increase by one 2 nodes
  • critical button-name — Buttons must have discernible text 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node

Accessibility failures 6 of 19 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.

  • link-name — Links do not have a discernible name 7 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 2 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 2 nodes
  • button-name — Buttons do not have an accessible name 1 node
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 1 node
  • 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 h2

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 20, 2026, 4:29 PM UTC 90 3.12 s 0.046 57 ms 4.45 MB 3/3 ±33 3,205 28.2s

Embed this score

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