Website speed and Core Web Vitals
How do you check website speed with PageSpeed Insights?
Test your website on mobile and desktop, read the performance report, and identify loading problems. Learn how lab tests differ from real-user data.

Is your website slow on a phone?
- ◷Loading / LCP
- ◷Interaction / INP
- ◷Stability / CLS
PageSpeed Insights basics
What you need to know
Start with what the tool does, when to use it, and the first thing to check.
- 01Plain answer
- PageSpeed Insights shows how a page performs for real users and lab tests, especially on mobile where impatient buyers don't care about your giant hero video.
- 02Best for
- Businesses with slow service pages, heavy images, clunky mobile layouts, or ads sending paid traffic to pages that take too long to load.
- 03First move
- Test your homepage, top service page, and main landing page on mobile. Don't stop at the homepage.
What is PageSpeed Insights?
PageSpeed Insights is a Google tool that tests a page and reports on performance, accessibility, best practices, SEO basics, and Core Web Vitals. It gives lab data and, when available, real-user field data.
- Performance is about speed and loading behavior.
- Accessibility checks whether people can use the page more easily.
- Best Practices catches some technical and security basics.
- SEO checks basic crawl and page structure items.
- Core Web Vitals measure loading speed, visual stability, and responsiveness.
Why does website speed matter on a phone?
If your website is slow or jumpy on mobile, buyers notice. They may not know the words Core Web Vitals, but they know when a site feels broken and annoying.
- Slow pages can hurt trust.
- Paid ad traffic gets more expensive to waste on a weak page.
- Mobile experience matters because many local searches happen on phones.
- Technical issues can make good content harder to use.
What do PageSpeed scores and Core Web Vitals mean?
- Performance score for the tested page.
- Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift.
- Image, JavaScript, CSS, and font issues that may slow the page down.
- Accessibility warnings like contrast, labels, and document structure.
- Basic SEO checks such as title, meta description, crawlability, and mobile viewport.
How do you test a page with PageSpeed Insights?
- 01
Go to PageSpeed Insights and test your homepage.
- 02
Test one important service page, not just the homepage.
- 03
Switch between Mobile and Desktop results.
- 04
Look at real-user data if available, then lab data.
- 05
Review Opportunities and Diagnostics, but prioritize issues that affect real users.
- 06
Check image size, render-blocking scripts, layout shift, and mobile usability first.
What mistakes should you avoid when checking speed?
- Testing only the homepage.
- Obsessing over a perfect score instead of fixing real friction.
- Ignoring mobile because desktop looks fine.
- Adding tracking and chat widgets without checking how they affect loading.
- Compressing images so badly the work looks cheap.
What should you fix on a slow website first?
- Optimize large images without ruining quality.
- Remove scripts you don't need.
- Fix layout shift around images, fonts, and embeds.
- Test service pages and landing pages.
- Pair speed cleanup with stronger copy and calls to action.
Why do lab scores and real-user data differ?
A Lighthouse lab run is a controlled diagnostic. PageSpeed field data, when available, reflects real-user data across a rolling 28-day period. Record whether the field result covers the URL or the origin. Missing field data isn't a pass or a failure. Compare repeatable lab conditions and validate changes on actual screens. A score doesn't establish rankings or leads.
Screenshot checklist
What should you screenshot before asking for help?
A good screenshot makes the conversation concrete. It shows whether the tool is set up, whether the numbers are useful, and where the next fix should start.
- 01Mobile score for homepage and top service pages.
- 02Core Web Vitals status if field data exists.
- 03Largest Contentful Paint details.
- 04Image size and format warnings.
- 05Unused JavaScript and third-party script warnings.
- 06Accessibility and SEO checks that affect real buyers.
Example problems
What problems might you find?
Each example shows a problem, what it might mean, and what to check.
A page loads slowly on a phone
- What happens
- The desktop site looked expensive, but the mobile page loaded slowly and pushed the call button too far down.
- What it means
- The design was doing showroom work while the sales path limped.
- The move
- Compress images, simplify above-the-fold assets, and make the main action obvious on mobile.
Tracking scripts slow down a service page
- What happens
- A landing page carried old scripts from vendors that weren't even working on the account anymore.
- What it means
- Dead scripts can slow pages and muddy tracking.
- The move
- Remove old tags, test what remains, and retest the page after cleanup.
Tasks to work through
What can you check yourself?
Work through these checks in order.
- 01
Test the pages people actually land on, not just the homepage.
- 02
Fix oversized images before chasing tiny technical scores.
- 03
Give images stable dimensions so mobile layouts don't jump around.
- 04
Remove scripts you don't use.
- 05
Retest after changes and compare the buyer experience, not just the score.
Free 30-minute call
Need help with your website or Google profile?
We’ll discuss your website, profile, or measurement questions and identify a useful next step. Thirty minutes, no commitment. Advertising guides are educational; paid campaign management isn’t an advertised service here.


