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 ·

homeding.github.io

https://homeding.github.io/

100 77 100 100 9AXE ✓CWV

Data from Aug 20, 2026, 11:26 PM UTC 2d old

Built Awesome #922 · 1 measurement · since Aug 20, 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 920 ms good
INP — no data
CLS 0 good

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 940 ms — — 940 ms 940 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 940 ms — — 940 ms 940 ms
Speed Index 940 ms — — 940 ms 940 ms
TTFB Time to First Byte 604 ms — — 604 ms 604 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 940 ms 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 59 ms
time to first byte 5 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 920 ms good 98.4% good
CLS CWV 0 good 99.2% good
FCP 817 ms good 97.5% good
TTFB 469 ms good 92.1% good

Lab vs field

Lab LCP 940 ms · field p75 920 ms · real users are 0.98× 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 850 ms — 0 776 ms 463 ms
2026-08-08 844 ms — 0 739 ms 443 ms
2026-08-01 827 ms — 0 746 ms 469 ms
2026-07-25 901 ms — 0 869 ms 591 ms
2026-07-18 1.00 s — 0 968 ms 632 ms
2026-07-11 980 ms — 0 911 ms 616 ms
2026-07-04 942 ms — 0 891 ms 584 ms
2026-06-27 834 ms — 0 805 ms 460 ms
2026-06-20 830 ms — 0 795 ms 456 ms
2026-06-13 834 ms — 0 815 ms 412 ms
2026-06-06 817 ms — 0 738 ms 362 ms
2026-05-30 796 ms — 0 738 ms 372 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 28.4 kB — — 28.4 kB 28.4 kB
Requests 10 — — 10 10
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

document 16.4 kB · 4 req
stylesheet 5.1 kB · 1 req
script 5.0 kB · 2 req
other 2.0 kB · 2 req
third party 28.4 kB · 9 req

Page health

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

Main thread work

other 386 ms
script evaluation 163 ms
style layout 127 ms
paint composite render 125 ms
parse HTML 8 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

9 violating nodes across 4 rules, 527 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 4 nodes
  • serious object-alt — <object> elements must have alternative text 3 nodes
  • critical button-name — Buttons must have discernible text 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

Accessibility failures 3 of 15 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.

  • object-alt — `<object>` elements do not have alternate text 3 nodes
  • button-name — Buttons do not have an accessible name 1 node
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 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, 11:26 PM UTC 100 940 ms 0 0 ms 28.4 kB 3/3 ±0 2,494 22.8s

Embed this score

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