How Fast Should a Café Website Be?

"Fast" is not a feeling, it is a measurement, and Google publishes the thresholds. There are three, and you do not need to be technical to understand what they mean.

The three numbers

Largest Contentful Paint — under 2.5 seconds. How long until the biggest thing on screen appears. In practice this is usually your hero image. If it takes four seconds, the visitor spends four seconds looking at an empty page.

Interaction to Next Paint — under 200 milliseconds. How long the page takes to respond when someone taps. Above about a fifth of a second, a tap feels broken and people tap again, which often makes it worse.

Cumulative Layout Shift — under 0.1. How much the page jumps around while loading. Everyone has tried to tap a link and hit something that loaded underneath their thumb. That is layout shift, and on a menu page it means tapping the wrong section.

Where the time actually goes on small sites

In our experience three things account for most of it.

Images that were never resized. A photograph straight from a phone is often four thousand pixels wide and several megabytes. Displayed in a card three hundred pixels across, that is a hundred times more data than needed. Resizing and converting to a modern format routinely cuts page weight by eighty percent, and it changes nothing visually.

Fonts that block the first paint. A custom font loaded badly means the browser waits before drawing any text at all. Setting the font to swap in — showing a system font first, then switching — costs you a flash and buys you seconds.

Scripts nobody uses. Analytics, a chat widget, a social feed, a cookie tool, a booking script. Each was added for a reason and each costs load time. The chat widget nobody answers and the social feed with four likes are pure tax. Audit them once a year and delete what you do not use.

What does not cause slowness

Having a blog. Having several pages. Using a content management system. Video, if it is not set to autoplay at full resolution on mobile.

Slowness is almost never architectural on a site this size. It is almost always weight.

Measuring it honestly

Run PageSpeed Insights on your phone, on mobile data, away from the café wifi. The lab score is a useful hint; the field data at the top of the report is what real visitors experienced.

Test the menu page, not the homepage. The homepage is what you look at. The menu is what they look at.

The realistic target

For a café or restaurant site, a hero visible in under two seconds on a mid-range phone on a normal mobile connection is achievable without unusual engineering. It mostly requires someone to compress the images and remove the scripts.

That is the unglamorous truth about web performance at this scale. It is rarely clever. It is mostly housekeeping that nobody has done yet.