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 ·

fershad.com

https://fershad.com/

94 91 100 92 CWV 6AXE

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

Built Awesome · 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.

Cloudflare Hosted by Cloudflare

Scores

94
Performance
no change
91
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.13 s 2.13 s 2.13 s
CLS Cumulative Layout Shift 0.101 0.101 0.101
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.10 s 2.10 s 2.10 s
Speed Index 3.19 s 3.19 s 3.19 s
TTFB Time to First Byte 1.26 s 1.26 s 1.26 s

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.

time to first byte 1.26 s
resource load duration 218 ms
element render delay 172 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.69 MB 1.69 MB 1.69 MB
Requests 16 16 16
Third-party Weight 22.9 kB 22.9 kB 22.9 kB
Third-party CPU 2 ms 2 ms 2 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 1.62 MB · 3 req
script 22.8 kB · 4 req
other 17.2 kB · 3 req
font 10.8 kB · 1 req
stylesheet 8.3 kB · 4 req
document 6.8 kB · 1 req
third party 22.9 kB · 5 req

Third parties 2 entities

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

ESM>CDN 19.3 kB · 0 ms CPU
Fathom Analytics 3.6 kB · 2 ms CPU

Page health

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

Main thread work

other 561 ms
style layout 193 ms
paint composite render 70 ms
script evaluation 56 ms
parse HTML 12 ms
script parse compile 5 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 3 rules, 456 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 3 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
  • critical button-name — Buttons must have discernible text 1 node

Accessibility failures 2 of 25 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. 7 nodes
  • button-name — Buttons do not have an accessible name 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 20, 2026, 9:33 PM UTC 94 2.13 s 0.101 0 ms 1.69 MB 3/3 ±6 3,271 26.2s

Embed this score

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