Your PageSpeed Score Is Under 50 — Here's What to Do Next

A PageSpeed score under 50 puts your site in the red zone. It means real visitors — especially on mobile — are experiencing a noticeably slow page, and Google is aware of it through Core Web Vitals field data.

But here is what most articles will not tell you: a score under 50 is fixable in most cases without a developer, without rebuilding your site, and without expensive tools. The causes of scores this low are almost always the same four problems — and all four have practical solutions.

This guide gives you a clear, ordered action plan. Follow the steps in sequence. Do not skip ahead.

What a Score Under 50 Actually Means

A PageSpeed score under 50 signals that your page has significant performance issues that real users notice. Specifically it means:

• Your LCP (how fast the main content loads) is almost certainly over 2.5 seconds
• Your page likely has multiple Core Web Vitals failures
• Google is flagging your pages as Poor in Search Console
• Mobile users are experiencing load times that increase bounce rate significantly

According to Google's research, 53% of mobile users abandon a page that takes longer than 3 seconds to load. A score under 50 typically corresponds to load times well above this threshold.

This is not just an SEO problem — it is a business problem. Slow pages lose visitors before they have a chance to read your content or become customers.

Understand what scores mean across the full range in our guide → What Is a Good PageSpeed Score? (And How to Fix a Bad One)

Understand how this impacts your Google rankings specifically in our guide → Does Page Speed Actually Affect Google Rankings in 2026?

Step 1: Diagnose Before You Fix

Never start fixing blindly. Run a proper diagnosis first — 20 minutes here saves hours of wasted effort.

Diagnosis checklist

1. Run PageSpeed Insights on mobile: Go to pagespeed.web.dev. Test your homepage and your two highest-traffic pages separately. Screenshot the results. Write down which metrics are failing — LCP, INP, or CLS.

2. Check the Opportunities section: PageSpeed Insights lists specific fixes ranked by estimated impact (in seconds saved). The top three Opportunities on your page are where you start. Everything else is secondary.

3. Check Google Search Console: Go to Experience → Core Web Vitals. Identify which pages are marked Poor and which specific metric is failing. This is real user data — more reliable than the lab score.

4. Identify your LCP element: In PageSpeed Insights mobile results, scroll to the Diagnostics section and find "Largest Contentful Paint element." It tells you exactly which element is slowest — usually a hero image or large heading.

Learn how to read your full technical audit results in our guide → How to Read a Technical SEO Audit Report (Beginner's Guide)

Step 2: Fix the Biggest Issues First

Scores under 50 almost always have the same root causes. Address them in this order.

Unoptimised Images

Images are responsible for low scores in approximately 70% of cases. A single uncompressed hero image can drag your score from 75 down to 40.

Fix — in order of impact:

1. Find the heaviest images: In Chrome, right-click → Inspect → Network tab → filter by "Img" → sort by Size. Any image over 300KB on a page needs compression.
2. Compress and convert to WebP: Upload each oversized image to squoosh.app. Convert to WebP at quality 80. Download. Re-upload to your site replacing the original.
3. Set explicit dimensions: Add width and height attributes to every image tag. Prevents CLS (layout shift) which compounds your score problem.
4. Disable lazy loading on above-fold images: Lazy loading delays the hero image — the most common LCP element. In WordPress caching plugins, add your hero image to the "exclude from lazy load" list.

Learn the complete image fix process in our guide → How WebP Images Improve Your PageSpeed Score and SEO

Unused JavaScript

The second most common cause of scores under 50. JavaScript files load, parse, and execute in the browser — blocking page rendering while they run.

Fix:

1. Delay non-essential JS: In WP Rocket → File Optimisation → enable "Delay JavaScript Execution." In LiteSpeed Cache → Page Optimisation → enable "JS Defer."
2. Remove unused plugins: Every inactive plugin with scripts running is burning JavaScript execution time. Go to WordPress → Plugins. Deactivate anything not actively used. Test your score after each deactivation.
3. Check for third-party scripts: Google Tag Manager, Hotjar, Intercom, chat widgets — each adds 100–500ms of execution time on mobile. Audit which ones you genuinely need and remove the rest.

Learn how plugins affect your performance in our guide → How to Find Which WordPress Plugins Are Slowing Your Site

No Server Caching

Without caching, your server rebuilds your page from scratch for every single visitor. On shared hosting this can mean 1–3 second server response times (TTFB) — before the browser has even started loading your content.

Fix:

1. Enable server-side caching: In your hosting control panel (cPanel), look for LiteSpeed Cache, OPcache, or server-level caching. Enable it with one click.
2. Install a caching plugin: WP Rocket ($59/year) or LiteSpeed Cache (free) both provide page-level caching that serves pre-built HTML to visitors instead of rebuilding it each time.
3. Enable Cloudflare: Cloudflare's free tier acts as a CDN and caches your pages at edge locations worldwide — dramatically reducing TTFB for all visitors regardless of location.

Too Many Plugins

Every active WordPress plugin is a potential performance drain. Sites with 20–30 active plugins almost always score under 50 on mobile. Each plugin adds PHP execution time on the server AND JavaScript execution time in the browser.

Fix — the plugin audit:

1. List all active plugins
2. Categorise each as: Essential / Useful / Unnecessary
3. Deactivate all Unnecessary plugins immediately
4. Test score after deactivation — improvement is often instant
5. For each Useful plugin: research if a lighter alternative exists

Target: Under 15 active plugins for a typical WordPress blog. Under 20 for a WooCommerce store.

Step 3: Re-Test and Track Progress

After each fix — test again. Do not apply all fixes at once. Apply one fix, run PageSpeed Insights three times, record the average, then apply the next fix.

This approach shows you exactly which fix had the most impact — valuable information if you ever need to troubleshoot regression later.

For tracking real-world improvement in Google Search Console, remember field data updates on a 28-day rolling cycle — expect 3–4 weeks to see the full impact in Search Console.

Check your Core Web Vitals status alongside your PageSpeed score in our guide → How to Pass Core Web Vitals Without Hiring a Developer

Common Mistakes When Fixing a Low Score

Mistake 1: Only testing the homepage. Your homepage is often your best-optimised page. Blog posts and product pages frequently score much lower. Test your top five traffic pages individually.

Mistake 2: Chasing 100 instead of passing Core Web Vitals. A score of 100 is nearly impossible for real-world sites. Focus on passing LCP, INP, and CLS thresholds — a score of 75–85 with passing Core Web Vitals is an excellent outcome.

Mistake 3: Installing multiple performance plugins simultaneously. Two caching plugins conflict and break each other. One plugin, configured well, is always better than two competing plugins.

Mistake 4: Forgetting mobile. Always test and fix the mobile score. Desktop optimisations do not always translate to mobile improvements. Google cares about mobile — so you should too.

Understand why mobile always scores lower in our guide → Why Your Mobile PageSpeed Score Is Always Lower Than Desktop

Mistake 5: Fixing and forgetting. PageSpeed scores regress. A new plugin installation, a theme update, or a large image upload can drop your score by 20 points overnight. Check quarterly or after any major site change.

FAQ

Is a PageSpeed score of 38 really that bad for SEO?

Yes — a score this low almost certainly means failing Core Web Vitals on mobile. Google's field data will flag your pages as Poor in Search Console, which actively suppresses ranking potential. Fix it as a priority.

How quickly can I get from under 50 to over 70?

With the four fixes in this guide — image compression, JS delay, caching, and plugin reduction — most WordPress sites move from under 50 to 65–80 within a single day of work. Lab score improvements are immediate. Field data improvements take 28 days.

My score is 42 on mobile but 91 on desktop. Which do I fix?

Mobile, always. Google uses mobile-first indexing for rankings. Your desktop score at 91 is irrelevant to SEO if your mobile score is 42 and failing Core Web Vitals.

Should I rebuild my site to fix a score under 50?

Almost never necessary. The vast majority of scores under 50 are caused by fixable configuration issues — images, plugins, caching — not fundamental site architecture problems. Only consider rebuilding if you have tried all four fixes and your score remains under 50.

Will a CDN fix my score under 50?

A CDN helps significantly with TTFB (server response time) but does not fix image or JavaScript issues. Use a CDN alongside image compression and JS optimisation — not instead of them.

Conclusion

A PageSpeed score under 50 is serious — but it is fixable in a single day of focused work for most sites. The same four problems cause nearly every sub-50 score: oversized images, unused JavaScript, missing server caching, and too many active plugins.

Work through the fixes in order. Diagnose first. Fix images. Enable caching. Delay JavaScript. Audit plugins. Test after each change. Track progress in Google Search Console over 28 days.

Most site owners who follow this sequence move from under 50 to 70+ within a day of applied fixes — without a developer, without rebuilding their site, and without expensive tools.