Website Speed & Performance Tester
> return_hub · module_loader · boot
> BOOT_SEQUENCE // ROY-HUB
HOST … · SEGMENT … · MEM … [ OK ]
CHECKSUM … · SIG … · SESSION … [ SYNC ]
> No clutter, no ads, no bait-n-switch—just simple tools that work at no cost
> return_hub · module_loader · boot
> return_hub · module_active
> Lighthouse scores · Core Web Vitals · accessibility · server check · mobile and desktop at once
Website Speed & Performance Tester runs Google Lighthouse on a public web page as a phone and as a desktop and reports Performance, Accessibility, and Best Practices scores with lab metrics such as Largest Contentful Paint and Total Blocking Time. It adds real-user Core Web Vitals from the Chrome UX Report, a server check of connection timing, protocol, compression, and redirects, and one ranked list of fixes.
Test any public page with Google Lighthouse as a phone and as a desktop at once, see how real Chrome visitors experienced it, and get one ranked list of fixes. A server check and six months of real-user trends appear while Lighthouse runs.
A mobile Performance score of 62 with LCP at 4.1 s, and Fix first led by “Improve image delivery: −1.4 s LCP”, means the hero image is the biggest win: serve it as WebP or AVIF at the size it is shown, and preload it.
Performance is a weighted mix of five lab metrics: Total Blocking Time 30%, Largest Contentful Paint 25%, Cumulative Layout Shift 25%, First Contentful Paint 10%, and Speed Index 10%. 90 and up is good, 50 to 89 needs improvement, and under 50 is poor.
Google's assessment passes when 75% of real visits over the last 28 days have LCP of 2.5 s or less, INP of 200 ms or less, and CLS of 0.1 or less.
A server wait over 600 ms, missing compression, HTTP/1.1 only, and redirect chains are flagged, because each one delays the first paint on every visit.
90 to 100 is good, 50 to 89 needs improvement, and under 50 is poor. Mobile scores are usually lower than desktop because Lighthouse emulates a mid-range phone on a slow 4G connection with a slowed-down processor.
Lighthouse is one simulated visit on fixed, slow hardware. Core Web Vitals come from real Chrome visitors over 28 days on their own devices and networks. Google uses the real-user data in search; use the lab results to find out why a page is slow.
Network routes, server load, ads, and third-party scripts vary from one run to the next, so a few points either way is normal. Test again and compare trends rather than a single number.
The Lighthouse results come from the same PageSpeed Insights service. This page adds one ranked fix list across both devices, six months of real-user trends, and a server check of connection timing, compression, HTTP/2 and HTTP/3, caching, and redirects.
No. Google's test browser and this site's server can only reach public addresses, so pages on localhost, private networks, or behind a login can't be tested. Run Lighthouse from Chrome DevTools for those.
No. This tool covers speed, accessibility, and best practices. For search and AI-answer readiness, use the GEO / AEO / SEO Audit.
No. The address is sent to Google PageSpeed Insights and the Chrome UX Report, and this site's server fetches the page once. Results are held in memory for ten minutes so repeat tests are quick, and your recent tests stay only in this browser.