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 ·

shimma.info

https://shimma.info/

59 84 96 92 CWV 48AXE

Data from Aug 21, 2026, 7:59 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.

Self-hosted · nginx Hosted by Self-hosted

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 659 ms good
INP 88 ms good
CLS 0 good

Scores

59
Performance
no change
84
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 10.42 s 10.42 s 10.42 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 403 ms 403 ms 403 ms
FCP First Contentful Paint 2.26 s 2.26 s 2.26 s
Speed Index 5.06 s 5.06 s 5.06 s
TTFB Time to First Byte 819 ms 819 ms 819 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 1.67 s
resource load duration 330 ms
resource load delay 241 ms
time to first byte 112 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 659 ms good 96.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 88 ms good 92.8% good
CLS CWV 0 good 96.7% good
FCP 526 ms good 96.7% good
TTFB 198 ms good 95.8% good

Lab vs field

Lab LCP 10.42 s · field p75 659 ms · real users are 0.06× 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
2026-08-08
2026-08-01
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27
2026-06-20
2026-06-13
2026-06-06
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.81 MB 2.81 MB 2.81 MB
Requests 20 20 20
Third-party Weight 480.7 kB 480.7 kB 480.7 kB
Third-party CPU 134 ms 134 ms 134 ms
Unused JS 208.9 kB 208.9 kB 208.9 kB
Unused CSS 18.4 kB 18.4 kB 18.4 kB

By resource type

image 1.79 MB · 7 req
script 497.0 kB · 5 req
font 69.6 kB · 2 req
other 43.1 kB · 1 req
stylesheet 21.8 kB · 2 req
document 8.2 kB · 1 req
third party 480.7 kB · 6 req

Third parties 3 entities

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

Google Tag Manager 455.5 kB · 125 ms CPU
Google Analytics 20.9 kB · 9 ms CPU
JSDelivr CDN 4.3 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.37 s 1.37 s 1.37 s
Long Tasks 6 6 6
DOM Elements 617 617 617
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 48 48 48
A11y Failures 4 4 4
A11y Failing Nodes 51 51 51

Main thread work

style layout 498 ms
script evaluation 466 ms
other 265 ms
script parse compile 117 ms
parse HTML 16 ms
paint composite render 12 ms

Axe violations axe-core 4.13.0, full rule set

48 violating nodes across 4 rules, 821 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 valid-lang — lang attribute must have a valid value 45 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • serious link-name — Links must have discernible text 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node

Accessibility failures 4 of 23 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.

  • valid-lang — `[lang]` attributes do not have a valid value 48 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • link-name — Links do not have a discernible name 1 node
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 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:59 AM UTC 59 10.42 s 0 403 ms 2.81 MB 3/3 ±13 2,801 31.2s

Embed this score

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