Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A 20/100 in PageSpeed Insights is a low Lighthouse score for one page under one simulated mobile test—not proof that WordPress itself is slow or that every visitor has a poor experience. The score alone cannot identify the cause. To find out what is happening, inspect the report’s individual metrics and audits, repeat a comparable test, and check real-user data separately.
What does a 20/100 mobile score actually measure?
PageSpeed Insights (PSI) reports Lighthouse performance analysis for mobile and desktop. The mobile score summarizes a synthetic, or lab, run in a controlled environment. It is useful for reproducing and investigating potential problems, but it cannot represent every visitor’s phone, connection, location, or interaction with the page. Google’s PSI explanation distinguishes Lighthouse lab analysis from field data collected from real Chrome users.
Where enough eligible data is available, PSI also displays Chrome User Experience Report (CrUX) field data. That data describes a distribution of real experiences, rather than the conditions of one test. PSI may show data for the specific page and, where available, the broader site origin. A page can lack enough data for a page-level field result even when origin-level context is available. Google’s explanation of PSI data covers this distinction.
Recommended Free Tools
Do not treat the composite score as a diagnosis. Open the report’s metric values and diagnostic audits to see what the run found. A low result does not, by itself, establish that a particular theme, plugin, host, or other WordPress component caused it.
Why might a WordPress site be slow on mobile?
Without the exact page and its report, the reason for a particular 20/100 cannot be determined. The score is a reason to investigate, not evidence pointing to one specific culprit. Depending on what the report shows, areas to check may include the theme, plugins, images, scripts, server response, caching, and content delivery. Treat these as hypotheses until site-specific measurements support them.
Start with the report’s actual findings. For example, a loading metric, a main-thread diagnostic, and a layout-stability metric describe different aspects of performance; they call for different follow-up checks. Confirm that a proposed change affects the relevant metric instead of assuming that a lower or higher overall score proves the cause.
How do you measure mobile speed so the result holds up?
- Test the exact public page. Enter its URL in PageSpeed Insights and select the mobile report. Record the page URL, date and time, report link or screenshot, and metric-level results. Do not compare a homepage test with a test of a different landing page.
- Repeat under comparable conditions. Treat each run as a sample, not as a permanent rating of the whole site. Compare individual metrics and diagnostic audits, not only the rounded score. Test conditions can vary with the network, device, location, cache state, redirects, and rendered content.
- Use lab results to investigate initial loading. Lighthouse can report Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Total Blocking Time (TBT). TBT can help you reason about a blocked main thread in a lab run, but it is not Interaction to Next Paint (INP). Lighthouse cannot measure INP without real user input. Google’s Web Vitals guidance explains the relationship between lab measurements and field metrics.
- Check what actual visitors experience. Review field data in PSI, Search Console, or a real-user monitoring (RUM) setup. Search Console’s Core Web Vitals report provides historical field reporting; field data and a Lighthouse lab run answer different questions. Google’s Search Console guidance describes its Core Web Vitals report.
- Evaluate changes with both kinds of evidence. After making a change, repeat the same lab process and watch field trends over time. Describe the lab result and real-user trend separately. A single before-and-after score does not establish that a change caused an improvement in visitor experience.
Which Core Web Vitals should you check?
Google’s current Web Vitals guidance, accessed October 7, 2026, gives these recommended “good” thresholds. Evaluate the 75th percentile separately for mobile and desktop; these are metric targets and a measurement percentile, not population averages. Google’s Web Vitals guidance provides the definitions and assessment method.
| Metric | What it describes | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading performance | 2.5 seconds or less |
| Interaction to Next Paint (INP) | Responsiveness to user interactions | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability | 0.1 or less |
Lab and field results are complementary. Google’s web.dev guidance puts it this way: “While all of the Core Web Vitals are, first and foremost, field metrics, many of them are also measurable in the lab.” The guidance on Web Vitals explains why lab tests help with diagnosis while field data is needed to assess real-user experience.
How do you compare two PageSpeed results fairly?
Before deciding that a score changed meaningfully, check that the reports match on the dimensions that shape their interpretation:
- Measurement type: Lighthouse lab run versus CrUX or RUM field data.
- Device segment: mobile versus desktop.
- Scope: the exact page versus the site’s origin-level data.
- Time and sample: one controlled test versus a field distribution collected over time.
- Metric: loading (LCP), responsiveness (INP; TBT is only a lab aid), or visual stability (CLS).
PSI can vary between runs, so retain the report details and conditions rather than relying on a single rounded number. Google’s PSI explanation describes the lab and field distinction; the report’s metric details are more useful for investigation than an isolated score. Google PageSpeed Insights.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What should you conclude from a low score?
A 20/100 mobile result says the tested page performed poorly in that Lighthouse run. It does not, alone, show how all visitors experience the site or identify what caused the result. Use the report to select a metric and a plausible site-specific check, then compare like-for-like lab runs and consult field data before drawing conclusions about real-user performance.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
