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 ·

pnetto.com

https://pnetto.com/

96 90 100 90 38AXE –CWV

Data from Aug 22, 2026, 3:43 AM UTC 41h old

Built Awesome #884 · 3 measurements · 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.

Vercel Hosted by Vercel

Scores

96
Performance
no change
90
Accessibility
no change
100
Best Practices
no change
90
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.28 s — — 2.28 s 2.28 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.28 s — — 2.28 s 2.28 s
Speed Index 2.28 s — — 2.28 s 2.28 s
TTFB Time to First Byte 618 ms — — 618 ms 618 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 2.28 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 122 ms
time to first byte 15 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 115 kB — — 115 kB 115 kB
Requests 23 — — 23 23
Third-party Weight 4.7 kB — — 4.7 kB 4.7 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 37.6 kB — — 37.6 kB 37.6 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

other 55.8 kB · 16 req
script 41.8 kB · 2 req
document 8.8 kB · 1 req
stylesheet 8.6 kB · 4 req
third party 4.7 kB · 5 req

Third parties 2 entities

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

umami.is 3.3 kB · 2 ms CPU
Adobe TypeKit 1.3 kB · 0 ms CPU

Page health

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

Main thread work

other 235 ms
style layout 168 ms
paint composite render 60 ms
script evaluation 45 ms
parse HTML 11 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

38 violating nodes across 4 rules, 713 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 35 nodes
  • serious aria-prohibited-attr — Elements must only use permitted ARIA attributes 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 1 node

Accessibility failures 2 of 21 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. 25 nodes
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 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 22, 2026, 3:43 AM UTC 96 2.28 s 0 0 ms 115 kB 2/3 ±0 2,476 49s
Aug 21, 2026, 9:27 PM UTC NO_FCP: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP) 95.9s
Aug 21, 2026, 2:35 PM UTC NO_FCP: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP) 95.9s

Embed this score

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