Slow Website, Lost Orders: Why Speed Matters More Than You Think

The Friday Night Problem

It is 7:15pm. Someone is standing in their kitchen, hungry, phone in hand. They search "pizza takeaway [your town]", tap your link, and wait. The screen stays white. They wait a beat longer. Then they tap back and click the next result.

That is not a hypothetical. That is how most takeaway websites lose orders every single Friday and Saturday night — the two busiest sessions of the week. Not to a better pizza or a lower price. To a faster page.

Google's own research found that the probability of a visitor bouncing — leaving without doing anything — more than doubles when a page takes longer than three seconds to load. On mobile, where most of your customers are searching, it is even less forgiving. Most people will not give a slow site a second chance.

Speed is not a technical nicety. It is the difference between a collected order and an empty seat.

Why Google Ranks Slow Sites Lower

Google officially uses page experience as part of its ranking system. That includes a set of measurements called Core Web Vitals — three numbers that describe how fast a page loads, how quickly it becomes usable, and whether elements jump around as it loads.

You do not need to memorise the jargon. What matters is the practical outcome: a site that loads slowly, or that shifts and flickers while loading, is treated by Google as a worse experience for users. Google rewards the better experience with higher placement in search results.

For a takeaway website, that means a slow site is working against you twice. It loses visitors who land on it. And it appears lower in results, so fewer visitors find it in the first place.

Google's guidance is consistent on this: fast sites, built for mobile, with content that is easy for search engines to read, outperform slow, clunky alternatives — all else being equal. This is one reason Takely builds sites with real, searchable menu text rather than PDFs or image scans. Speed and searchability go together. See also why PDF menus are invisible to Google for what that costs you on a separate but related front.

The Usual Culprits on Takeaway Sites

Most slow takeaway sites share the same handful of problems. Here are the ones we see most often.

• Oversized menu photos. A single uncompressed photo from a modern phone can be 5–8MB. A menu page with ten of those is 80MB. That takes a long time to load even on a decent connection, and on a 4G signal in the middle of town it can feel glacial. The fix is image compression and serving properly sized files — not removing photos altogether. Photos still sell; they just need to be optimised.
• Bloated page builder plugins. WordPress sites built with Elementor, Divi, or similar tools load dozens of CSS and JavaScript files that the page does not actually need. The builder generates beautiful layouts in the editor, but the output is heavy code that browsers have to parse before anything appears on screen.
• Cheap shared hosting. A £3/month hosting plan puts your site on a server shared with hundreds or thousands of other websites. When those sites spike — around dinner time, for instance — your site slows down. The server is simply not fast enough to respond quickly under load.
• No caching or CDN. Every time someone visits the site, the server generates the page fresh. A basic caching setup stores a ready-made copy and serves it instantly. Without it, every visitor waits for the full build process.
• Render-blocking scripts. Some plugins and third-party tools (chat widgets, booking systems, cookie banners) load before the page content, blocking the visible page from appearing. The visitor sees white space while scripts run in the background.
• PDF or image menus. A menu embedded as a PDF or a scanned image is one more large file to load — and it contributes nothing to searchability. Text menus load faster and rank better.

How to Test Your Own Site Free (No Tech Knowledge Needed)

Google offers a free tool called PageSpeed Insights. Here is how to use it without needing to understand anything technical.

1. Open a browser and go to pagespeed.web.dev
2. Type your website address into the box and press Analyse
3. Wait about 30 seconds. The tool loads your site several times and measures the experience.
4. You will see two tabs: Mobile and Desktop. Click Mobile first — that is where your customers are.
5. Look at the score out of 100 at the top. Above 90 is good. 50–89 needs work. Below 50 is costing you orders.
6. Scroll down to the Diagnostics section. Each item listed is a specific problem. The ones flagged red or orange are the ones that matter most.
7. The "Largest Contentful Paint" number tells you how long before the main content appears on screen. Aim for under 2.5 seconds.
8. The "Cumulative Layout Shift" score tells you how much the page jumps around while loading. Any score above 0.1 is disruptive to users.

You do not need to fix the issues yourself. But knowing your score gives you something concrete to ask any web designer about. If a developer cannot explain what they will do about your PageSpeed score, that is worth knowing before you hire them.

If you want a quick sense of whether visitors are even staying long enough to interact, the five-second test is a useful companion check — speed and first impressions often fail together.

What a Good Score Actually Looks Like

Here is a rough guide to what the numbers mean in plain English.

Most takeaway websites built on generic templates or cheap shared hosting score in the 20–50 range on mobile. That is not a design flaw — it is a build flaw, and it is fixable.

Common Mistakes That Make This Worse

A slow site is bad. A slow site with these additional issues is worse — and they are surprisingly common.

• Uploading a new menu photo every month without compressing it first. The folder fills up with 6MB images and the page weight doubles.
• Installing every plugin suggested in a WordPress tutorial. Each one adds code. Twenty plugins is twenty code libraries loading on every page visit.
• Using a full-screen background video on the homepage. Video files are enormous. They will bring a mobile connection to its knees.
• Embedding a live Google Maps widget. This triggers a full Google Maps script load, which adds significant weight to every page it appears on.
• Linking to a PDF menu instead of displaying menu text on the page. Visitors have to wait for the page to load, then wait again for the PDF.
• Not testing on a real mobile device. Sites that look fine on a desktop computer on a fast office Wi-Fi often fail badly on a phone with a 4G signal.

Several of these also overlap with the design mistakes that kill conversions in general. If you want a fuller list, common takeaway website mistakes covers the broader picture.

What a Fast Takeaway Site Looks Like in Practice

Speed does not mean a plain, ugly site. It means a site built with the right priorities.

• Images compressed to under 200KB each, served in modern formats (WebP), and sized for the screen they will appear on
• Menu items written as real HTML text — searchable by Google, readable by screen readers, fast to load
• Hosted on fast, UK-based servers (not a shared plan splitting resources with hundreds of unrelated websites)
• Minimal third-party scripts — no unnecessary chat widgets, pop-ups, or cookie walls that load before the content
• A Google Business Profile linked and consistent with the website, so local search results point to a fast destination

Takely sites are built to score well on PageSpeed Insights out of the box. The Starter package (£499 + £49/mo) includes hosting on fast infrastructure and a searchable text menu that is both readable and fast. The Growth package (£999 + £79/mo) adds locally-targeted landing pages and analytics so you can see how that speed translates into orders.

If you want to see how your current site performs before committing to anything, run the PageSpeed Insights test on your homepage and your menu page. Then contact us and we will walk you through the numbers.