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 ·

mrmowji.com

https://mrmowji.com/

97 92 100 91 68AXE ✗CWV

Data from Aug 21, 2026, 3:11 AM UTC 2d old

Built Awesome #1,130 · 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.

GitHub Pages Hosted by GitHub Pages

Core Web Vitals field data, origin-level

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

LCP 2.20 s good
INP — no data
CLS 0.150 needs-improvement

Scores

97
Performance
no change
92
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.29 s — — 2.29 s 2.29 s
CLS Cumulative Layout Shift 0.085 — — 0.085 0.085
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 845 ms — — 845 ms 845 ms
Speed Index 845 ms — — 845 ms 845 ms
TTFB Time to First Byte 642 ms — — 642 ms 642 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.29 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 160 ms
time to first byte 99 ms

Field data Chrome UX Report, origin-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 2.20 s good 82.6% good
CLS CWV 0.150 needs-improvement 71.9% good
FCP 2.09 s needs-improvement 68.6% good
TTFB 1.67 s needs-improvement 36.7% good

Lab vs field

Lab LCP 2.29 s · field p75 2.20 s · real users are 0.96× 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 2.18 s — 0.140 2.05 s 1.67 s
2026-08-08 2.18 s — 0.130 2.05 s 1.62 s
2026-08-01 2.08 s — 0.020 1.69 s 1.29 s
2026-07-25 2.10 s — 0.020 1.75 s 1.30 s
2026-07-18 2.11 s — 0.020 1.79 s 1.31 s
2026-07-11 2.09 s — 0.020 1.89 s 1.34 s
2026-07-04 2.16 s — 0.030 1.99 s 1.52 s
2026-06-27 2.60 s — 0.040 2.58 s 1.80 s
2026-06-20 2.85 s — 0.120 2.78 s 2.15 s
2026-06-13 2.85 s — 0.150 2.77 s 2.25 s
2026-06-06 3.13 s — 0.140 3.07 s 2.85 s
2026-05-30 2.39 s — 0.050 2.39 s 2.10 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 188 kB — — 188 kB 188 kB
Requests 11 — — 11 11
Third-party Weight 0 B — — 0 B 0 B
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 114 kB · 3 req
image 44.3 kB · 2 req
script 15.8 kB · 2 req
stylesheet 5.5 kB · 1 req
document 5.3 kB · 1 req
other 2.8 kB · 2 req

Page health

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

Main thread work

style layout 106 ms
other 104 ms
script evaluation 27 ms
paint composite render 22 ms
parse HTML 9 ms
script parse compile 7 ms

Axe violations axe-core 4.13.0, full rule set

68 violating nodes across 2 rules, 518 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 67 nodes
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 1 of 13 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. 67 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 21, 2026, 3:11 AM UTC 97 2.29 s 0.085 0 ms 188 kB 3/3 ±1 2,339 21.8s

Embed this score

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