Test PageSpeed yourself: free tools explained clearly

Why should you test PageSpeed regularly yourself?

Website speed is not a one-time launch task. New images, plugins, cookie banners, tracking codes or a booking tool can slow down a previously fast site. For small businesses, a simple rhythm is enough: test immediately after major changes and otherwise do a short check monthly or quarterly.

The test mainly helps you spot problems early. If your contact page suddenly takes five seconds or a large photo blocks the home page, you lose enquiries before anyone reaches the form. A PageSpeed test does not replace technical maintenance, but it shows where a closer look is worthwhile.

Which free tools are best for beginners?

The most useful starting point is Google PageSpeed Insights. Enter your URL and you receive a mobile and desktop report. PageSpeed Insights combines lab data with field data from the Chrome User Experience Report when enough real-user data is available. If field data is missing, the lab test is still useful but not the whole truth.

You can also use Lighthouse in the Chrome browser. Open the website, start developer tools and create a performance report. For non-technical users, PageSpeed Insights is usually enough. WebPageTest or GTmetrix can add detail, but do not overvalue every single percentage point.

• PageSpeed Insights: quick overview, especially for mobile
• Lighthouse in Chrome: technical lab test in the browser
• WebPageTest: detailed waterfall for developers
• GTmetrix: accessible view of load time and page weight
• own smartphone test on mobile data: often the most honest impression

Which PageSpeed metrics really matter?

The big score from 0 to 100 is visible, but not the only decision point. The Core Web Vitals matter more: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Google defines good targets as LCP up to 2.5 seconds, INP up to 200 milliseconds and CLS no more than 0.1. In plain language: main content visible quickly, page usable quickly, no jumping layout.

Pay special attention to the mobile report. Many local searches happen on the go: a customer looks for a tradesperson, practice, salon or restaurant and wants to call or book quickly. If desktop is green but mobile is red, that is not cosmetic; it can cost real revenue.

How do you read the recommendations without tech jargon?

PageSpeed reports often use terms such as “render-blocking resources”, “unused JavaScript” or “properly size images”. In practice, sort the issues into four groups: images, code, server and third-party tools. Images are often too large or in the wrong format. Code often means too many plugins, sliders or page-builder leftovers. Server means slow hosting or missing caching.

Third-party tools include everything loaded from outside: maps, videos, review widgets, chat, tracking, ad pixels and external fonts. Each tool may be useful, but each tool costs load time. Do not only ask “How do I remove the warning?” Ask “Do our customers really need this element before first contact?”

• Images: compress, correct size, use WebP
• Code: remove unnecessary plugins, sliders and animations
• Server: check hosting, caching and response time
• Third parties: load only what the business really needs

How do you run a clean PageSpeed test?

Do not test only the home page. Check at least the home page, the most important service page and the contact page. For shops or booking systems, also test product page, cart or booking flow. Repeat the test two or three times because lab data can vary. The trend matters more than one outlier.

Also do a real-world test: smartphone, mobile data, cleared browser cache or private tab. Can you find phone number, opening hours and enquiry button quickly? Does the form react without delay? For small businesses, this manual impression is often more valuable than a perfect technical number.

What can you improve yourself, and when do you need help?

Many quick wins are manageable: do not upload original camera files, resize images before upload, remove old sliders, disable unnecessary plugins, avoid autoplay videos and have fonts hosted locally. If you use WordPress, still make changes carefully and keep a backup first.

Professional help is worthwhile when the site remains slow after small fixes, when a shop or booking system is involved or when PageSpeed breaks after every update. In our website subscriptions, the technical base is part of the service: Starter from 79 euros per month, Business from 149 euros and Premium from 299 euros. SEO can be added from 69 euros once speed and structure are clean.

Which PageSpeed testing mistakes should you avoid?

The most common mistake is score chasing. A small business website does not need 100 points at any cost. It matters more that customers can see content, click and contact you quickly. Do not remove important elements just because a tool shows a theoretical gain.

The second mistake is testing once and never again. Performance is maintenance. New photos, tracking codes or external widgets change the page. A short regular self-test prevents slow decline and makes conversations with providers more concrete.