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 ·

antithesis.com

https://antithesis.com/

54 96 58 92 ✓CWV 16AXE

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

11ty Emeritus · 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.

Astro 6.4.0 Built with Astro 6.4.0
Amazon S3 Hosted by Amazon S3

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 1.49 s good
INP 140 ms good
CLS 0 good

Scores

54
Performance
no change
96
Accessibility
no change
58
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.86 s — — 5.86 s 5.86 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 1.16 s — — 1.16 s 1.16 s
FCP First Contentful Paint 1.45 s — — 1.45 s 1.45 s
Speed Index 1.45 s — — 1.45 s 1.45 s
TTFB Time to First Byte 613 ms — — 613 ms 613 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 40 ms
resource load delay 17 ms
time to first byte 6 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 1.49 s good 91.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 140 ms good 90% good
CLS CWV 0 good 99.9% good
FCP 1.42 s good 84.9% good
TTFB 721 ms good 78.4% good

Lab vs field

Lab LCP 5.86 s · field p75 1.49 s · real users are 0.25× 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.49 s 141 ms 0 1.41 s 686 ms
2026-08-08 1.60 s 145 ms 0 1.43 s 719 ms
2026-08-01 1.55 s 143 ms 0 1.43 s 686 ms
2026-07-25 1.63 s 138 ms 0 1.36 s 672 ms
2026-07-18 1.80 s 137 ms 0 1.21 s 558 ms
2026-07-11 2.17 s 131 ms 0 1.13 s 438 ms
2026-07-04 2.42 s 132 ms 0 1.13 s 454 ms
2026-06-27 2.49 s 131 ms 0 1.14 s 388 ms
2026-06-20 2.41 s 131 ms 0 1.09 s 367 ms
2026-06-13 2.41 s 131 ms 0 1.18 s 415 ms
2026-06-06 2.49 s 132 ms 0 1.19 s 370 ms
2026-05-30 2.41 s 129 ms 0 1.22 s 434 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.09 MB — — 2.09 MB 2.09 MB
Requests 96 — — 96 96
Third-party Weight 959.1 kB — — 959.1 kB 959.1 kB
Third-party CPU 380 ms — — 380 ms 380 ms
Unused JS 388.5 kB — — 388.5 kB 388.5 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 1.13 MB · 41 req
font 782.6 kB · 9 req
document 65.5 kB · 1 req
image 36.6 kB · 13 req
stylesheet 28.3 kB · 8 req
other 11.9 kB · 18 req
third party 959.1 kB · 45 req

Third parties 14 entities

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

Google Tag Manager 339.3 kB · 130 ms CPU
Facebook 251.5 kB · 127 ms CPU
posthog.com 129.2 kB · 51 ms CPU
Usercentrics CMP 118.9 kB · 23 ms CPU
reo.dev 54.6 kB · 22 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.28 s — — 3.28 s 3.28 s
Long Tasks 14 — — 14 14
DOM Elements 1,244 — — 1,244 1,244
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 16 — — 16 16
A11y Failures 1 — — 1 1
A11y Failing Nodes 3 — — 3 3

Main thread work

script evaluation 1.97 s
other 593 ms
script parse compile 347 ms
style layout 174 ms
parse HTML 103 ms
garbage collection 45 ms
paint composite render 42 ms

Axe violations axe-core 4.13.0, full rule set

16 violating nodes across 6 rules, 1394 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 5 nodes
  • serious listitem — <li> elements must be contained in a <ul> or <ol> 4 nodes
  • serious aria-hidden-focus — ARIA hidden element must not be focusable or contain focusable elements 3 nodes
  • moderate region — All page content should be contained by landmarks 2 nodes
  • serious link-name — Links must have discernible text 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

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

  • aria-hidden-focus — `[aria-hidden="true"]` elements contain focusable descendents 3 nodes

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:27 PM UTC 54 5.86 s 0 1.16 s 2.09 MB 3/3 ±6 2,478 37.6s

Embed this score

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