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 ·

maful.web.id

https://maful.web.id/

99 95 96 100 –CWV 3AXE

Data from Aug 21, 2026, 4:38 AM UTC — 14h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 14h

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.

Eleventy Built with Eleventy
Vercel Hosted by Vercel

Scores

99
Performance
no change
95
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.87 s — — 1.87 s 1.87 s
CLS Cumulative Layout Shift 0.007 — — 0.007 0.007
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.72 s — — 1.72 s 1.72 s
Speed Index 1.72 s — — 1.72 s 1.72 s
TTFB Time to First Byte 627 ms — — 627 ms 627 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 154 ms
time to first byte 22 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 101.0 kB — — 101.0 kB 101.0 kB
Requests 11 — — 11 11
Third-party Weight 76.1 kB — — 76.1 kB 76.1 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

font 73.9 kB · 2 req
stylesheet 9.9 kB · 4 req
document 9.7 kB · 1 req
other 4.2 kB · 2 req
third party 76.1 kB · 5 req

Third parties 1 entities

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

Google Fonts 76.1 kB · 0 ms CPU

Page health

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

Main thread work

other 76 ms
style layout 36 ms
parse HTML 11 ms
script evaluation 8 ms
paint composite render 7 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 207 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 link-name — Links must have discernible text 2 nodes
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 1 of 22 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.

  • link-name — Links do not have a discernible name 2 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 1 console error

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, 4:38 AM UTC 99 1.87 s 0.007 0 ms 101.0 kB 3/3 ±10 3,010 23.2s

Embed this score

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