Page Speed Optimisation: A Practical Guide for Non-Developers

Key Takeaways

• Google uses Core Web Vitals as a direct ranking signal — pages that fail the LCP threshold (above 2.5 seconds) are at a measurable ranking disadvantage (Google Search Central on Core Web Vitals)
• A one-second delay in mobile page load time reduces conversions by an average of 20%, according to Google's research — page speed is a revenue problem, not just an SEO problem
• The most impactful fixes for most small business sites — image compression, caching, removing render-blocking scripts — do not require coding knowledge and can often be done through your CMS settings or a plugin
• RnkRocket surfaces Core Web Vitals data alongside other site health signals, so you can see exactly which pages are failing and prioritise accordingly

---

Page speed is one of those topics that sounds technical but has a deeply practical impact. If your website takes more than 3 seconds to load on a mobile phone, you are losing visitors before they have seen a single word of your content. According to research from Portent, the first 5 seconds of page load time have the highest impact on conversion rates — with sites loading in 1 second converting up to 3 times better than sites loading in 5 seconds.

For small businesses competing in local or niche markets, this is not an abstract technical concern. It is directly affecting whether your customers stay on your site or click back to a competitor.

This guide explains what page speed actually means, what Google measures, and — most importantly — what you can do about it without needing a developer.

---

What Google Measures: Core Web Vitals Explained

Google's Core Web Vitals are three specific metrics that measure real-world user experience on your pages. They are built into Google's ranking algorithm as signals that influence position in search results.

Largest Contentful Paint (LCP)

LCP measures how quickly the largest visible element on the page — usually a hero image, a large heading, or a banner — loads and becomes visible to the user.

Google's threshold:

• Good: under 2.5 seconds
• Needs improvement: 2.5–4.0 seconds
• Poor: above 4.0 seconds

LCP is the metric most directly related to the user's perception of "how fast is this page?" It is also the most commonly failed metric on small business sites, primarily because of unoptimised hero images.

Cumulative Layout Shift (CLS)

CLS measures visual stability — how much the page layout shifts around as it loads. You have experienced poor CLS when you go to click a button and the page suddenly jumps, causing you to click the wrong thing.

Google's threshold:

• Good: below 0.1
• Needs improvement: 0.1–0.25
• Poor: above 0.25

CLS problems are typically caused by images without defined dimensions, ads loading dynamically, and web fonts that render differently from fallback fonts.

Interaction to Next Paint (INP)

INP replaced First Input Delay (FID) in March 2024 as Google's measure of interactivity. It measures the time from a user interaction (click, tap, keyboard input) to the next visual response from the page.

Google's threshold:

• Good: under 200 milliseconds
• Needs improvement: 200–500 milliseconds
• Poor: above 500 milliseconds

Poor INP is usually caused by heavy JavaScript that blocks the main thread, preventing the browser from responding to user inputs quickly.

For a deeper dive into Core Web Vitals and how they interact with your overall SEO performance, see our dedicated guide to Core Web Vitals.

---

How to Check Your Current Page Speed

Before you can fix anything, you need to know where you currently stand.

Google PageSpeed Insights (pagespeed.web.dev) is the definitive free tool. Enter any URL and it gives you:

• Performance score (0–100) for both mobile and desktop
• Core Web Vitals scores with pass/fail indicators
• A list of specific issues with estimated impact on load time
• Recommendations for improvement (though these can be technical — this guide translates them into plain-English actions)

Critical: always check the mobile score, not just desktop. Mobile is what Google primarily uses for ranking (mobile-first indexing), and mobile scores are consistently lower than desktop because of slower processors and network connections.

A score of 90+ is excellent. 50–89 needs improvement. Below 50 is a priority problem.

---

The Most Impactful Fixes (No Coding Required)

Fix 1: Compress and Resize Your Images

Images are the single biggest cause of slow load times on small business websites. A high-resolution photo uploaded directly from a camera is typically 3–8MB — vastly more data than a browser needs to display an image on screen.

The target for web images:

• Hero images: 150–300KB maximum
• Blog feature images: 80–150KB
• Inline content images: 30–80KB
• Thumbnails and icons: under 20KB

Free tools to compress images before uploading:

• Squoosh — Google's own tool, very effective, drag and drop
• TinyPNG — simple interface, good for bulk compression
• ImageOptim — Mac desktop app for bulk processing

Image format: Use WebP format instead of JPEG or PNG where possible. Google's WebP data shows files 25–35% smaller than JPEG at equivalent visual quality. Most modern CMS platforms and page builders can serve WebP automatically — check your settings.

Dimensions: Do not upload a 3,000-pixel-wide image if it will only display at 800 pixels wide. Resize the image to its display size before compressing.

If you are on WordPress, the plugin ShortPixel automatically compresses and converts images to WebP on upload and can bulk-process your existing media library.

Fix 2: Enable Browser Caching

When a browser loads your site, it downloads all the assets (images, stylesheets, scripts). Caching tells the browser to store a copy of these assets locally, so on the next visit it does not need to re-download everything.

For WordPress sites, the plugins WP Super Cache or W3 Total Cache handle caching setup without requiring technical knowledge.

For Shopify, caching is largely handled at the platform level. For Squarespace, Wix, and similar builders, caching is automatic and managed by the platform.

Fix 3: Use a Content Delivery Network (CDN)

A CDN stores copies of your site's static assets (images, CSS, JavaScript) on servers in multiple geographic locations. When a user visits your site, they receive assets from the nearest server rather than your hosting origin server — which can be thousands of miles away.

For UK small businesses, using a CDN with UK points of presence ensures your UK visitors load assets from nearby servers, typically reducing time-to-first-byte (TTFB) from 300–600ms to 30–80ms.

Cloudflare offers a free tier that includes CDN functionality and can be set up in about 30 minutes by following their onboarding wizard. It sits in front of your existing hosting and requires only a DNS change — no code changes needed.

Cloudflare free also provides:

• Basic DDoS protection
• SSL certificate management
• Minification of HTML, CSS, and JavaScript

Fix 4: Remove Unused Plugins and Scripts

Every plugin installed on a WordPress site (or every script added via Google Tag Manager or your theme settings) has the potential to add load time. Scripts loaded from third parties — chat widgets, social media share buttons, cookie consent banners, abandoned cart tools — each add an HTTP request and processing time.

Audit what is actually running on your site:

1. In Google PageSpeed Insights, look at the "Reduce unused JavaScript" and "Eliminate render-blocking resources" recommendations
2. These list the scripts that are loaded but not immediately needed
3. In WordPress, disable and test each plugin individually to see which ones affect your score most
4. Remove any plugins you installed and forgot about — they are often loading scripts even if you are not actively using them

For Google Tag Manager users: audit your GTM container and remove any tags that are no longer in use. Every tag fires on page load by default.

Fix 5: Enable Lazy Loading for Images

Lazy loading means images only load when they scroll into the user's viewport, rather than all loading at once when the page opens. This dramatically reduces initial page load time, especially on long pages with many images.

Most modern browsers support lazy loading natively via the HTML `loading="lazy"` attribute. Many CMS platforms have added this as a default option:

• WordPress: Enabled by default since WordPress 5.5
• Shopify: Available in most modern themes
• Squarespace / Wix: Handled automatically by the platform

Check your theme or image settings to confirm lazy loading is active. If you are on a custom WordPress site with an older theme, the a3 Lazy Load plugin adds it with no configuration required.

Fix 6: Minify CSS and JavaScript

Minification removes unnecessary whitespace, comments, and formatting from code files — making them smaller without changing how they function. The difference is invisible to users but can reduce CSS and JS file sizes by 20–40%.

On WordPress: the W3 Total Cache and WP Rocket plugins both include minification options under "Minify" settings. Enable CSS and JS minification but test your site immediately after — very occasionally, minification breaks specific scripts.

On Shopify: minification of CSS and JavaScript is handled automatically.

On custom-built sites: tools like PostCSS and build tools like Vite or Webpack handle minification as part of the build process — if your developer is not doing this, ask them to add it.

Fix 7: Choose a Fast Hosting Provider

Your hosting infrastructure sets the performance ceiling for your site. A £2/month shared hosting plan that puts your site on a server shared with thousands of others will struggle to achieve consistent performance, regardless of other optimisations.

For small business websites, the performance sweet spot in the UK is:

• Managed WordPress hosting: Kinsta, WP Engine, or Cloudways — typically £25–60/month for a single site, but dramatically faster than budget shared hosting
• VPS hosting: More control, faster than shared, requires slightly more technical management
• Platform hosting (Shopify, Squarespace, Webflow): Infrastructure is managed for you and generally performant

If you are on budget shared hosting and your site is consistently scoring below 50 on PageSpeed Insights, migrating to faster hosting is the most impactful single action you can take.

---

Understanding PageSpeed Insights Recommendations

PageSpeed Insights uses specific language in its recommendations. Here is a plain-English translation of the most common ones:

PageSpeed Recommendation	Plain-English Meaning	What to Do
Eliminate render-blocking resources	CSS or JS files are loading before your page content, delaying visible render	Use a caching plugin to defer non-critical scripts
Properly size images	Images are much larger than their display size requires	Resize images before uploading
Serve images in next-gen formats	You are using JPEG/PNG when WebP would be smaller	Convert to WebP via plugin or Squoosh
Reduce unused JavaScript	Scripts are loaded but much of the code is never used	Audit and remove unnecessary plugins/scripts
Enable text compression	HTML, CSS, and JS are not compressed with Gzip or Brotli	Enable compression in your hosting settings or Cloudflare
Reduce initial server response time	Your server takes too long before sending any data	Upgrade hosting or enable caching at server level
Avoid enormous network payloads	Total page size is very large (usually due to images)	Compress all images, remove unnecessary assets
Avoid large layout shifts	Elements are moving after initial render (CLS issues)	Add width/height attributes to all images

---

Prioritising What to Fix First

Not every improvement has equal impact. Use this priority order for a typical small business site:

1. Compress and resize all images — usually the highest-impact, lowest-effort fix
2. Enable lazy loading — easy, immediate LCP improvement on image-heavy pages
3. Install a caching plugin — significant improvement for repeat visitors and crawlers
4. Set up Cloudflare free — CDN + minification + SSL in one step
5. Audit and remove unused scripts/plugins — reduces unnecessary processing
6. Review hosting — if the above fixes do not get you to 60+ score, hosting is likely the bottleneck

Measure your PageSpeed Insights score before and after each fix so you can see the impact of each change individually.

---

Tracking Page Speed Over Time

A one-time speed fix is not sufficient — sites slow down over time as new plugins, images, and scripts are added. Build page speed into your regular site maintenance:

• Run PageSpeed Insights on your homepage and top 5 pages monthly
• Monitor Core Web Vitals in Google Search Console → Core Web Vitals report (updated monthly with real-user data)
• Use RnkRocket's site health monitoring to flag pages where performance has degraded

For a broader understanding of how technical SEO — including page speed — fits into your overall SEO strategy, see our guide to technical SEO explained.

---

Frequently Asked Questions

What is a good PageSpeed Insights score for a small business website?

Aim for 75+ on mobile and 90+ on desktop. A mobile score below 50 represents a meaningful ranking and conversion risk and should be treated as a priority. Bear in mind that even major global brands often score 60–75 on mobile — the target is continual improvement, not perfection.

Does page speed directly affect my Google rankings?

Yes, but as one factor among many. Core Web Vitals (LCP, CLS, INP) are confirmed Google ranking signals. However, Google has stated that page speed is a "tiebreaker" signal — a page with excellent content and slow loading will generally outrank a fast page with poor content. Fix speed issues, but do not sacrifice content quality chasing score improvements.

My PageSpeed Insights score is different every time I run it. Why?

PageSpeed Insights measures real network conditions, which vary slightly each time. The score can fluctuate 5–10 points between runs without any underlying changes. What matters is the trend over time and whether you pass or fail each Core Web Vitals threshold — not the precise number on any single run.

Do I need a developer to fix page speed issues?

Many of the most impactful fixes — image compression, caching plugins, Cloudflare setup, lazy loading — require no development knowledge. If your issues are primarily render-blocking JavaScript from a custom theme or complex script management, a developer's help will be more efficient. Start with the no-code fixes first and re-measure before deciding whether to bring in technical help.

Can a slow website cause me to lose customers, not just rankings?

Absolutely. According to Google's Think with Google data, 53% of mobile users abandon sites that take more than 3 seconds to load. Page speed directly affects bounce rates, time on site, and conversion rates — independent of its SEO implications. Improving your site's speed is one of the few optimisations that simultaneously improves your SEO, your user experience, and your conversion rate.

---

Related Reading

• Core Web Vitals: What They Are and How to Improve Them
• Technical SEO Explained: What It Is and Why It Matters
• What Is SEO? A Plain-English Guide for Business Owners

---

Slow pages cost you rankings and customers every day. RnkRocket monitors your Core Web Vitals and site health automatically — plans from £9.95/month. Know what is slowing your site down before it costs you in the SERPs.