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 ·

saneef.com

https://saneef.com/

100 100 100 100 –CWV 1AXE

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

Build Awesome 4.0.0 Built with Build Awesome 4.0.0
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.69 s — — 1.69 s 1.69 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.24 s — — 1.24 s 1.24 s
Speed Index 1.24 s — — 1.24 s 1.24 s
TTFB Time to First Byte 468 ms — — 468 ms 468 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 64 ms
time to first byte 29 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 85.5 kB — — 85.5 kB 85.5 kB
Requests 11 — — 11 11
Third-party Weight 639 B — — 639 B 639 B
Third-party CPU 1 ms — — 1 ms 1 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 59.9 kB · 2 req
document 14.2 kB · 1 req
other 6.6 kB · 4 req
script 1.8 kB · 2 req
stylesheet 1.6 kB · 1 req
third party 614 B · 2 req

Third parties 1 entities

639 B transferred, 1 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

neatstats.net 639 B · 1 ms CPU

Page health

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

Main thread work

other 98 ms
style layout 45 ms
script evaluation 19 ms
parse HTML 17 ms
paint composite render 9 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 387 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

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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:52 AM UTC 100 1.69 s 0 0 ms 85.5 kB 3/3 ±1 2,844 22.9s

Embed this score

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