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 ·

thegymnasium.com

https://thegymnasium.com/

100 100 100 100 ✓CWV 1AXE

Data from Aug 21, 2026, 7:49 AM UTC — 11h old.

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

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

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.46 s good
INP — no data
CLS 0 good

Scores

100
Performance
no change
100
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 1.38 s — — 1.38 s 1.38 s
CLS Cumulative Layout Shift 0.021 — — 0.021 0.021
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.08 s — — 1.08 s 1.08 s
Speed Index 1.08 s — — 1.08 s 1.08 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.

time to first byte 220 ms
element render delay 84 ms
resource load duration 14 ms
resource load delay 8 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.46 s good 91.6% good
CLS CWV 0 good 91.5% good
FCP 1.45 s good 86.5% good
TTFB 868 ms needs-improvement 67.2% good

Lab vs field

Lab LCP 1.38 s · field p75 1.46 s · real users are 1.06× 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 1.37 s — 0 1.37 s 858 ms
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 1.11 s — 0 1.12 s 782 ms
2026-07-18 — — — — —
2026-07-11 1.48 s — 0 1.48 s 899 ms
2026-07-04 1.63 s — 0 1.53 s 1.01 s
2026-06-27 1.61 s — 0 1.52 s 1.05 s
2026-06-20 1.64 s — 0 1.52 s 1.06 s
2026-06-13 1.62 s — 0 1.47 s 1.05 s
2026-06-06 1.49 s — 0 1.42 s 1.03 s
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 269.7 kB — — 269.7 kB 269.7 kB
Requests 32 — — 32 32
Third-party Weight 17.5 kB — — 17.5 kB 17.5 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 116.5 kB · 3 req
image 104.7 kB · 21 req
other 18.5 kB · 3 req
stylesheet 10.9 kB · 2 req
document 5.7 kB · 1 req
script 4.5 kB · 1 req
third party 17.5 kB · 1 req

Third parties 1 entities

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

WP Engine 17.5 kB · 0 ms CPU

Page health

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

Main thread work

other 347 ms
paint composite render 235 ms
style layout 211 ms
script evaluation 26 ms
parse HTML 15 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 928 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 landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

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

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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 21, 2026, 7:49 AM UTC 100 1.38 s 0.021 0 ms 269.7 kB 3/3 ±1 2,900 28s

Embed this score

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