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 ·

kreativan.dev

https://kreativan.dev/

97 87 77 100 CWV 43AXE

Data from Aug 21, 2026, 3:08 AM UTC — 15h old.

11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 15h

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

97
Performance
no change
87
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 2.21 s 2.21 s 2.21 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 97 ms 97 ms 97 ms
FCP First Contentful Paint 1.81 s 1.81 s 1.81 s
Speed Index 1.81 s 1.81 s 1.81 s
TTFB Time to First Byte 690 ms 690 ms 690 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.

time to first byte 138 ms
resource load duration 83 ms
element render delay 78 ms
resource load delay 14 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.20 MB 1.20 MB 1.20 MB
Requests 27 27 27
Third-party Weight 395.9 kB 395.9 kB 395.9 kB
Third-party CPU 108 ms 108 ms 108 ms
Unused JS 163.5 kB 163.5 kB 163.5 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 397.0 kB · 9 req
font 375.4 kB · 7 req
other 350.5 kB · 4 req
image 34.2 kB · 3 req
document 22.3 kB · 2 req
stylesheet 15.7 kB · 2 req
third party 396.3 kB · 13 req

Third parties 7 entities

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

Google Tag Manager 279.9 kB · 70 ms CPU
JSDelivr CDN 71.6 kB · 23 ms CPU
cal.com 24.4 kB · 6 ms CPU
Cloudflare 11.6 kB · 3 ms CPU
simpleanalyticscdn.com 7.3 kB · 6 ms CPU

Page health

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

Main thread work

script evaluation 517 ms
other 386 ms
style layout 297 ms
script parse compile 109 ms
paint composite render 105 ms
parse HTML 26 ms

Axe violations axe-core 4.13.0, full rule set

43 violating nodes across 4 rules, 630 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 40 nodes
  • critical button-name — Buttons must have discernible text 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node

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

  • target-size — Touch targets do not have sufficient size or spacing. 3 nodes
  • button-name — Buttons do not have an accessible name 1 node
  • heading-order — Heading elements are not in a sequentially-descending order 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, 3:08 AM UTC 97 2.21 s 0 97 ms 1.20 MB 3/3 ±8 2,352 26.9s

Embed this score

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