The fastest PageSpeed fixes any business owner can make without a developer are compressing images using a free tool like Squoosh, converting images to WebP format, removing unnecessary third-party scripts like chat widgets and social embeds, enabling lazy loading on images, and checking that your hosting plan includes a CDN. These five changes alone can move a Performance score from the 40s into the 70s on most small business websites without touching a line of code.
Google PageSpeed is not a vanity metric. It is a direct ranking signal that Google uses to determine where your pages appear in search results — and a business experience signal that determines whether visitors stay or leave before they ever see what you offer. A score below 50 on mobile means more than half the people arriving at your site from a mobile search are leaving before your page finishes loading.
The assumption most small business owners make is that fixing PageSpeed requires a developer. That assumption is wrong for the majority of the most impactful improvements. The changes that move a score from poor to good on most small business websites involve images, scripts, and hosting decisions — not code. This guide covers exactly what to fix and how to fix it yourself.
Before fixing anything, know exactly where you stand. Run your website through Google PageSpeed Insights at pagespeed.web.dev — it is free and takes thirty seconds. Enter your homepage URL and run the analysis for both mobile and desktop. The scores are separate because mobile typically scores significantly lower due to network conditions and device processing power.
Write down both scores and keep them as your baseline. Every improvement you make from here should be measured against these numbers. A score of 90 or above is considered good. A score of 50 to 89 needs improvement. Below 50 is poor and is actively hurting your search rankings and user experience every day.
You can also run a complete website health check at healthypage.help/check which includes your Performance score alongside SEO, Best Practices, Accessibility, and Agentic Browsing scores so you see the full picture in one report.
Unoptimized images are the number one cause of slow PageSpeed scores on small business websites. A homepage hero image that was uploaded directly from a phone or camera at full resolution can easily be five to fifteen megabytes. The same image displayed correctly on a webpage needs to be fifty to three hundred kilobytes. That gap — five to fifteen megabytes versus three hundred kilobytes — is the gap between a two-second load time and a ten-second load time.
The fix requires no developer and no paid software. Go to squoosh.app — Google's free image compression tool — and upload every image on your site one at a time. The tool shows you the original file size on the left and the compressed version on the right with a quality slider. Drag the quality slider until the image still looks sharp to your eye and the file size is under three hundred kilobytes for standard images and under one hundred kilobytes for smaller elements like icons and thumbnails. Download the compressed version and replace the original on your website.
Do this for every image on your homepage first. Homepage images have the most impact on PageSpeed because Google measures the score on the initial page load. A homepage with four optimized images will score dramatically higher than one with four unoptimized images regardless of everything else on the page.
WebP is a modern image format developed by Google that produces images twenty-five to thirty-five percent smaller than JPEG or PNG at the same visual quality. Every major browser now supports WebP and Google PageSpeed specifically rewards pages that use it.
Squoosh — the same tool used for compression — converts images to WebP automatically. When you are compressing your images in Fix One, select WebP as the output format in the right panel before downloading. You get both the compression benefit and the format benefit in a single step.
If your website platform does not support WebP uploads directly most platforms accept it now including WordPress, Squarespace, Wix, and Systeme.io. If your specific platform does not accept WebP files, compress to JPEG at maximum quality and the compression benefit alone will still improve your score significantly.
Every third-party script added to a website — a live chat widget, a social media feed, an advertising pixel, an analytics tool, a pop-up service, a review widget — adds load time. Each script makes an external request to a third-party server that your visitor's browser has to wait for. When five of these scripts are running simultaneously the cumulative load time can add two to four seconds to every page load.
Log into your website platform and review every plugin, integration, and embedded element that is active. For each one ask a single question: is this actively contributing to revenue or is it something that was added and forgotten. A live chat widget that nobody monitors. A social media feed showing posts from three months ago. An advertising pixel from a campaign that ended. These are all adding load time with zero return.
Remove everything that is not actively earning its place on the page. The performance improvement from removing two to three unnecessary scripts often rivals the improvement from image optimization in terms of PageSpeed impact.
Lazy loading is a technique that tells the browser not to load images until they are about to enter the visitor's viewport as they scroll down the page. Without lazy loading, every image on the entire page — including images at the very bottom that the visitor may never reach — loads when the page first opens. With lazy loading, only the images visible in the first screen load immediately. Everything else loads as the visitor scrolls toward it.
On most website platforms lazy loading can be enabled without touching code. In WordPress it is enabled by default since version 5.5. In Squarespace it is automatic. In Wix it is handled automatically. In Systeme.io you can add the attribute loading="lazy" to image HTML elements directly. If you are unsure whether your platform supports it the HealthyPage health check at healthypage.help/check will flag it as an issue if it is not in place.
A Content Delivery Network serves your website files from servers geographically close to each visitor. Without a CDN, every visitor loads your site from your single hosting server — which might be in a data center a thousand miles away. With a CDN, a visitor in Los Angeles loads your site from a server in Los Angeles, a visitor in New York loads from a New York server, and a visitor in London loads from a London server. The physical proximity reduces the time it takes for files to travel from server to browser.
Check whether your current hosting plan includes a CDN. Most major hosting providers — Cloudflare, AWS CloudFront, SiteGround, WP Engine — include CDN functionality either built in or as a free add-on. If your hosting plan does not include a CDN, Cloudflare offers a free tier that works with any hosting provider and can be set up in under an hour by following their step-by-step setup guide without any developer involvement.
Server response time — how long it takes your hosting server to respond to the browser's initial request before any content loads — is measured in milliseconds. Google recommends under 200 milliseconds. Shared hosting on low-cost plans can produce response times of 600 to 1,500 milliseconds, adding a full half-second to second of invisible wait time before the page even begins loading.
If your Google PageSpeed report shows a Time to First Byte (TTFB) warning, your hosting server response time is too slow. The fix is upgrading your hosting plan to one with dedicated resources or switching to a higher-performance provider. This is the one improvement on this list that may require a decision about spending — but hosting upgrades that improve response time consistently deliver more PageSpeed improvement per dollar than any other investment.
Render-blocking resources are JavaScript and CSS files that prevent the page from displaying content until they have fully loaded. Google PageSpeed flags these directly in the Opportunities section of the report with the label Eliminate render-blocking resources. The files listed are typically from third-party services or from your theme's built-in scripts.
On most website platforms this is addressed by moving scripts to load at the end of the page rather than the beginning — a setting available in most WordPress speed plugins like WP Rocket, W3 Total Cache, or LiteSpeed Cache. If you are on a platform like Squarespace or Wix, render-blocking resources are managed by the platform itself and are not accessible without developer access. In those cases the other fixes on this list will have the most direct impact.
The complete guide for small business owners covering PageSpeed, SEO, GEO optimization, Agentic Browsing, a full self-audit checklist, and eight quick wins you can implement this week. No developer needed.
Get the Playbook — $7 $7 · Instant download · PDF included · healthypage.helpAnswers to the exact questions small business owners ask AI assistants about improving their Google PageSpeed score.
A low PageSpeed score is not a permanent condition. It is a solvable problem with known causes and known fixes — most of which require no developer, no code, and no significant budget. Start with your images and work down the list. Your free health check is at healthypage.help/check