Mobile optimization means the site loads quickly on a phone, does not jump around while loading, and lets a guest read the menu and book without zooming or mis-tapping. We measure against Google's Core Web Vitals and fix the causes, usually images, fonts and third-party scripts.
Why phones get special attention
A guest deciding where to eat may be standing on a sidewalk, sitting in a car or comparing options on the couch. On a phone, a slow page or a tiny button is a reason to try the next result. We treat the phone version as the main version of the site and scale up from there.
What we measure
Google sets three Core Web Vitals targets for a good experience: the main content should render in 2.5 seconds or under (LCP), taps should get a visual response in 200 ms or under (INP), and the layout should hardly move, with a shift score of 0.1 or less (CLS). Google suggests measuring each one at the 75th percentile of page loads, with mobile and desktop segmented separately [1].
| Measure | What it means for a restaurant site | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | When the hero photo or main heading finishes drawing | 2.5 seconds or less |
| Interaction to Next Paint (INP) | The delay between a tap on the menu or booking button and a visible reaction | 200 ms or less |
| Cumulative Layout Shift (CLS) | Whether text and buttons jump while images and widgets load | 0.1 or less |
We record the numbers before we start and after we finish, so you can see what changed.
Common causes we fix
- Oversized photos. Large images scaled down in the browser waste data. We export each image at the size it is shown, in a modern format, with a sharper version only for high-density screens.
- Too many fonts. Each font file is a download. We limit the set and host fonts on your own server.
- Heavy widgets. Reservation, ordering, review and social widgets can add a lot of script. We load them only where needed or replace them with simple links.
- Layout jumps. Images and embeds without set dimensions push text around as they load. We reserve space for each one.
- Menus as images or PDFs. These force pinching and zooming. We turn them into HTML text.
Tap targets and readable text
Buttons and links that are too small or too close together cause mis-taps. WCAG 2.2 added a target size criterion at level AA, and we design tap targets to meet it [2]. We also keep body text at a comfortable size, set enough contrast for reading outdoors, and make sure the booking button stays reachable with one thumb.
Mobile navigation
We keep the mobile menu short: menu, book or order, visit, and contact, with the rest one tap away. The header shows your name and the main action, and the navigation can be opened and closed with a keyboard as well as by touch.
How we test on phones
Our phone testing follows the same steps on every page:
- Load the page on a slower mobile connection and note when the main photo and headline appear.
- Tap the menu, booking and ordering buttons and check how quickly the page responds.
- Scroll while images and widgets load and watch for text or buttons that jump.
- Read the menu without zooming, outdoors if possible, to check text size and contrast.
- Open and close the navigation with touch and with a keyboard.
- Try the booking or ordering flow from start to confirmation.
What you get
- A short report with the measurements before and after the work.
- The fixes themselves, made on your site or in a new build.
- A list of any third-party tools that still slow pages down, with options for each.
If your site needs more than speed work, our redesign service covers a full rebuild.
Accessibility and speed together
Speed and accessibility support each other. Real text instead of images, clear headings and fewer scripts make pages lighter and easier to use with assistive technology. We test both together against WCAG 2.2 level AA [2].
Frequently asked questions
Can you speed up a site on a builder platform?
Partly. We can optimize images, fonts and embeds, but some builder platforms limit what can change. We will tell you what is possible before we start.
Will the site look different afterward?
Mobile optimization keeps your design. Some images may be cropped or resized for small screens, and we agree those changes with you.
Do you test on real phones?
Yes. We test on recent iPhone and Android browsers as well as in browser tools that simulate slower networks.
Will this improve our rankings?
We cannot promise ranking changes. Faster, more usable pages are better for guests, and Google publishes Core Web Vitals so site owners can measure how pages feel to use.
Sources
Checked on October 29, 2026.
- web.dev, Web Vitals. Primary source
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2. Primary source
