How to Audit Your Website’s Speed in 7 Steps (No Developer Required)

Go to pagespeed.web.dev and enter your homepage URL. Your own experience of “does this feel slow” is unreliable — you’re on a fast connection, your browser has already cached half the page, and you’re testing the same site every day. PageSpeed Insights simulates a real visitor on a typical connection and gives you an actual score, split into Mobile and Desktop. Always check Mobile first; it’s almost always worse, and it’s what most of your visitors are actually using.

The red, orange or green badge is not the point — the number under it is. Anything below 50 on mobile means real visitors are likely abandoning the page before it finishes loading. Write the number down. You’ll want it later to prove whether whatever gets fixed actually made a difference, rather than trusting a “feels faster” impression.

Scroll to the “Diagnostics” section of the report. Look specifically for anything about render-blocking resources — this is almost always the single biggest lever on an older or heavily-plugin-laden site. It usually means a font, a script, or a stylesheet is forcing the browser to stop and wait before it can show anything at all. You don’t need to fix this yourself; you just need to know it exists, because it’s the first thing worth mentioning to whoever does the fix.

Images are the most common cause of slow load times, and the easiest to fix. In the same Diagnostics section, look for “Properly size images” or “Serve images in next-gen formats.” If you see either flagged, it almost always means someone uploaded a 4MB photo straight from a phone or camera without resizing it first — a problem a good web team can fix sitewide in one afternoon, often cutting load time in half on its own.

Homepages get all the attention, but a service page or blog post is usually where a paid ad or a search result actually lands someone. Run the same PageSpeed test on your busiest inner page. It’s common to find the homepage scoring fine while a page carrying an embedded video or an old plugin’s widget is dragging badly — and that page might be the one costing you the most.

Turn off Wi-Fi on your phone, switch to mobile data, and load your site the way an actual customer standing outside your business would experience it. Automated tools are useful, but nothing replaces watching the page load, in real time, on a real connection. If it feels frustrating to you on a decent connection, it’s worse for someone with weaker signal.

You don’t need to fix everything in the report — most sites never will, and most of it doesn’t matter much. Write down your mobile score, whatever the single biggest render-blocking issue was, and whether images were flagged. Those three data points are enough to have a focused, useful conversation with a developer instead of a vague one — and enough to know, next time you run this same seven-step audit, whether anything actually improved.