What a slow ecommerce store costs you
Speed is not a technical detail; it is a line in your accounts. According to Google data, the probability that a visitor leaves a page grows by 32% when load time stretches from one to three seconds. More than half of mobile users leave if a page takes longer than three seconds to load. And most ecommerce traffic today comes from mobile.
Do the math with us. A store with revenue of CZK 300,000/month that loses a tenth of its visitors to slow loading gives up tens of thousands of crowns a year. On top of that, Google factors store speed into search rankings. A slow site pays twice: in lost customers and in worse search positions.
Measure your store’s speed in two minutes
Before you change anything, measure. Open PageSpeed Insights (Google’s free website speed tool), enter your store’s address and wait for the result. Focus mainly on the mobile tab; that is where the score is usually worst and where most of your visitors are.
Two numbers matter most. The first is LCP (the time it takes for the main content of the page to appear); up to 2.5 seconds is fine. The second is server response time, or TTFB (the time before the server sends the first data, i.e. before it starts answering at all); under 200 milliseconds is excellent, over 800 milliseconds is a clear problem. Measure the homepage, one category and one product. Ideally around eight in the evening, when the most people are shopping and the server is under load.
Why the store is slow: three server-side causes
The first group of causes sits where you normally cannot see, on the server.
- Overloaded shared hosting. On cheap hosting you share one server with hundreds of other websites, like an apartment block with a single water pipe. When a neighbour turns on the tap, you get a trickle. Telltale sign: the store is slow mainly in the evening and before Christmas, exactly when you sell the most.
- Slow database. The database is the warehouse of all your products, orders and customers. Without maintenance it grows and searching it takes longer, like a warehouse nobody has tidied for years. Typical symptom: a filtered category listing takes several seconds while static pages stay snappy.
- Missing cache. A cache is a ready-made copy of a page that the server delivers instantly instead of assembling it from the database for every visitor. A store without a server cache does the same work a thousand times a day. The difference usually shows at first glance in the server response time.
Four causes on the website side
The second group of causes lives directly in your store. You can reach these even without a server administrator.
- Heavy images. The most common and cheapest fix of all. A product photo straight from the camera can easily be 5 MB; after resizing and converting to WebP (an efficient image format for the web) it is 150 kB. A category page with thirty such photos then loads in one second instead of ten.
- Overloaded theme. A theme packed with animations, big banners and effects looks great in the demo, but every visitor has to download all of it. Multipurpose themes also load code for features you never use.
- Too many plugins and scripts. Chat, heatmap, three tracking codes, a pop-up and product reviews; every add-on brings its own files to the page. Ten third-party scripts can delay loading by several seconds even when the server answers instantly.
- Old PHP version. PHP is the programming language behind WordPress, WooCommerce and Prestashop. Newer versions process the same page noticeably faster, and old versions are losing security support. You can find the version in your hosting control panel; if you see the 7.x line there, it is time to upgrade.
How to speed up your store: what you can do yourself and when the problem is infrastructure
Images, plugins and a basic cache are things a store owner can handle alone or with their web developer. Start with the images; the effort-to-result ratio is usually best there.
Elsewhere you will hit a wall. If the store has a high server response time even with caching on, slows down at peak times, or the hosting does not offer a current PHP version, the problem is not the website but the infrastructure. No amount of image optimization will fix a server that cannot keep up. In that situation the answer is a move to faster hosting; with our hosting plans (from CZK 550/month) we handle the migration free of charge and without downtime, so customers notice nothing. Stores with us run in a Prague TIER III datacenter (an independently certified reliability standard) and our admins respond within hours, not days. And if you have your own server and simply nobody tunes its performance, we offer server management at CZK 1,500/hour; a typical initial intervention, i.e. setting up caching and updating PHP, takes a few hours.
Checklist: find your store’s bottleneck today
- Measure the store in PageSpeed Insights: homepage, a category and a product. Write down the mobile score and the server response time (TTFB).
- Repeat the measurement in the evening between 7 and 9 p.m. If the results are noticeably worse than in the morning, that points to overloaded hosting.
- Check the images: right-click a product photo, save it and look at the file size. Resize anything over 300 kB and convert it to WebP.
- Go through your list of plugins and add-ons. Disable everything you have not used for six months and watch whether the site gets faster.
- Verify that caching is on: either in the store settings, via a plugin, or at server level (ask your host).
- Check the PHP version in the hosting control panel and have it raised to a currently supported line.
- Measure the store again and compare with the first run. If the server response stays above 800 milliseconds, the problem is the hosting and it is time to deal with the infrastructure.
Find out what is slowing your store down
Send us your address and within a few days you will get a free speed audit report: what exactly slows the store down and what to do about it. No obligation.