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 ·

eleventy.rongying.co

https://eleventy.rongying.co/

100 100 100 100 –CWV 2AXE

Data from Aug 20, 2026, 9:34 PM UTC — 21h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 21h

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.

Netlify Hosted by Netlify

Scores

100
Performance
no change
100
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 1.53 s — — 1.53 s 1.53 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.53 s — — 1.53 s 1.53 s
Speed Index 1.53 s — — 1.53 s 1.53 s
TTFB Time to First Byte 609 ms — — 609 ms 609 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 57 ms
time to first byte 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 19.7 kB — — 19.7 kB 19.7 kB
Requests 9 — — 9 9
Third-party Weight 1.2 kB — — 1.2 kB 1.2 kB
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

other 10.3 kB · 3 req
stylesheet 6.7 kB · 3 req
document 1.9 kB · 1 req
image 816 B · 2 req
third party 1.2 kB · 1 req

Third parties 1 entities

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

Unpkg 1.2 kB · 0 ms CPU

Page health

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

Main thread work

other 89 ms
style layout 50 ms
script evaluation 13 ms
parse HTML 9 ms
paint composite render 5 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 139 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 landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 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, 9:34 PM UTC 100 1.53 s 0 0 ms 19.7 kB 3/3 ±1 2,338 22.4s

Embed this score

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