Google’s PageSpeed Insights gives the mobile home page a low performance score. Slow pages lose visitors, and real visitors’ Core Web Vitals often follow the lab score down.
What it means
PageSpeed Insights loads the home page on a simulated phone in Google’s data centre and scores it out of 100. A score below 50 is poor. The action shows the score with the Largest Contentful Paint, total blocking time and layout shift that went into it.
What triggers it
The Lab performance service tests each mobile home page once a week, using the same Google API key as Core Web Vitals. A score below 50 raises a Medium issue, and owners and admins get a “Critical issue alert” email the first time it’s found.
Common causes
- Large or uncompressed images, especially the main image at the top of the page.
- Too many scripts, such as trackers, chat widgets, sliders and plugins, blocking the page while it loads.
- Slow hosting, no caching, or web fonts loaded in a way that delays text.
How to fix it
- Open PageSpeed Insights for the home page and read the full report.
- Start with the opportunities that save the most time, such as image sizes and unused JavaScript.
- Retest in PageSpeed Insights after each change; lab scores vary by a few points between runs.
When it clears
The issue goes at the next weekly test that scores 50 or more. A sudden fall has its own issue; see Lab performance dropped.
After 7 days without the problem, the action drops off the board. If you marked it done and the problem is still detected 14 days later, it returns as “Fix didn’t work”.