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 ·

jcmendez.io

https://jcmendez.io/

75 94 77 100 CWV 18AXE

Data from Aug 21, 2026, 1:17 AM UTC — 17h old.

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

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

75
Performance
no change
94
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.43 s 5.43 s 5.43 s
CLS Cumulative Layout Shift 0.002 0.002 0.002
TBT Total Blocking Time 58 ms 58 ms 58 ms
FCP First Contentful Paint 2.76 s 2.76 s 2.76 s
Speed Index 2.76 s 2.76 s 2.76 s
TTFB Time to First Byte 466 ms 466 ms 466 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 153 ms
time to first byte 31 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.71 MB 1.71 MB 1.71 MB
Requests 36 36 36
Third-party Weight 376.5 kB 376.5 kB 376.5 kB
Third-party CPU 80 ms 80 ms 80 ms
Unused JS 136.4 kB 136.4 kB 136.4 kB
Unused CSS 51.3 kB 51.3 kB 51.3 kB

By resource type

image 1.09 MB · 17 req
script 357.1 kB · 8 req
font 171.6 kB · 2 req
stylesheet 56.9 kB · 3 req
document 38.1 kB · 1 req
other 799 B · 2 req
third party 376.5 kB · 8 req

Third parties 6 entities

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

Google Tag Manager 284.4 kB · 67 ms CPU
Google Fonts 37.6 kB · 0 ms CPU
iconfinder.com 21.8 kB · 0 ms CPU
Google Analytics 20.9 kB · 9 ms CPU
Cloudflare 11.5 kB · 3 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.36 s 1.36 s 1.36 s
Long Tasks 4 4 4
DOM Elements 998 998 998
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 18 18 18
A11y Failures 2 2 2
A11y Failing Nodes 13 13 13

Main thread work

script evaluation 407 ms
style layout 373 ms
other 361 ms
script parse compile 94 ms
parse HTML 67 ms
paint composite render 58 ms

Axe violations axe-core 4.13.0, full rule set

18 violating nodes across 4 rules, 1416 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 heading-order — Heading levels should only increase by one 10 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 4 nodes
  • serious link-name — Links must have discernible text 3 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 2 of 23 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.

  • heading-order — Heading elements are not in a sequentially-descending order 10 nodes
  • link-name — Links do not have a discernible name 3 nodes

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, 1:17 AM UTC 75 5.43 s 0.002 58 ms 1.71 MB 3/3 ±16 2,477 36.3s

Embed this score

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