Website Speed Test
Test any page the way Google does: on a phone or on a computer, with the same Lighthouse engine as PageSpeed Insights. You get the score, the three Core Web Vitals and the fixes that save the most time, in plain words.
Lab timings, this one test
Real visitors, last 28 days
What would save the most time
Most of these come down to images, scripts and the server. Every site I build is hand-coded and sized for phones first. Book a free 20-minute strategy call and I will go through your result with you.
36 Toronto web design studios, tested on a phone
On November 17, 2026 I ran this test on the home page of every studio in my GTA website price survey, phone setting, one run each.
Sixteen scored 90 or more and two scored under 50. The slowest home page took 17.6 seconds to show its main picture, and the heaviest weighed 38 MB. For 14 of the 36, the biggest saving Google suggested was the same one: render-blocking requests, meaning stylesheets and scripts the browser has to download before it can draw anything.
The last number matters most for a small business. Google only reports real-visitor speed once a site has enough visits from Chrome users, and none of these studios had it. For most local sites the lab test above is the only speed number there is.
Which numbers to look at first
Google calls three of them Core Web Vitals and gives each a target:
- Largest Contentful Paint
- Under 2.5 seconds. How long until the biggest picture or block of text appears.
- Interaction to Next Paint
- Under 200 milliseconds. How quickly the page reacts to a tap. Only real visitors can measure it, so it shows in the real-visitor box.
- Cumulative Layout Shift
- Under 0.1. How much the page jumps while it loads, the thing that makes people tap the wrong button.
Source: Google Search Central, Core Web Vitals. Google writes that good Core Web Vitals line up with what its ranking systems reward, together with the other parts of page experience. I explain each metric and the usual fixes for a small business site in how fast your website should load, and pictures in particular in the image sizes I use.
Questions about the speed test
Is this the same as Google PageSpeed Insights?
Yes. My server sends your address to the PageSpeed Insights service and shows its answer: the same Lighthouse test and the same real-visitor report. The page here explains the result and sorts the fixes by the time each one would save.
Why does my score change each time I test?
Each test is one page load on a simulated phone, and servers, ads and third-party scripts never answer in exactly the same time twice. A swing of a few points between runs is normal. Judge the timings and the fixes, not one score.
Why is there no real-visitor data for my site?
Google only publishes it once a page or site has enough visits from Chrome users who share usage statistics. None of the 36 studios I tested had it. Until then the lab test is the number to work with.
Phone or computer: which one counts?
Test both, but fix the phone first. The phone test uses a slower device and a slower connection, and that is where 12 of the 36 studios above needed more than 4 seconds.
How many tests can I run?
Twelve new tests an hour from one connection. Testing the same page again within 30 minutes shows the saved result instantly and does not count.
Fast is only one part of a working website
The free website audit runs the speed test together with SEO, security, email and accessibility checks. If the test says your images are too big, the image converter shrinks them to WebP in your browser.