Why your business site loads slowly on a phone, and how to test it for free

Measure your site with PageSpeed Insights

A customer who looks you up on a phone often has a weak signal, a small screen and one free hand. A site that feels fine on your office computer can take much longer to load for that person. I build and fix websites for local businesses around Tuscaloosa. Google offers a free tool called PageSpeed Insights at pagespeed.web.dev. Paste in your home page address and press Analyze. The report opens on the Mobile tab, which is the one that matters for customers on phones.

Look at Largest Contentful Paint first. It measures how long the biggest piece of the page, usually a photo or a headline, takes to appear. Google rates 2.5 seconds or less as good. If your site has enough visitors, the top of the report also shows data from real Chrome users. Below that, a lab test lists specific problems under headings such as Diagnostics.

Run the test on your home page and on your busiest inner page, such as the menu or the services page. Write down the Largest Contentful Paint for each so you can compare after any fix.

Cause one: photos far larger than the screen

A photo straight from a modern phone camera can be several megabytes and thousands of pixels wide. A phone screen shows it at a few hundred pixels wide. When a site serves the full file, every visitor downloads data they never see.

PageSpeed Insights flags this under items such as Properly size images or Improve image delivery. To fix it, resize each photo to roughly the largest width it appears on your site, then compress it. Squoosh, a free tool at squoosh.app, does both in the browser and can save the file as WebP, a format that most browsers support and that usually comes out smaller than a JPEG.

If your site runs on WordPress, an image optimization plugin can resize and compress photos as you upload them. Pick one plugin for this job and remove any others that overlap.

Cause two: plugins and add-ons that load on every page

Each plugin, chat widget, social feed or slideshow can add its own scripts and styles. Many of them load on every page, including pages that never use them. A site with a long list of plugins makes a phone download and run all of that code before the page settles.

In the PageSpeed report, look for items about unused JavaScript and render-blocking requests. The details often name the plugin or service that added the file.

Open your plugin list and deactivate anything you no longer use. Then deactivate one plugin at a time, run PageSpeed Insights again, and note whether the score moves. Back up the site before you start so you can restore it if a page breaks.

Cause three: hosting that responds slowly

Before a page can load, your hosting server has to answer the request. On a crowded shared hosting plan, that first answer can take a long time no matter how small your photos are.

PageSpeed Insights flags a slow server response in its list of problems, and the field data section shows a measure called Time to First Byte. A free tool called WebPageTest at webpagetest.org shows the same thing as the first bar in its waterfall chart.

If the server response stays slow after you fix photos and plugins, ask your host whether your plan includes caching and whether a faster plan or a content delivery network is available. Some hosts turn on caching with one setting in the control panel.

Fix in this order

Start with photos, because resizing them takes no technical skill and often makes the largest change. Move to plugins next, testing after each change. Look at hosting last, since it may involve a new plan or a move.

Run PageSpeed Insights again after each step and compare the new Largest Contentful Paint with the number you wrote down. That record shows you which change made the difference.