What is a good website speed score?

Google PageSpeed Insights scores pages 0–100. A score of 90 or above is considered good. Scores below 50 indicate serious performance issues that are likely hurting both user experience and search rankings. For most small business websites, a score of 80–90 on mobile is a realistic target that captures most of the ranking and conversion benefit without requiring a full rebuild. The most important metric alongside the score is Largest Contentful Paint (LCP) — the time until the biggest element on the page finishes loading — which should be under 2.5 seconds.

Does website speed affect my Google ranking?

Yes. Google uses Core Web Vitals — which include page speed metrics — as ranking signals for mobile search results. A page that loads in 5 seconds on mobile will rank below a comparable page that loads in 1.5 seconds, all else being equal. The effect is most pronounced in competitive local markets where several businesses are competing for the same search terms. A slow website does not just lose visitors after they arrive — it may not appear in results at all for buyers who would have converted.

Will switching hosting providers make my website faster?

Sometimes, but hosting is usually not the primary cause of a slow small business website. The bigger factors are almost always image size, render-blocking scripts, and font loading. If you are on a shared host with poor performance and your site has other speed issues fixed, switching to a faster host (like a CDN-backed platform) can reduce load times by 0.5–1 second. If your images are uncompressed and your scripts are blocking the page render, better hosting will help less than fixing those underlying problems.

Why does my website load slower on mobile than on desktop?

Mobile devices have slower processors and often connect over cellular networks with higher latency than home broadband. A page that loads in 1.5 seconds on a fast desktop connection might take 4+ seconds on a mid-range phone over 4G. The biggest mobile-specific causes are: images that are the same size as desktop versions (a 1200px-wide image served to a 375px phone screen), scripts that load synchronously and block the page from rendering, and fonts that block text from displaying until they are fully downloaded. Google tests your mobile performance specifically when determining rankings.

Do I need a developer to improve my website speed?

Not always. Several of the most impactful fixes are available without writing code. Compressing images — running them through a free tool like Squoosh before uploading — often cuts page weight by 60–80% with no visible quality loss. If your site is on WordPress, switching to a caching plugin and a performance-focused theme can make a significant difference. Where you do need a developer is for changes like converting render-blocking scripts to defer loading, implementing responsive images with srcset, or replacing a bloated page builder with cleaner code. A Website Intelligence Audit identifies which fixes you can do yourself and which require development work.

Why Is My Website Slow? The Real Causes (And What to Fix First)

Most business owners discover their website is slow when a potential client mentions it — "I tried to check out your site but it took forever to load." By then, the damage is already done: most visitors leave within three seconds of waiting. The ones who leave do not come back, and they do not call.

A slow website is not just a user experience problem. Google uses page speed as a ranking factor for mobile search. A page that loads in five seconds on a phone may not appear for local buyers at all, even if the content is exactly what they are searching for.

The good news is that most slow small business websites have the same three or four problems — and they are fixable without rebuilding from scratch. Here is what is actually causing it.

Cause 1: Unoptimized images — the most common issue by far

Images are the single biggest cause of slow websites on small business sites. A photo taken on a modern phone is 3–6 megabytes. A standard WordPress theme uploads it at full size. Every visitor's browser then has to download that 4MB image before the page finishes loading — on every visit, on every device.

The fix is compression and format conversion. A 4MB JPG can be converted to a WebP image under 200KB with no visible quality loss at normal viewing sizes. Tools like Squoosh (free, browser-based) and Cloudflare Images handle this without writing code. For sites with many images, automating this step during upload — through a plugin or a build step — prevents the problem from returning every time a new photo is added.

If your site has a hero image that is noticeably slow to appear, it is almost always an uncompressed, full-resolution file. Fixing that one image often cuts load time by 1–3 seconds.

Cause 2: Render-blocking scripts and fonts

Most websites load several JavaScript files and custom fonts. When those files are loaded in a way that blocks the page from rendering — meaning the browser waits for them to download before showing anything — the result is a blank screen that persists for several seconds even after the HTML has arrived.

Scripts that should load after the page renders (analytics, chat widgets, social share buttons) are often loaded synchronously in the document head, where they delay the entire page. The fix is adding defer or async attributes to those script tags, or moving non-critical scripts to the bottom of the page.

Fonts cause a similar problem. A site that loads three or four custom font files before showing any text will appear blank until all fonts have downloaded. The fix is preloading the critical fonts and using a font-display strategy that shows system fonts while the custom font loads in the background. Visitors see text immediately; the custom font swaps in within a half second.

Cause 3: Too many plugins or page builder bloat

WordPress websites built with page builders — Elementor, Divi, WPBakery — typically load four to six times as much CSS and JavaScript as a hand-coded page. Each plugin adds its own scripts and stylesheets, most of which load on every page regardless of whether they are used there. A site with 30 plugins and an active page builder can have a performance score under 30 before any content optimization at all.

The same problem appears with third-party embeds: booking widgets, chat tools, review carousels. Each one loads external scripts that the page waits on. A single slow embed — a chat widget that takes 3 seconds to initialize — holds up the entire page's performance score.

Fixing this usually requires either consolidating plugins (replacing three tools that each do one thing with one tool that does all three), removing embeds that are rarely used, or rebuilding the site with leaner code. Which path makes sense depends on how much of the site's functionality is tied to specific plugins.

Cause 4: Shared hosting with no caching

Shared hosting places hundreds of websites on the same server. When your server is under load, pages take longer to generate. Without caching — where the server saves a pre-built version of your page and delivers it instantly instead of regenerating it on every visit — even a well-optimized site can be slow if the hosting tier is overwhelmed.

Most quality hosting providers for small business websites include caching at the platform level. If yours does not, a caching plugin for WordPress or a CDN (content delivery network) can reduce server response times significantly. A CDN also delivers your content from a server physically close to the visitor, which reduces the travel time for every file the page loads.

How to check your page speed right now

Google PageSpeed Insights (pagespeed.web.dev) is free and gives a detailed breakdown of what is slowing your site down. Enter your URL, choose Mobile, and read the Opportunities section. Each item includes an estimated time savings if fixed. That list, ordered by impact, is your speed fix priority queue.

The two metrics that matter most for search ranking and user experience are Largest Contentful Paint (LCP) — how long until the main content on the page finishes loading — and First Contentful Paint (FCP), the time until anything appears at all. LCP under 2.5 seconds is the target; above 4 seconds is considered poor.

What can be fixed without rebuilding

Most speed issues on service business websites can be addressed without touching the site's design or content structure. Image compression and format conversion, script deferral, font preloading, and adding a caching layer are all changes that improve performance without changing what the site looks like or how it works for visitors.

What does require more work — sometimes a rebuild — is when the performance problem is architectural: a page builder that generates 800KB of CSS no plugin can efficiently remove, or a hosting setup that cannot support caching, or a design that requires loading 12 fonts across 8 weights. In those cases, patching the symptoms improves the score slightly but does not address the root cause.

A Website Intelligence Audit covers page speed as part of the technical layer review — identifying whether your site's slow load time is fixable with targeted changes or is a symptom of a deeper architectural problem. Related: website audit checklist covers the checks worth running before any redesign decision.

Find out what is actually slowing your site down.

A Website Intelligence Audit covers speed, search visibility, and conversion — delivered as a prioritized fix list. No hourly rate. Fixed price.

See the audit ↗ Revenue Leak Audit

Why is my website slow?