I wrote about Core Web Vitals earlier. This post is the practical side: how to run a test yourself and decide what to fix.
Step 1: Pick the right pages
Don’t just test your home page. Test the pages that matter most:
- Your home page
- Your top service page
- The page your Google Business Profile links to
- Any landing page you send ads to
Step 2: Run PageSpeed Insights
Go to Google’s PageSpeed Insights, enter the page address and run the test. Start with the mobile results. Most of your customers search on phones, often on a cell signal, so mobile is the result that matters most.
Step 3: Read the top section first
The top section shows real-visitor data, if Google has enough of it, labeled as what your real users are experiencing. It reports the three Core Web Vitals and whether the page passes:
| Metric | Good |
|---|---|
| Largest Contentful Paint (LCP) | 2.5 seconds or less |
| Interaction to Next Paint (INP) | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | 0.1 or less |
If you pass here, your page is in good shape for real visitors. If there’s no field data, your site may not have enough traffic yet; use the lab section instead.
Step 4: Use the lab section to diagnose
Below that is a lab test with a score from 0 to 100 and detailed findings. The score is useful as a rough guide, but don’t obsess over it. The useful part is the list of opportunities and diagnostics, which tells you what’s slowing the page down.
Common findings and what they mean:
- “Properly size images” or “Serve images in next-gen formats.” Your images are bigger than they need to be. Resize and convert them to WebP or AVIF.
- “Reduce unused JavaScript.” The page loads code it doesn’t use, often from page builders, sliders, chat widgets or tracking tools.
- “Eliminate render-blocking resources.” Files must load before anything shows. Usually stylesheets and scripts in the wrong place.
- “Reduce initial server response time.” Hosting is slow, or the server does a lot of work to build each page.
- “Avoid large layout shifts.” Something moves while loading, often images without set sizes or late banners.
Step 5: Fix the biggest wins first
Start where the effort is small and the impact large:
- Compress and resize images
- Remove widgets and plugins you don’t use
- Delay chat widgets and non-essential scripts until after the page loads
- Give images set dimensions
- Look at hosting, especially if server response is slow
Step 6: Retest
After each change, run the test again. Lab results vary, so run it two or three times and look at the trend. Real-visitor data in the top section and in Search Console updates more slowly, over a few weeks.
Watch it over time
In Google Search Console, the Core Web Vitals report groups pages into good, needs improvement and poor based on real visitors. Check it monthly, and after any big website change.
When to fix vs. rebuild
Some sites can be fixed with image work and plugin cleanup. Others are built on heavy themes or page builders that will never be fast without starting over. If you’ve done the easy fixes and still fail on mobile, a rebuild may be cheaper than more patching. Our page speed optimization service tells you which situation you’re in, and our website audit covers speed along with SEO and conversion.
A quick speed checklist
| Check | Good sign |
|---|---|
| Mobile Core Web Vitals | Passing in field data |
| Images | Sized to display and in WebP or AVIF |
| Scripts | Only what the page needs, chat and tracking delayed |
| Hosting | Fast server response, served from a CDN |
| Layout | Nothing jumps while the page loads |