speedlify2

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

Measurement runs · Embed a score ·

oldpersiangames.org

https://oldpersiangames.org/

97 95 96 92 6AXE CWV

Data from Aug 21, 2026, 5:33 AM UTC 2d old

11ty Emeritus · 1 measurement · since Aug 21, 2026

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.

Nuxt Built with Nuxt
GitHub Pages Hosted by GitHub Pages

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP 2.14 s good
INP 559 ms poor
CLS 0.230 needs-improvement

Scores

97
Performance
no change
95
Accessibility
no change
96
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.26 s 2.26 s 2.26 s
CLS Cumulative Layout Shift 0.006 0.006 0.006
TBT Total Blocking Time 47 ms 47 ms 47 ms
FCP First Contentful Paint 1.81 s 1.81 s 1.81 s
Speed Index 1.81 s 1.81 s 1.81 s
TTFB Time to First Byte 611 ms 611 ms 611 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 2.26 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 57 ms
time to first byte 11 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 2.14 s 559 ms 0.230 2.14 s 1.57 s
2026-08-08 2.21 s 720 ms 0.230 2.21 s 1.66 s
2026-08-01 2.24 s 766 ms 0.240 2.24 s 1.66 s
2026-07-25 2.32 s 0.240 2.32 s 1.83 s
2026-07-18 2.25 s 0.240 2.26 s 1.83 s
2026-07-11 2.13 s 628 ms 0.240 2.13 s 1.63 s
2026-07-04 2.12 s 576 ms 0.230 2.09 s 1.61 s
2026-06-27 2.06 s 528 ms 0.230 2.06 s 1.61 s
2026-06-20 2.45 s 528 ms 0.220 2.45 s 1.80 s
2026-06-13 2.65 s 627 ms 0.230 2.65 s 1.85 s
2026-06-06 2.65 s 0.230 2.70 s 2.00 s
2026-05-30 3.03 s 544 ms 0.190 3.23 s 2.40 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 690 kB 690 kB 690 kB
Requests 43 43 43
Third-party Weight 0 B 0 B 0 B
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 46.0 kB 46.0 kB 46.0 kB
Unused CSS 21.2 kB 21.2 kB 21.2 kB

By resource type

other 247 kB · 10 req
script 233 kB · 21 req
font 177 kB · 3 req
document 30.4 kB · 1 req
stylesheet 730 B · 1 req

Page health

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

Main thread work

script evaluation 337 ms
other 212 ms
style layout 118 ms
parse HTML 27 ms
paint composite render 9 ms
script parse compile 6 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 1 rule, 154 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 6 nodes

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

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 6 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 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, 5:33 AM UTC 97 2.26 s 0.006 47 ms 690 kB 3/3 ±5 3,641 25.6s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show oldpersiangames.org's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://oldpersiangames.org/"></speedlify2-score>