Why Is Your Website’s Mobile PageSpeed Score So Low?

A hand holding a smartphone whose screen shows a loading bar and the words β€œLoading... Please Wait”

A low mobile score in Google's PageSpeed Insights is not a penalty, and it is not the number Google ranks on. It is a lab test on a simulated phone. What matters is how fast the page feels to real visitors. Read the real-visitor data first, fix the heavy items you control, and ignore the rest.

Most guides stop at "field data vs lab data." This one covers how the score is graded, what you can change on a website builder, and how to test the pages that bring in money.

Does a low PageSpeed score hurt your Google rankings?

Not directly. The 0 to 100 score comes from Lighthouse, a lab test. Google says Core Web Vitals, measured from real visits, are used by its ranking systems, but relevance comes first. Google even warns that chasing a perfect score just for SEO "may not be the best use of your time."

Google's page experience guide says Search "always seeks to show the most relevant content, even if the page experience is sub-par," and that good results in speed reports don't guarantee top rankings. Speed helps when several pages answer a search equally well. It will not carry a thin page past a better one.

Why is the mobile score so much lower than desktop?

Because the mobile test is tougher on purpose. PageSpeed Insights simulates a mid-tier phone on a throttled mobile connection, and Google's docs name the Moto G4. Desktop runs on an emulated wired connection. The same page can score in the 40s on mobile and the 80s on desktop without anything being broken.

The score is also graded on a curve. Per Lighthouse's scoring docs, each metric earns a 50 when it matches the fastest quarter of real websites in the HTTP Archive dataset, and a 90 only around the fastest 8 percent. Past about 96, every extra point gets harder. A 50 is not a failing grade.

Total Blocking Time carries 30 percent of the score and is mostly driven by JavaScript, much of which belongs to the platform on a website builder. Scores also move between runs, so test three times and use the middle result.

What should you read first in the report?

Read the section at the top that shows what real users experienced. That is field data from the Chrome UX Report, covering the last 28 days. If it says the page passes the Core Web Vitals assessment, a red lab score is a to-do list, not an emergency. If it shows no data, that is common for small sites.

The PageSpeed Insights documentation sets "good" at the 75th percentile of visits: Largest Contentful Paint (when the main content appears) within 2.5 seconds, Interaction to Next Paint (how fast taps respond) within 200 milliseconds, and Cumulative Layout Shift (how much the page jumps) at 0.1 or less.

With too few visits, the report falls back to data for the whole site, and a small site may have none at all. Search Console's Core Web Vitals report also leaves out pages without enough data. No data is not a fail. It means you test it yourself.

What can you actually fix on Squarespace, WordPress or Shopify?

You control what you add: images, video, fonts, pop-ups and third-party widgets. On a hosted builder like Squarespace, you can't rewrite the platform's own code, so a "guaranteed 90+ mobile score" offer should make you skeptical. Fix the heavy items first and judge the result on real visits, not the lab number.

Start with the "Largest Contentful Paint element" in the report's diagnostics. It names the thing the test waited on. If it is your hero photo, shrink it. If it is a pop-up, cookie banner or background video, that is your first fix.

Squarespace's own page size guide gives clear targets:

  • Keep each page at 5 MB or less. 1 MB is the safest size for cellular connections.
  • Keep images under 500 KB, 1500 to 2500 pixels wide.
  • Keep a page to 60 blocks or fewer, and spread embedded videos across pages.

The same guide warns that on a CMS "some tools can return false negatives." On WordPress, look at plugins, theme and hosting. On Shopify, look at apps. Still choosing? See our Squarespace vs WordPress vs Shopify comparison.

How do you test speed the way a customer does?

Test the pages that make you money, on a phone, on cellular data. Use your top pages in Search Console, any page you send ads to, and your contact or booking page. Time how long until the headline and main button show up, then tap the phone number and send the form.

When we review a site before a rebuild or an ad campaign, we run this phone test before any speed tool. A slow form, a chat bubble covering the button, or a widget that pushes the page around costs leads, and a score won't show it.

Then list every add-on: chat, review and social feeds, booking embeds, maps, tracking pixels. Each one has to earn its spot. Remove one, retest three times, compare. Do the most with the least. Running ads? Fix your website first.

How long until your fixes show up?

The lab score updates as soon as you rerun the test. Real-user data takes longer, because it covers a rolling 28 days. Expect a fix to show up gradually over about four weeks. In Search Console, the Core Web Vitals report's validation check also runs a 28-day monitoring session before an issue is marked fixed.

Frequently asked questions

Is a PageSpeed Insights score of 50 bad?

Not by itself. Lighthouse grades each metric on a curve, where 50 matches the fastest quarter of real websites in the HTTP Archive dataset. Google calls 90 or above good, 50 to 89 needs improvement and below 50 poor. Check the real-user Core Web Vitals section and test the page on a phone before you spend money on it.

Why does my PageSpeed score change every time I run it?

The lab test is sensitive to internet routing, the hardware running it, and ads or A/B tests that change what the page serves. Lighthouse's own documentation says a lot of that variability is not caused by Lighthouse. Run the test three times on mobile, use the middle result, and compare changes the same way each time.

What does it mean when PageSpeed Insights shows no real-user data?

It means Google does not have enough visits from Chrome users to that page, or to the whole site, in the last 28 days. That is normal for new pages and many small business sites. It is not a fail. Use the lab results as clues and test the page yourself on a phone over cellular data.

Do you need to leave Squarespace to get a faster website?

Usually not. On Squarespace, the weight you control is images, video, fonts and add-ons. Squarespace recommends pages at 5 MB or less and images under 500 KB. Fix those first, then check real-user data. Switch platforms only if the business needs features Squarespace can't offer, not to chase a lab score.

Want help?

We build and fix websites for small businesses on Squarespace, WordPress and Shopify. If your score has you worried, we can check the pages that matter, tell you what is worth fixing and what to ignore, and fix it. Send us a note, or see our website and digital marketing services.

Updated November 2026. Thresholds and scoring reflect Google's PageSpeed Insights and Lighthouse documentation at the time of writing.

Next
Next

What Should a Small Business Do During a Google Core Update?