Free Website Speed Test
Enter your address. We load the page the way a phone would, then measure how fast the server answers, how heavy the page is, what stops it from showing, and what to fix first. Google’s own Core Web Vitals are added when they are available.
Google ranks pages partly on how they load on a phone, and a visitor who is kept waiting leaves. This test reads the page itself: the server’s response time, every script, stylesheet and image it references, how they are compressed and cached, and which outside services it pulls in. No account, nothing to install, and nothing on the site is changed. What we can do about the results →
Any public page works: the home page, or one page deep in the site. It takes 10 to 30 seconds, longer if the site is slow, which is itself the answer.
Result
—
Core Web Vitals, real Chrome visitors, last 28 days
What we measured
What to fix first
What Google would fix first
From Google PageSpeed Insights, which runs the page’s JavaScript on a simulated phone, so it sees what our read of the HTML cannot.
Already good
What loaded
Get the full report, and $10 off your first hour
Email yourself the complete write-up: every finding with its fix, the biggest files, and Google’s numbers when they are available. Tick the box to join the Bay Geeks newsletter too (occasional tech tips, scam alerts and maintenance reminders) and we will send you a code worth $10 off your first hour of service. We follow up once, a few days later, with the fix that matters most.
No spam, ever. Unsubscribe anytime. Offer terms → · Prefer to talk? Call 727-579-4335.
Rather go over it with someone?
Pick a time for a 15-minute call. We’ll walk through these results with you and say plainly which fixes are worth doing and what they cost. No obligation.
Pick a TimeWhat this test covers
How long the server takes to start sending the page, redirects on the way, HTTPS, compression, and whether a CDN is in front.
The HTML plus every stylesheet, script and image it references, measured, and how many files a phone has to fetch.
Scripts and stylesheets the browser must finish before it draws anything: the usual reason for a blank screen.
Oversized files, older formats, missing dimensions, and whether images below the fold load lazily.
Whether static files are cached by the browser, and which outside services (tag managers, chat widgets, embeds, fonts) the page pulls in.
When Google PageSpeed Insights is available: its performance score, lab metrics, and the Core Web Vitals your real visitors experience.
What the score means
The page starts at 100 and loses points for each finding, weighted by how much it slows a phone: a slow server or a page that stays blank costs the most, a missing cache header the least. It is our own measurement, made without running the page’s JavaScript, so a page that loads more through scripts is heavier than the count here, never lighter. Google’s score, when it is shown, comes from a full simulated phone load and is the one search ranking uses. The two usually agree on what to fix first.
Why it matters
A slow site is rarely one big problem. It is images uploaded at camera size, a plugin or two that stopped earning its place, a tag manager full of forgotten tags, and hosting that builds the page fresh for every visitor. Each is a routine fix, and together they are the difference between a page that shows at once and one that loses the visitor before the first word. When you want them done, that is what our web services are for, from hosting with a CDN and backups to the edits themselves at our hourly rate. Checking your internet connection instead? That is the internet speed test.