My PageSpeed score is low. Should I worry?
Not on its own. The 0 to 100 score is a lab test on one simulated phone, and it moves between runs. What matters more is the real-visitor section above it: if your Core Web Vitals pass there, most real visitors are fine. If they fail, or there's no field data, fix the largest items the report lists first.
The short version
- PageSpeed Insights shows two things: real-visitor data at the top and a lab score below it.
- Real-visitor data (Core Web Vitals) matters most. If it says “passed”, relax.
- The lab score comes from one simulated phone and varies from run to run.
- A low lab score is a to-do list, not an emergency.
- Fix the biggest items first, usually images, scripts and hosting.
How do I read the report?
Google’s About PageSpeed Insights page explains the two halves.
Field data comes from real Chrome users over the previous 28 days. It shows your Core Web Vitals: LCP, INP and CLS. Each is rated Good, Needs Improvement or Poor. Small sites often don’t have enough visits for this section to appear.
Lab data comes from Lighthouse, which loads the page once on a simulated mid-range phone over a mobile network. That’s where the colored score comes from:
| Score | Google’s rating |
|---|---|
| 90 to 100 | Good |
| 50 to 89 | Needs improvement |
| Below 50 | Poor |
The same page says a good lab score doesn’t guarantee a good real-user experience, and the reverse is true too.
When should a low score worry me?
- Field data failing: yes, worth fixing. Real customers are waiting.
- No field data and a red lab score: take it seriously. It’s your best clue about phone visitors.
- Field data passing, lab score amber: lower priority. Most measured visitors get a good experience, but the pass is based on the 75th percentile, so check any problem a customer reports.
- Desktop green, mobile amber: normal. The phone test is far stricter.
Why does it matter?
Speed on a phone is often the first impression a local customer gets. A page that takes a long time to show its main content loses people before they read a word. Real-visitor Core Web Vitals are also part of Google’s page experience signals.
What usually drags the score down?
- Oversized images, especially the big photo at the top. See how big images should be.
- Scripts on every page: chat widgets, sliders, tracking tags and social feeds. See how many plugins is too many.
- Slow hosting or no caching, which shows up as a slow server response.
- Heavy themes or page builders that load lots of code.
- Embedded maps and videos loaded before anyone asks for them.
What are the common mistakes?
- Removing things customers need, like the booking tool or contact form, just to gain points.
- Judging from one run. Test three times and compare.
- Testing only the home page. Check your busiest service page and your contact page too.
- Installing a “speed plugin” on top of other speed plugins. Overlapping caching tools can break pages.
What if the score didn’t improve after fixes?
The lab score should move on the next run. Field data takes up to 28 days to reflect a change. If neither moves, the problem is probably the server or a script you can’t see. Our help article on why a website is slow walks through the next checks.
How much does it cost, and how long does it take?
Testing is free and takes about a minute. Image and plugin cleanups are often quick. Hosting changes or replacing a heavy theme take longer and usually need a developer.
How does E-3 handle this?
Speed work is part of E-3’s speed program, and speed fixes are tested on a staging copy first. Try the free speed test for a plain-English version of your report.
Related questions
Common questions
- Why does my score change every time I test?
- Google's PageSpeed documentation says lab results vary with network conditions, hardware and resource contention on the test machine. Run it a few times and look at the trend, not one result.
- Do I need a perfect 100?
- No. Google rates 90 to 100 as good, but a site whose real visitors pass Core Web Vitals is doing fine. Chasing the last few points rarely pays off.
- Why is my mobile score so much lower than desktop?
- The mobile test simulates a mid-range phone on a mobile network, which is much tougher than the desktop test's wired connection. Most local customers are on phones, so the mobile result is the one to watch.
Rather talk it through?
Call our team, or send a note and we’ll reply within one business day. No pressure and no jargon.