speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time. Follow us on Mastodon or Bluesky.

Charts Compare Measurement runs Embed a score Open to Work

gericci.me

https://gericci.me/

100PERF 100A11Y 100BEST 100SEO !AXE –CWV

Ranks Overall #591 Built Awesome #444

Data from Sep 23, 2026, 10:42 PM UTC old, older than this category's 14 days freshness target Measured once a week · 28 runs since Aug 20, 2026

Elsewhere: PageSpeed Insights · Calibre · Treo · CrUX Vis · Tame the Bots · Scoring Calculator · Wayback Machine

The most recent attempt failed (6 in a row). ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403)

Numbers below are from the last successful run, old.

Retries are backing off, so this site is being attempted less often than the rest.

The measuring machine was faster than most in this project.

Lighthouse benchmark index was 4,021, 62% faster than this project's median of 2,486. CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).

Stack

hc Hosted by hcdn

Lighthouse Scores LAB Simulated

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

Metrics LAB

No field data: the Chrome UX Report is not being collected for this project, so every figure below is from the Lighthouse run.

Metric Lab Simulated
Value Change / range Trend
LCP CWV (estimate) Largest Contentful Paint 1.42 s good ↑ +456 ms (+47.5%) 961 ms – 2.80 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0.003 good → no change 0.003 – 0.003
TBT Total Blocking Time 0 ms good → no change 0 ms – 0 ms
FCP First Contentful Paint 1.42 s good ↑ +456 ms (+47.5%) 961 ms – 2.80 s
Speed Index 1.42 s good ↑ +270 ms (+23.5%) 1.15 s – 6.77 s
TTFB Time to First Byte 633 ms good ↑ +4 ms (+0.6%) 629 ms – 1.32 s

LCP Subparts LAB Unthrottled

The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab LCP shown above is a simulated throttled estimate.

time to first byte 394 ms
element render delay 107 ms

Page weight

Metric Value Change / range Trend
Page Weight 88.8 kB ↑ +10 B 88.8 kB – 88.9 kB
Requests 11 → no change 11 – 11
Third-party Weight 0 B → no change 0 B – 0 B
Third-party CPU 0 ms → no change 0 ms – 0 ms
Unused JS 0 B → no change 0 B – 0 B
Unused CSS 0 B → no change 0 B – 0 B

By resource type

Type Transfer Share Size Requests
font 66.3% 58.9 kB 3
document 16.8% 14.9 kB 1
stylesheet 8.8% 7.8 kB 3
other 8.1% 7.2 kB 4
Total 88.8 kB 11

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

0% of pixels differ — they are identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Page health

Metric Value Change / range Trend
Main Thread Work 172 ms ↓ -15 ms (-8%) 172 ms – 203 ms
Long Tasks 0 → no change 0 – 0
DOM Elements 134 → no change 134 – 134
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 2 → no change 2 – 2
A11y Failures 0 → no change 0 – 0
A11y Failing Nodes 0 → no change 0 – 0

Main thread work

Task Time Share Duration Simulated
other 55% 94 ms
style layout 25% 43 ms
parse HTML 9% 15 ms
script evaluation 6% 11 ms
paint composite render 4% 7 ms
script parse compile 1% 1 ms
Total 172 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 1 rule, 212 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • moderate region — All page content should be contained by landmarks 2 nodes

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 7, 2026, 5:25 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.6s
Oct 6, 2026, 11:21 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.6s
Oct 3, 2026, 9:08 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 13.8s
Oct 1, 2026, 2:25 PM UTC The "start lh:runner:gather" performance mark has not been set 273.1s
Oct 1, 2026, 7:04 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.6s
Oct 1, 2026, 12:22 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 17.1s
Sep 23, 2026, 10:42 PM UTC 100 1.42 s 0.003 0 ms 88.8 kB 2/3 ±0 4,021 +62% 27.5s Wayback
Sep 23, 2026, 3:19 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 13.4s
Sep 16, 2026, 2:39 PM UTC 100 961 ms 0.003 0 ms 88.8 kB 2/3 ±0 2,292 -8% 25.7s Wayback
Sep 16, 2026, 3:31 AM UTC The "start lh:runner:gather" performance mark has not been set 274s
Sep 9, 2026, 12:02 AM UTC 85 2.80 s 0.003 0 ms 88.9 kB 2/3 ±12 2,492 0% 40.5s Wayback
Sep 7, 2026, 10:44 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 11.9s
Sep 6, 2026, 4:55 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.6s
Sep 5, 2026, 12:41 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.9s
Sep 4, 2026, 10:41 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.8s
Sep 3, 2026, 1:05 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.8s
Sep 1, 2026, 10:56 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 13.2s
Aug 31, 2026, 9:14 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.9s
Aug 27, 2026, 4:15 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 13.1s
Aug 26, 2026, 9:40 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.8s
Aug 25, 2026, 8:42 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 13.2s
Aug 24, 2026, 8:00 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.5s
Aug 23, 2026, 7:33 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.5s
Aug 22, 2026, 3:23 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 13.2s
Aug 22, 2026, 6:42 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 13.1s
Aug 21, 2026, 11:31 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.8s
Aug 21, 2026, 4:44 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 14.9s
Aug 20, 2026, 11:33 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) 12.9s

Embed this score

Use this web component to show gericci.me's scores on any website, updated whenever this instance re-measures. Don’t forget to bundle the speedlify2-score.js component code into your site!

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