Why Does My WordPress Site Score So Low on Google PageSpeed Insights?

Low PageSpeed Insights scores are normal for WordPress sites that have not been specifically optimized for speed. The tool measures real performance problems, and WordPress sites accumulate those problems naturally as they grow. Here is what the most confusing terms in the results actually mean, and what you can realistically achieve.

What does Google PageSpeed Insights actually measure?

PageSpeed Insights simulates a real visitor loading your page from a standard mobile device on a 4G connection. It times how long each part of the loading process takes and grades the results.

The score from 0 to 100 is a summary. The real information is in the list of specific issues below it. That list tells you exactly which things are slowing your page down and estimates how much time fixing each one would save.

The tool measures two kinds of things: lab data (the simulated test it runs right now) and field data (real measurements from real visitors who used Chrome on your site, when available). Both matter, but the lab data is what you can act on immediately.

What does “render-blocking resources” mean?

Your browser cannot display anything on a page until it has run certain scripts and loaded certain style files. A render-blocking resource is one of those things that must finish before the display starts.

Imagine you asked for a menu and the server said “wait here while I go find a recipe book first.” You are standing there, looking at a blank wall, waiting. That is render-blocking.

The fix is to make non-essential scripts load after the page is already visible, and to load essential styles inline rather than as separate file requests. This is often handled through caching plugins or code changes, and it is one of the harder recommendations to act on without technical help.

What does “eliminate unused JavaScript” mean?

Many plugins load all of their code on every page, even when only some pages actually use the plugin. A booking calendar plugin that loads its date-picker code on your blog posts is sending unnecessary code to visitors who will never see the calendar.

This is one of the clearest signs that a site has accumulated too many plugins with too little management. The fix is to remove plugins you do not use, or to find plugins that load code only on the pages that need it.

For a deeper look at what happens with too many plugins, that article covers it in full.

What does “reduce server response times” mean?

Before any content loads, your browser makes a request to your web server and waits for it to respond. PageSpeed measures this as Time to First Byte, or TTFB.

A slow server response time means the server is taking a long time just to start sending the page. This is usually caused by shared hosting (your site is on a server with hundreds of others, and they are all competing), a slow database, or WordPress running code without caching in place.

The fastest fix is to enable server-level caching, which lets your server skip the database and code execution and just send a pre-built page directly.

What scores are realistic for WordPress sites?

Here is an honest picture:

A typical unconfigured WordPress site with a page builder and several plugins: 30 to 50 on mobile, 50 to 70 on desktop.

A WordPress site with good hosting, a caching plugin, and compressed images: 60 to 80 on mobile, 80 to 90 on desktop.

A heavily optimized WordPress site with managed hosting, a performance-focused setup, and minimal plugins: 75 to 90 on mobile, 90 to 95 on desktop. This requires active, ongoing effort to maintain.

A site on a platform built for pre-assembled delivery, with no plugins and no live database queries: 95+ on mobile, consistently, with no ongoing tuning. This is what Basalt’s destination looks like.

What you can do today

1. Run the test and read the whole report. Enter your address at pagespeed.web.dev. Read the opportunities section, not just the score number.
2. Identify your LCP element. The report shows what your Largest Contentful Paint is. If it is an image, compressing it is your best immediate win.
3. Count your plugins. Look at your active plugin list and ask which ones are actively being used on your site today. Deactivate the rest.
4. Check your hosting caching. Log into your hosting control panel and look for performance or caching settings.
5. Test on mobile, not desktop. The mobile score is what most of your visitors experience. Focus on improving that number.

Why these scores are hard to maintain on WordPress

Passing PageSpeed Insights is achievable on WordPress with work. Staying passing is the harder part.

Every plugin update can change how scripts load. Every new image uploaded at camera resolution adds weight. The score you earned through careful optimization drifts back down as the site grows. Maintaining a good score is a recurring effort, not a one-time fix.

If you want a site that holds those scores without ongoing tuning, Basalt moves small business websites off WordPress to a platform with nothing to hack and nothing to update. The move is free. Start at why WordPress is slow to understand the full picture.

Find out what is wrong in 60 seconds

Or skip all this. Enter your web address and we will tell you exactly what is wrong with your site. Free, 60 seconds, no account needed.