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 ·

classic-mahjong.com

https://classic-mahjong.com/

50 100 77 100 CWV 3AXE

Data from Aug 20, 2026, 8:28 PM UTC — 22h old.

11ty Emeritus · 1 measurement · since Aug 20, 2026 · last attempt 22h

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 5.17.1 Built with Astro 5.17.1
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.97 s good
INP 120 ms good
CLS 0 good

Scores

50
Performance
no change
100
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.50 s 4.50 s 4.50 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 3.69 s 3.69 s 3.69 s
FCP First Contentful Paint 2.10 s 2.10 s 2.10 s
Speed Index 4.68 s 4.68 s 4.68 s
TTFB Time to First Byte 605 ms 605 ms 605 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 207 ms
time to first byte 5 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.97 s good 83.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 120 ms good 89.7% good
CLS CWV 0 good 99.7% good
FCP 1.16 s good 87.6% good
TTFB 502 ms good 87% good

Lab vs field

Lab LCP 4.50 s · field p75 1.97 s · real users are 0.44× 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.96 s 120 ms 0 1.17 s 507 ms
2026-08-08 2.01 s 120 ms 0 1.22 s 524 ms
2026-08-01 2.06 s 119 ms 0 1.27 s 536 ms
2026-07-25 2.02 s 115 ms 0 1.24 s 520 ms
2026-07-18 2.03 s 114 ms 0 1.23 s 517 ms
2026-07-11 2.02 s 116 ms 0 1.20 s 501 ms
2026-07-04 2.00 s 117 ms 0 1.18 s 491 ms
2026-06-27 2.00 s 117 ms 0 1.18 s 491 ms
2026-06-20 2.02 s 119 ms 0 1.19 s 487 ms
2026-06-13 2.02 s 120 ms 0 1.18 s 478 ms
2026-06-06 2.05 s 123 ms 0 1.19 s 479 ms
2026-05-30 2.07 s 124 ms 0 1.21 s 480 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.89 MB 2.89 MB 2.89 MB
Requests 128 128 128
Third-party Weight 2.01 MB 2.01 MB 2.01 MB
Third-party CPU 646 ms 646 ms 646 ms
Unused JS 992.2 kB 992.2 kB 992.2 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 2.09 MB · 43 req
image 334.1 kB · 17 req
other 268.6 kB · 45 req
font 171.5 kB · 7 req
stylesheet 21.6 kB · 7 req
document 7.4 kB · 3 req
third party 2.03 MB · 99 req

Third parties 22 entities

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

Google Tag Manager 475.9 kB · 160 ms CPU
intergient.com 438.7 kB · 154 ms CPU
Google/Doubleclick Ads 269.0 kB · 58 ms CPU
Facebook 173.2 kB · 94 ms CPU
Amazon Ads 103.1 kB · 62 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 7.11 s 7.11 s 7.11 s
Long Tasks 20 20 20
DOM Elements 442 442 442
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 3 3 3
A11y Failures 0 0 0
A11y Failing Nodes 0 0 0

Main thread work

script evaluation 3.45 s
other 2.64 s
script parse compile 573 ms
style layout 229 ms
garbage collection 107 ms
paint composite render 59 ms
parse HTML 58 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 605 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 2 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 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, 8:28 PM UTC 50 4.50 s 0 3.69 s 2.89 MB 3/3 ±6 2,492 48s

Embed this score

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