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 ·

practical.guide

https://practical.guide/

67 73 100 82 24AXE –CWV

Data from Aug 21, 2026, 6:48 AM UTC 2d old

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

Self-hosted · nginx Hosted by Self-hosted

Scores

67
Performance
no change
73
Accessibility
no change
100
Best Practices
no change
82
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 9.53 s — — 9.53 s 9.53 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 149 ms — — 149 ms 149 ms
FCP First Contentful Paint 3.10 s — — 3.10 s 3.10 s
Speed Index 3.13 s — — 3.13 s 3.13 s
TTFB Time to First Byte 1.13 s — — 1.13 s 1.13 s

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 9.53 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 1.16 s
time to first byte 182 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.14 MB — — 4.14 MB 4.14 MB
Requests 13 — — 13 13
Third-party Weight 382 kB — — 382 kB 382 kB
Third-party CPU 87 ms — — 87 ms 87 ms
Unused JS 137 kB — — 137 kB 137 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 3.74 MB · 5 req
script 315 kB · 3 req
font 65.7 kB · 2 req
document 10.0 kB · 1 req
stylesheet 4.7 kB · 2 req
third party 382 kB · 6 req

Third parties 3 entities

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

Google Tag Manager 294 kB · 77 ms CPU
Google Fonts 67.5 kB · 0 ms CPU
Google Analytics 20.9 kB · 11 ms CPU

Page health

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

Main thread work

script evaluation 340 ms
other 177 ms
style layout 81 ms
script parse compile 78 ms
paint composite render 20 ms
parse HTML 9 ms

Axe violations axe-core 4.13.0, full rule set

24 violating nodes across 5 rules, 272 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 18 nodes
  • critical image-alt — Images must have alternative text 2 nodes
  • moderate region — All page content should be contained by landmarks 2 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 4 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. 18 nodes
  • image-alt — Image elements do not have `[alt]` attributes 2 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • landmark-one-main — Document does not have a main landmark. 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, 6:48 AM UTC 67 9.53 s 0 149 ms 4.14 MB 3/3 ±21 2,449 30.8s

Embed this score

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