speedlify2

Recently measured 60 sites

Newest first, across the whole corpus. The dots are the four Lighthouse categories, then axe and Core Web Vitals, in the colors that run carried.

1. yonga.io 3h
2. yaes.netlify.app 3h
3. xtdb.com 3h
4. vktr.dev 3h
5. vitaline.by 3h
6. troyv.dev 3h
7. tim-kleyersburg.de 3h
8. tempertemper.net 3h
9. tripgazer.com 3h
10. teacupgorilla.com 3h
11. roboleary.net 3h
12. totmanga.com 3h
13. tampadevs.com 3h
14. splitinfinities.com 3h
15. tilt-studio.fr 3h
16. ribomation.se 3h
17. spencerharston.com 3h
18. stefanimhoff.de 3h
19. tgiles.dev 3h
20. psicologoreggio.com 3h
21. simoncox.com 3h
22. srwild.com 3h
23. teotimepacreau.fr 3h
24. rs-rss.com 3h
25. srva.ai 3h
26. svog.org 3h
27. prakriti.care 3h
28. rohanbansal.com 3h
29. simpleerb.com/blog 3h
30. star-shaped.org 3h
31. nicolas-birckel.fr 3h
32. signalkuppe.com 3h
33. museinteriors.co.uk 3h
34. sobolewski.cz/en 3h
35. realproducersmag.com 3h
36. mikeritteronline.com 3h
37. seancdavis.com/twenty-ninety 3h
38. readhostel.com 3h
39. slrconsulting.com 3h
40. mealsforthenhs.com 3h
41. rajeevedmonds.com 3h
42. silvestar.codes 3h
43. mattnortham.com 3h
44. sarrosenvironmental.com 3h
45. psycareer.org 3h
46. ryzokuken.dev 3h
47. quinndombrowski.com 3h
48. ryangittings.co.uk 3h
49. oddbird.net 3h
50. flamedfury.com 3h
51. nonbreakingspace.co.uk 3h
52. designftw.mit.edu 3h
53. design2seo.com 3h
54. naprogu.pl 3h
55. design-guide.publishing.service.gov.uk 3h
56. mx.sb 3h
57. rosiedalia.com 3h
58. debitpay.directory 3h
59. mikestreety.co.uk 3h
60. robinbruidsjurken.nl 3h

The measuring machines Lighthouse benchmark index

Recorded once per measurement, from the run whose numbers were kept. Higher is faster.

Median

2,480

±35% Median

1,612–3,348

Mean

2,607

Range

838–4,555

From 5,185 measurements. The mean sits above the median because a few unusually fast machines pull it there; most runs land close together. A site is told “the measuring machine was faster than most in this project” when its run lands outside that band. That is a distance rather than a percentile because the notice claims the CPU-bound numbers moved, and how far off the machine was decides that; how rare it was does not. These machines vary by running fast rather than slow, so in practice the notice is a fast-machine one.

Reading the logs

Each run writes a full NDJSON log to logs/<runId>.ndjson, one JSON object per line, plus a summary line appended to logs/runs.ndjson. Both are greppable:

# Every warning and error across all runs
grep -h '"level":"warn"\|"level":"error"' logs/*.ndjson | jq .

# What happened to one site in one run
jq 'select(.data.url == "https://example.com/")' logs/2026-01-01*.ndjson

# Run history at a glance
npx speedlify runs