speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

makkusu.dev

https://makkusu.dev/

81 88 100 100 6AXE CWV

Data from Aug 21, 2026, 4:40 AM UTC 2d old

Built Awesome #1,015 · 1 measurement · since Aug 21, 2026

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
Self-hosted · nginx Hosted by Self-hosted

Scores

81
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.67 s 3.67 s 3.67 s
CLS Cumulative Layout Shift 0.036 0.036 0.036
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 3.67 s 3.67 s 3.67 s
Speed Index 3.67 s 3.67 s 3.67 s
TTFB Time to First Byte 735 ms 735 ms 735 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 3.67 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 1.21 s
time to first byte 136 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.04 MB 3.04 MB 3.04 MB
Requests 15 15 15
Third-party Weight 368 kB 368 kB 368 kB
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 213 kB 213 kB 213 kB

By resource type

font 2.80 MB · 5 req
stylesheet 219 kB · 2 req
document 2.3 kB · 1 req
script 2.3 kB · 4 req
other 366 B · 1 req
image 330 B · 1 req
third party 368 kB · 6 req

Third parties 2 entities

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

Google Fonts 367 kB · 0 ms CPU
xxiivv.com 330 B · 0 ms CPU

Page health

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

Main thread work

other 157 ms
style layout 76 ms
parse HTML 36 ms
script evaluation 13 ms
paint composite render 6 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 4 rules, 56 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 of 12 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
  • 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, 4:40 AM UTC 81 3.67 s 0.036 0 ms 3.04 MB 3/3 ±7 2,952 26.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show makkusu.dev's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://makkusu.dev/"></speedlify2-score>