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 ·

saeedmirshekari.com

https://saeedmirshekari.com/

69 86 77 92 –CWV 19AXE

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

Netlify Hosted by Netlify

Scores

69
Performance
no change
86
Accessibility
no change
77
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.72 s — — 5.72 s 5.72 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 275 ms — — 275 ms 275 ms
FCP First Contentful Paint 2.62 s — — 2.62 s 2.62 s
Speed Index 2.66 s — — 2.66 s 2.66 s
TTFB Time to First Byte 621 ms — — 621 ms 621 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.

resource load duration 87 ms
element render delay 57 ms
time to first byte 22 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.60 MB — — 1.60 MB 1.60 MB
Requests 46 — — 46 46
Third-party Weight 650.2 kB — — 650.2 kB 650.2 kB
Third-party CPU 167 ms — — 167 ms 167 ms
Unused JS 262.6 kB — — 262.6 kB 262.6 kB
Unused CSS 41.7 kB — — 41.7 kB 41.7 kB

By resource type

script 641.8 kB · 16 req
image 593.7 kB · 10 req
font 291.5 kB · 5 req
stylesheet 63.1 kB · 9 req
document 8.6 kB · 1 req
other 838 B · 3 req
third party 650.2 kB · 17 req

Third parties 8 entities

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

Google Tag Manager 465.8 kB · 134 ms CPU
Google Fonts 99.5 kB · 0 ms CPU
Netlify 55.4 kB · 24 ms CPU
StatCounter 18.5 kB · 7 ms CPU
Calendly 5.0 kB · 1 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.35 s — — 1.35 s 1.35 s
Long Tasks 6 — — 6 6
DOM Elements 354 — — 354 354
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 19 — — 19 19
A11y Failures 4 — — 4 4
A11y Failing Nodes 15 — — 15 15

Main thread work

script evaluation 680 ms
other 205 ms
script parse compile 194 ms
style layout 174 ms
parse HTML 71 ms
paint composite render 24 ms

Axe violations axe-core 4.13.0, full rule set

19 violating nodes across 8 rules, 649 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 9 nodes
  • serious link-name — Links must have discernible text 3 nodes
  • moderate heading-order — Heading levels should only increase by one 2 nodes
  • critical label — Form elements must have labels 1 node
  • moderate landmark-main-is-top-level — Main landmark should not be contained in another landmark 1 node
  • moderate landmark-no-duplicate-main — Document should not have more than one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 4 of 26 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. 9 nodes
  • link-name — Links do not have a discernible name 3 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 2 nodes
  • label — Form elements do not have associated labels 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, 7:51 AM UTC 69 5.72 s 0 275 ms 1.60 MB 3/3 ±21 2,799 27.5s

Embed this score

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