If your small business website is slow on mobile, the cause is usually one of four things: oversized images, too many plugins and scripts, weak hosting without caching, or fonts and layout that shift while loading. Test on a real phone, fix the biggest problems first, and measure again to prove the change.
Why a small business website is slow on mobile: test on a real phone first
A site can feel instant on an office computer and crawl on a phone. Phones have less processing power than a desktop, and mobile connections vary, particularly outside the main cities. So test the way customers experience it.
- Open the site on an ordinary mid-range phone using mobile data, not your office wifi.
- Note what you see: how long until something appears, until the main content is visible, and until buttons respond when tapped.
- Run a free testing tool such as the page speed reports built into common browsers, using the mobile setting. They use field data from real visitors where available and lab data where it is not, so read both.
- Look at the three Core Web Vitals: how quickly the main content appears, how stable the layout is, and how fast the page responds to taps and clicks.
- Save the starting results and screenshots. You will want them later.
Test a few key pages, not only the home page: the most visited page, a service page and the contact page.
Images: the usual culprit
Photos taken on a modern camera or phone are often several times larger than the space they fill. Uploading them straight to the site makes pages heavy.
- Resize images to the largest size they will actually be displayed at, allowing for sharp screens.
- Use modern formats where your platform supports them, and compress sensibly.
- Use responsive images so phones download smaller versions than desktops.
- Lazy-load images below the fold, but do not lazy-load the main image at the top.
- Set width and height attributes so the browser reserves space.
- Replace heavy background videos and sliders with a single well-chosen image.
This is often the quickest and most effective improvement, and it needs no programming on most platforms.
Plugins and scripts
Every plugin, widget and tracking tag can add code that the visitor's phone must download and run. Common offenders include page builders, sliders, social feeds, chat widgets, multiple analytics tags and ad pixels.
- List everything the site loads. Browser developer tools show requests and their sizes.
- Remove what you do not use. Deactivated plugins can be deleted; unused tags should go.
- Replace heavy plugins with lighter ones, or with a small amount of custom code.
- Load non-essential scripts after the main content, or only on pages that need them.
Plugins do slow WordPress sites when they add scripts, styles and database queries on every page. Quality matters more than count, but fewer is nearly always better. If you run an online shop, our WooCommerce performance guide covers store-specific issues, and fast mobile product pages looks at product pages.
Hosting and caching
Cheap shared hosting can mean a slow response before the page even starts to load. The time between a request and the first byte matters, particularly when your visitors are in Australia and your server is on another continent.
- Choose hosting with servers near your customers, or use a content delivery network that serves files from nearby locations.
- Turn on page caching so the server sends saved pages instead of rebuilding them each time.
- Keep PHP and the database on supported versions; they are usually faster as well as safer.
- Enable compression and browser caching for static files.
- Check that backups and scans are not running during business hours.
Hosting changes need care. Take a backup, test on a copy and confirm email, forms and redirects still work after any move.
Fonts and layout shift
Layout shift happens when elements move while the page loads, such as a button jumping just as you tap it. Slow fonts can also cause text to flash or reflow.
- Limit the number of font families and weights. Each is another file to download.
- Host fonts on your own domain where licensing allows, and use a font-display setting so text appears immediately with a fallback.
- Reserve space for images, embeds, ads and cookie banners so they do not push content down.
- Avoid inserting content above existing content after the page loads.
Our deeper look at fixing Core Web Vitals on custom websites explains each metric in more detail.
Fix order by impact
With a long list, work in this order, checking the result after each step:
| Step | Effort | Likely benefit |
|---|---|---|
| Compress and resize images | Low | Often large on image-heavy pages |
| Remove unused plugins and tags | Low | Fewer requests, less code to run |
| Turn on caching and compression | Low to medium | Faster server response |
| Reserve space, simplify fonts | Medium | More stable layout |
| Upgrade hosting or add a CDN | Medium | Helps all pages when the server is the bottleneck |
| Replace the theme or rebuild templates | High | Worth it when the foundation is the problem |
Take the simple, cheap steps first. Only consider a rebuild when the theme or page builder itself is the cause, a question we explore in redesign or rebuild.
Proving the improvement
After each change, test the same pages in the same way and compare with your saved baseline. Lab tests vary from run to run, so repeat them and look at the trend. Field data takes longer to update, so give it time.
Also look at business signals: bounce rate on mobile, form submissions, phone-call taps and sales. A speed improvement should show up somewhere your business cares about. Put the checks into a recurring routine, as described in what a website maintenance plan should include, because speed drifts as content, plugins and scripts are added.
Next step
Begin with a phone test, record the results, then work through images, plugins, hosting and fonts in that order. If you would like a second opinion on a slow site, see our software development in Australia page or get in touch through the contact page.
Frequently asked questions
Why is my site fast on desktop but slow on mobile?
Phones have less processing power and often use slower or less stable connections. Large images, heavy scripts and layouts that need a lot of work to display hit them harder. Test with a real phone on mobile data and use the mobile setting in speed tools.
Do plugins slow a WordPress site?
They can. Plugins often load extra scripts, styles and database queries on every page, and several overlapping ones add up. Quality matters as much as quantity. Remove what you do not use, replace heavy ones with lighter options, and test speed before and after changes.
What is layout shift?
Layout shift is when page elements move unexpectedly while the page loads, such as text jumping down as an image appears, or a button moving as you tap. It is caused by missing image sizes, late-loading fonts and injected content, and it is measured as part of Core Web Vitals.