Making your webshop faster
Your webshop is usually slow because of heavy images, too many plugins and scripts, and cheap or overloaded hosting. First measure where the time is being lost, then tackle the biggest bottleneck, starting with images and unused extensions.
A slow webshop costs you visitors and orders, because nobody likes waiting for a product page that only half loads. Yet the cause is rarely one single thing. Usually small problems pile up: a heavy homepage, extensions you never use and a server that struggles with busy periods. In this article you will read why a shop becomes slow, how to find the cause and which measures deliver the most.
Why a webshop is slower than an ordinary website
A webshop does much more work per page visit than a simple information site. With every request, the server retrieves products, prices, stock and often customer data from the database. A shopping basket and a checkout page are also personal, so they cannot simply be reused as ready-made pages.
On top of that, a shop often grows. You start with twenty products and a simple theme, and after a year you have hundreds of items, filters, reviews, links with an accounting package and a pile of marketing scripts. Every component costs a little loading time. The problem rarely appears all at once, but creeps in.
Measure first before you change anything
Many owners start guessing: a different host, a new theme, another cache plugin. It costs time and afterwards you don't know whether it helped. So measure first. Use a free speed test and look at the homepage, a category page, a product page and the checkout page separately, because they can perform completely differently.
In the results, look at three things: how long the server takes to respond, how big the page is in total and which files load slowest. Write down the results. After every change you measure again, so you can see what really had an effect and what only gave a feeling of progress.
- Test at least four different page types
- Also test on a mobile connection, because that is where most of your visitors are
- Note the results before and after every change
Images: the most common cause
Product photos are often the heaviest part of a page. A photographer or supplier delivers files of several megabytes, and they go into the system unchanged. A visitor on a phone then downloads an image that is many times larger than the screen can display. This way, a single category page with twelve products can suddenly become very heavy.
So reduce photos before you upload them, to the size your theme actually uses. Choose a modern file format if your platform supports it and let images load only when they come into view. A practical example: a clothing shop with large lifestyle images at the top of every category often gains a lot of time just by reducing those images.
Plugins, apps and external scripts
Every extension you install usually loads its own code, even on pages where you don't need it. A plugin for a pop-up, a review widget and a chat window can together add several extra files and external connections. With WooCommerce there is also database work on top, with Shopify mainly extra scripts from apps.
So go through your list of extensions. Remove what you don't use, rather than just switching it off. Check whether two extensions do the same thing, such as two statistics tools. A common mistake is installing a trial app, deciding not to use it and leaving the remnants behind. Old tracking codes from campaigns that stopped long ago also keep loading unnecessarily.
Hosting and platform
With a hosted solution such as Shopify you have little influence over the server, and the gains lie mainly in the theme, images and apps. With WooCommerce or another self-hosted system, hosting is a big factor. On shared hosting you share computing power with other websites, and when it gets busy, such as during a sale, speed drops.
Look at the server response time in your measurement. If it is high even at a quiet moment, the cause is often the hosting, an outdated PHP version or a heavy database. Ask your hosting provider which version is running and whether caching is available. An upgrade to a bigger package only helps once you have cleaned up the rest, otherwise you pay for a problem that remains.
Caching, database and maintenance
Caching ensures that pages that are the same for everyone are not rebuilt with every visit. This works well for category pages and blog articles. Do note: the shopping basket, checkout and login pages must not be cached, otherwise customers see each other's data or the wrong basket. After setting it up, always check yourself that an order goes through normally.
The database also needs maintenance. Old drafts, expired sessions and log files accumulate and make queries slower. Schedule a regular moment, for example every quarter, for cleaning up, updates and a check of the loading time. Always make a backup before major changes, so you can go back if something goes wrong.
How to start tomorrow
Start small and in this order: measure the four most important pages, reduce the heaviest images, remove unused extensions and then check the hosting. This way you first take the measures that cost little and often deliver the most. Only once that is done does it make sense to think about a new theme or a different server.
Finally, keep your own visitors in mind. A shop that sells mainly via mobile benefits more from light pages than from a fast server. Check in your statistics which devices your customers order on and test those first. This way you spend your time on improvements that actually affect your revenue.
More on Webshoptiger
Frequently asked questions
How fast should a webshop load?
There is no fixed limit, but the faster the better, especially on mobile. Compare your own measurements before and after a change and pay attention to the pages where customers drop off, such as category and checkout.
Is a new theme the solution?
Sometimes, but often not. A heavy theme can play a part, but images and extensions are more often the cause. Measure first and only change theme if the results show that the theme is the bottleneck.
Does more expensive hosting always help?
No. It helps if the server response time is high because of shared capacity. If your page is heavy because of large files and many scripts, it will stay slow, even on a powerful server.
How often should I check the speed?
Measure at least after every major change, such as a new extension or a campaign with a lot of imagery. In addition, a fixed check every quarter is a practical rhythm.