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 ·

tonfotos.com

https://tonfotos.com/

84 94 77 100 47AXE ✓CWV

Data from Aug 21, 2026, 9:37 AM UTC 2d old

Built Awesome #1,026 · 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

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 1.48 s good
INP — no data
CLS 0 good

Scores

84
Performance
no change
94
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 4.54 s — — 4.54 s 4.54 s
CLS Cumulative Layout Shift 0.020 — — 0.020 0.020
TBT Total Blocking Time 59 ms — — 59 ms 59 ms
FCP First Contentful Paint 1.12 s — — 1.12 s 1.12 s
Speed Index 1.29 s — — 1.29 s 1.29 s
TTFB Time to First Byte 785 ms — — 785 ms 785 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 4.54 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 775 ms
time to first byte 188 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.48 s good 93.9% good
CLS CWV 0 good 98.8% good
FCP 1.09 s good 87.5% good
TTFB 777 ms good 76.2% good

Lab vs field

Lab LCP 4.54 s · field p75 1.48 s · real users are 0.33× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.64 s — 0 1.09 s 729 ms
2026-08-08 1.61 s — 0 1.07 s 773 ms
2026-08-01 1.85 s — 0 1.09 s 809 ms
2026-07-25 1.79 s — 0 1.02 s 729 ms
2026-07-18 2.05 s 78 ms 0 1.14 s 925 ms
2026-07-11 2.07 s — 0 1.14 s 831 ms
2026-07-04 1.81 s — 0 1.02 s 734 ms
2026-06-27 2.07 s — 0 1.14 s 957 ms
2026-06-20 2.04 s — 0 1.18 s 957 ms
2026-06-13 2.04 s — 0 1.28 s 987 ms
2026-06-06 2.07 s — 0 1.30 s 1.03 s
2026-05-30 1.92 s 79 ms 0 1.16 s 950 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.00 MB — — 1.00 MB 1.00 MB
Requests 46 — — 46 46
Third-party Weight 91.3 kB — — 91.3 kB 91.3 kB
Third-party CPU 34 ms — — 34 ms 34 ms
Unused JS 54.3 kB — — 54.3 kB 54.3 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 669 kB · 39 req
font 222 kB · 3 req
script 90.1 kB · 1 req
document 16.1 kB · 1 req
other 4.6 kB · 2 req
third party 91.3 kB · 2 req

Third parties 1 entities

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

Yandex Metrica 91.3 kB · 34 ms CPU

Page health

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

Main thread work

other 444 ms
style layout 180 ms
script evaluation 176 ms
paint composite render 165 ms
parse HTML 45 ms
script parse compile 26 ms
garbage collection 9 ms

Axe violations axe-core 4.13.0, full rule set

47 violating nodes across 3 rules, 834 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 28 nodes
  • moderate region — All page content should be contained by landmarks 17 nodes
  • moderate landmark-one-main — Document should have one main landmark 2 nodes

Accessibility failures 2 of 26 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. 27 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, 9:37 AM UTC 84 4.54 s 0.020 59 ms 1.00 MB 3/3 ±8 2,497 34.1s

Embed this score

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