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 ·

jamescowebdesigns.com

https://jamescowebdesigns.com/

47 83 73 92 CWV 77AXE

Data from Aug 20, 2026, 11:31 PM UTC — 19h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 19h

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

47
Performance
no change
83
Accessibility
no change
73
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 17.34 s 17.34 s 17.34 s
CLS Cumulative Layout Shift 0.003 0.003 0.003
TBT Total Blocking Time 874 ms 874 ms 874 ms
FCP First Contentful Paint 3.62 s 3.62 s 3.62 s
Speed Index 3.62 s 3.62 s 3.62 s
TTFB Time to First Byte 647 ms 647 ms 647 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 202 ms
element render delay 147 ms
time to first byte 44 ms
resource load delay 11 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 7.21 MB 7.21 MB 7.21 MB
Requests 61 61 61
Third-party Weight 894.2 kB 894.2 kB 894.2 kB
Third-party CPU 295 ms 295 ms 295 ms
Unused JS 446.8 kB 446.8 kB 446.8 kB
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

image 5.44 MB · 14 req
script 1.66 MB · 21 req
font 65.5 kB · 7 req
document 26.2 kB · 4 req
stylesheet 15.4 kB · 5 req
other 3.8 kB · 9 req
third party 1.53 MB · 34 req

Third parties 7 entities

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

Google Tag Manager 456.6 kB · 126 ms CPU
Stripe 243.7 kB · 78 ms CPU
Google Fonts 69.2 kB · 0 ms CPU
Netlify 55.3 kB · 30 ms CPU
Google CDN 30.9 kB · 11 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.95 s 3.95 s 3.95 s
Long Tasks 12 12 12
DOM Elements 797 797 797
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 77 77 77
A11y Failures 4 4 4
A11y Failing Nodes 36 36 36

Main thread work

script evaluation 2.02 s
other 843 ms
style layout 438 ms
script parse compile 374 ms
paint composite render 143 ms
parse HTML 79 ms
garbage collection 47 ms

Axe violations axe-core 4.13.0, full rule set

77 violating nodes across 5 rules, 519 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 41 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 16 nodes
  • serious listitem — <li> elements must be contained in a <ul> or <ol> 15 nodes
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 3 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 2 nodes

Accessibility failures 4 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 16 nodes
  • listitem — List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements. 15 nodes
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 3 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 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

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, 11:31 PM UTC 47 17.34 s 0.003 874 ms 7.21 MB 3/3 ±9 2,472 51.1s

Embed this score

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