FreePageSpeed Insights + your phoneAbout 60 min
Make the Site Fast and Test It for Real
Speed is not a score to chase. It is how fast the page feels on a phone with a weak signal. You will fix the biggest slowdowns first and test them the same way every time.
Why This Matters
The worst speed mistake is a giant image at the top that loads last. Our own home page went from 80 to 97 on mobile speed once heavy sections only loaded when someone scrolled to them. We did not rebuild it. We stopped loading things nobody had seen yet.
✓ How To Do It
- Open PageSpeed Insights, which is free. Test your home page and write the mobile score and the three numbers named Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
- Google says good means 2.5 seconds or less, 200 milliseconds or less, and 0.1 or less, measured for most visits. Compare your numbers to those.
- Fix the top image first. Resize it to the size it shows on screen and save it as WebP or a compressed JPG.
- Do not lazy load the top image. Lazy loading should only apply to images below the first screen. Add the loading lazy attribute to those images.
- Give every image a width and a height in the HTML, so the page does not jump while images load.
- Find heavy sections below the first screen, like maps, videos, review widgets and chat boxes. Load them only when the visitor scrolls near them. A map can show a plain button that loads the map on tap.
- Remove scripts you do not use. Each old tracker and chat tool slows every visit.
- Run the test again and compare. Change one thing at a time so you know what helped.
- Test on a real phone with Wi-Fi off. Open the page and count how long before you can read it and tap the number.
- Repeat once a month. Speed slips when new photos and tools get added.
Done WhenSave the before and after PageSpeed Insights mobile results and a note of what you changed.
Reference List
Tips & Pitfalls
- Lab scores move a few points between runs. Look for a pattern across three runs.
- Real visitor data takes weeks to update. Do not panic if it lags.
- A fast page that hides the phone number is still a bad page. See Improve Core Web Vitals for more on the three numbers.