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 ·

willvincentvoice.com

https://www.willvincentvoice.com/

80 88 100 100 –CWV 57AXE

Data from Aug 21, 2026, 2:41 PM UTC — 4h old.

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

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.

Eleventy Built with Eleventy
Cloudflare Hosted by Cloudflare

Scores

80
Performance
no change
88
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 3.95 s — — 3.95 s 3.95 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 321 ms — — 321 ms 321 ms
FCP First Contentful Paint 1.25 s — — 1.25 s 1.25 s
Speed Index 1.25 s — — 1.25 s 1.25 s
TTFB Time to First Byte 615 ms — — 615 ms 615 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 delay 151 ms
element render delay 70 ms
resource load duration 17 ms
time to first byte 8 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 454.2 kB — — 454.2 kB 454.2 kB
Requests 19 — — 19 19
Third-party Weight 193.8 kB — — 193.8 kB 193.8 kB
Third-party CPU 67 ms — — 67 ms 67 ms
Unused JS 76.8 kB — — 76.8 kB 76.8 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 245.7 kB · 4 req
image 98.6 kB · 4 req
document 78.7 kB · 1 req
other 6.8 kB · 5 req
stylesheet 1.4 kB · 3 req
third party 193.8 kB · 5 req

Third parties 4 entities

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

Google Tag Manager 180.1 kB · 61 ms CPU
Cloudflare 11.5 kB · 6 ms CPU
plyr.io 2.3 kB · 0 ms CPU
cloudflareinsights.com 36 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 488 ms
other 376 ms
style layout 134 ms
script parse compile 74 ms
parse HTML 50 ms
paint composite render 37 ms
garbage collection 12 ms

Axe violations axe-core 4.13.0, full rule set

57 violating nodes across 8 rules, 826 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 48 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 3 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • critical label — Form elements must have labels 1 node
  • moderate landmark-no-duplicate-contentinfo — Document should not have more than one contentinfo landmark 1 node
  • moderate landmark-one-main — Document should have 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 page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 4 of 27 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. 3 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • label — Form elements do not have associated labels 1 node
  • landmark-one-main — Document does not have a main landmark. 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, 2:41 PM UTC 80 3.95 s 0 321 ms 454.2 kB 3/3 ±1 2,502 26.3s

Embed this score

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