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 ·

vanessasickles.dev

https://vanessasickles.dev/

99 93 100 100 –CWV 6AXE

Data from Aug 21, 2026, 9:49 AM UTC — 9h old.

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

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 3.1.2 Built with Eleventy 3.1.2
Netlify Hosted by Netlify

Scores

99
Performance
no change
93
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 1.67 s — — 1.67 s 1.67 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.53 s — — 1.53 s 1.53 s
Speed Index 1.53 s — — 1.53 s 1.53 s
TTFB Time to First Byte 604 ms — — 604 ms 604 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 42 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 29.3 kB — — 29.3 kB 29.3 kB
Requests 11 — — 11 11
Third-party Weight 12.8 kB — — 12.8 kB 12.8 kB
Third-party CPU 7 ms — — 7 ms 7 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

script 16.6 kB · 3 req
stylesheet 5.7 kB · 2 req
document 4.7 kB · 1 req
other 2.3 kB · 5 req
third party 12.8 kB · 5 req

Third parties 3 entities

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

Cloudflare 11.5 kB · 7 ms CPU
Google Fonts 1.4 kB · 0 ms CPU
cloudflareinsights.com 36 B · 0 ms CPU

Page health

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

Main thread work

other 181 ms
style layout 74 ms
script evaluation 55 ms
paint composite render 36 ms
parse HTML 10 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 2 rules, 491 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 list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 3 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes

Accessibility failures 1 of 15 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.

  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 3 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 21, 2026, 9:49 AM UTC 99 1.67 s 0 0 ms 29.3 kB 2/3 ±1 2,482 48.7s

Embed this score

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