A restaurant website that loads in under 2 seconds can increase bookings by 40% or more by reducing bounce rates, improving user experience, and boosting search rankings. This case study shows how a Success restaurant transformed their slow, bloated website into a high‑performance digital asset, resulting in a 42% increase in online bookings within four months. The optimization focused on Core Web Vitals, image compression, and modern hosting—key factors that directly influence customer decisions in Perth’s competitive southern suburbs.
Case Study Overview
| Aspect | Details |
|---|---|
| Client | Family-focused restaurant in Success, WA (name withheld) |
| Location | Success, Perth’s southern suburbs (Cockburn area) |
| Problem | 8–12 second load times, 68% bounce rate, poor Core Web Vitals |
| Solution | Full rebuild with Astro, image optimization, edge hosting |
| Project Duration | 6 weeks (audit to launch) |
| Primary Result | 42% increase in online bookings within 4 months |
The Problem: A Slow Website Was Driving Hungry Customers Away
The venue, a popular family‑focused restaurant in Success, was struggling with a website that took 8–12 seconds to load on mobile. Despite having a great menu and positive reviews, the digital experience was frustrating potential diners:
Performance Issues Identified
| Issue | Measurement | Impact |
|---|---|---|
| Extreme bounce rates | 68% of mobile visitors leaving | ~30 lost bookings per week |
| Slow LCP | 9.2 seconds | Google “Poor” rating, ranking penalty |
| High CLS | 0.45 | Frustrating layout shifts, poor UX |
| Oversized images | 2MB+ per hero image | 73% of total page weight |
| Plugin bloat | 40+ WordPress plugins | Excessive HTTP requests, JS bloat |
| Slow TTFB | 1.8 seconds | Server response delay |
- Extreme bounce rates: 68% of mobile visitors left before the page finished loading, costing the restaurant an estimated 30 lost bookings per week.
- Poor Core Web Vitals: Google Lighthouse scored the site 32/100 for performance, with a Largest Contentful Paint (LCP) of 9.2 seconds and a Cumulative Layout Shift (CLS) of 0.45.
- Inefficient images: Unoptimized hero images (each over 2 MB) were the primary cause of slow loading, especially on mobile data.
- Outdated technology stack: The site was built on a generic WordPress theme with 40+ plugins, many of which were unused but still adding HTTP requests and JavaScript bloat.
The restaurant’s analytics revealed that mobile traffic accounted for 82% of all website visits, yet the average load time on 4G was 9.1 seconds—well above the 3‑second threshold where 40% of users abandon a site.
The Solution: A Performance‑First Overhaul
We partnered with the restaurant to rebuild their website with speed as the primary design constraint. The goal was to achieve sub‑2‑second loads on mobile while preserving the visual appeal and functionality they needed.
The 4-Pillar Optimization Strategy
| Pillar | Action | Expected Impact |
|---|---|---|
| 1. Platform Migration | WordPress → Astro static site | 90% JavaScript reduction |
| 2. Image Pipeline | WebP, responsive srcsets, CDN delivery | 84% image weight reduction |
| 3. CSS/JS Optimization | Critical CSS inline, deferred non-essential JS, lazy loading | Near-instant interactivity |
| 4. Hosting Upgrade | Edge hosting with built-in caching | TTFB from 1.8s to 180ms |
- Migration to Astro: We replaced the bloated WordPress theme with a lightweight static site built using Astro, eliminating unnecessary database queries and reducing JavaScript by 90%.
- Advanced image pipeline: Every image was resized, converted to WebP, and served via a global CDN with responsive srcsets, cutting total image weight by 84%.
- Critical CSS & lazy loading: We inlined critical CSS, deferred non‑essential JavaScript, and lazy‑loaded below‑the‑fold content to ensure the page became interactive almost instantly.
- Hosting & CDN upgrade: The site was moved to a high‑performance edge‑hosting platform with built‑in caching, reducing Time‑to‑First‑Byte (TTFB) from 1.8 s to 180 ms.
The new site retained all the essential features—online bookings, menu display, location map, and photo gallery—but delivered them in a fraction of the time.
The Optimization Process: Step by Step
Project Timeline
| Week | Phase | Activities |
|---|---|---|
| 1 | Audit & Benchmarking | Lighthouse, WebPageTest, RUM data analysis, bottleneck identification |
| 2 | Technology Evaluation | Platform comparison, Astro selection, architecture planning |
| 3–4 | Development | Astro build, image pipeline setup, component development |
| 5 | Image Optimization | Reprocessing all images, WebP conversion, responsive sizing |
| 6 | Testing & Launch | 30+ device testing, continuous Lighthouse checks, go-live |
1. Performance Audit & Benchmarking
We used Google Lighthouse, WebPageTest, and real‑user monitoring (RUM) data to identify the biggest bottlenecks. The audit showed that images accounted for 73% of the page weight, and render‑blocking JavaScript delayed the First Contentful Paint by 4.5 seconds.
2. Technology Stack Evaluation
After comparing WordPress, Astro, and other static‑site generators, we chose Astro for its near‑zero JavaScript overhead and excellent built‑in image optimization. The decision was also influenced by the restaurant’s simple content needs—no dynamic user interactions beyond a booking form. (See our comparison in Astro vs WordPress for Hospitality Websites.)
3. Image Optimization & Delivery
Our photography team reprocessed all existing menu and gallery images, exporting them at multiple breakpoints (400px, 800px, 1200px) in WebP format. We implemented Astro’s <Image /> component to automatically serve the correct size and format, and set up a CDN to cache images globally.
Image Optimization Results
| Image Type | Original Size (avg) | Optimized Size (avg) | Reduction |
|---|---|---|---|
| Hero banner | 2.4 MB | 145 KB | -94% |
| Menu dishes | 1.8 MB | 85 KB | -95% |
| Gallery images | 1.2 MB | 95 KB | -92% |
| Total page weight | 8.7 MB | 1.2 MB | -86% |
4. Code Splitting & Asset Minimization
We removed unused CSS, split JavaScript into critical and deferred bundles, and adopted modern ES modules. Third‑party scripts (like Google Maps and booking widgets) were loaded only after the main content had painted.
5. Testing & Validation
Before launch, we tested the site across 30+ real devices and network profiles (from 3G to fibre). We also ran continuous Lighthouse checks to ensure Core Web Vitals stayed in the “green” zone. After launch, we monitored performance with SpeedCurve and observed real‑user metrics via CrUX data.
Measurable Results: The Numbers Speak
Within four months of launching the optimized site, the restaurant saw dramatic improvements across every performance and business metric:
| Metric | Before Optimization | After Optimization | Change |
|---|---|---|---|
| Mobile bounce rate | 68% | 22% | ‑68% |
| Average load time (mobile 4G) | 9.1 s | 1.2 s | ‑87% |
| Largest Contentful Paint (LCP) | 9.2 s | 1.4 s | ‑85% |
| Cumulative Layout Shift (CLS) | 0.45 | 0.02 | ‑96% |
| Online bookings (monthly) | 118 | 168 | +42% |
| Organic search traffic | 340 visits/month | 810 visits/month | +138% |
| Google Lighthouse Performance Score | 32 | 98 | +206% |
| Time to First Byte (TTFB) | 1.8 s | 180 ms | -90% |
| Average session duration | 48 s | 2 min 15 s | +181% |
The improved performance also translated into higher customer satisfaction. Post‑launch surveys showed that 94% of diners found the new website “much faster and easier to use” on their phones, and 81% said the speed made them more likely to book a table directly instead of calling.
ROI Analysis
| Investment | Cost | Return (4 months) |
|---|---|---|
| Website rebuild (Astro) | $4,500 | 50 additional bookings/month × $45 avg. spend = $2,250/month |
| Image reprocessing | $400 | Included in conversion improvement |
| Edge hosting (annual) | $350 | Ongoing performance + SEO benefit |
| Total Investment | $5,250 | $9,000+ additional revenue in 4 months |
Payback period: Under 3 months. The ongoing benefits (improved SEO, reduced bounce rate, higher conversion) continue to compound.
Why Speed Matters for Success Restaurants
Success is a family‑oriented suburb in Perth’s southern corridor where many diners use their phones to find and book restaurants while on the go—often from Cockburn Gateway, the local shopping centre, or after visiting nearby attractions. Patchy mobile coverage in some areas makes fast‑loading websites even more critical. A site that loads instantly, displays menus clearly, and allows quick booking isn’t just a convenience—it’s a competitive edge.
The optimization succeeded because it addressed three specific needs of the Success market:
- Mobile‑first performance: With many locals using smartphones on 4G/5G networks, a fast‑loading site reduces frustration and keeps potential customers engaged.
- Local SEO advantage: Google’s page‑experience update prioritizes fast sites in local search results, helping the restaurant appear higher for queries like “family restaurant Success” or “best pizza near me.”
- Visual appeal without the weight: High‑quality food photography is essential, but it must be delivered efficiently. Our image pipeline ensured stunning visuals without slowing down the page.
Frequently Asked Questions: Website Speed Optimization
Key Takeaways for Other Hospitality Businesses
This case study demonstrates that a performance‑focused website overhaul can deliver substantial returns. The core lessons for other Perth hospitality businesses are:
- Measure Core Web Vitals regularly: Use Google Search Console and Lighthouse to track LCP, CLS, and INP. If any are in the “red,” you’re losing bookings. (Learn more in our pillar article Speed Kills (Competition): Why Fast Websites Get More Bookings.)
- Optimize images aggressively: Images are the largest performance bottleneck for most restaurant sites. Convert to WebP, serve responsive sizes, and use a CDN. (See how image optimization impacts SEO in How Image Compression Impacts SEO & Why Photographers Get It Wrong.)
- Consider a static‑site generator: For simple brochure‑style sites, static HTML (like Astro) is faster, more secure, and cheaper to host than a dynamic CMS. (Compare options in Astro vs WordPress for Hospitality Websites: A Perth‑Focused Comparison.)
- Test on real networks and devices: Lab tools like Lighthouse are helpful, but real‑user monitoring reveals the true experience of your customers.
Ready to Speed Up Your Restaurant Website?
If your restaurant’s website takes more than 3 seconds to load on mobile, you’re missing out on bookings, higher search visibility, and better customer satisfaction. The good news is that many performance issues can be fixed without a full rebuild—we can often optimize your existing site in a matter of days.
Want to see how fast your site could be? Explore our Perth restaurant website performance services or request a free speed audit. We’ll analyze your current site, identify the biggest bottlenecks, and provide a clear roadmap to increase your bookings through speed.
Related reading: Learn about Core Web Vitals explained simply, discover the annual digital checklist, and see what a Perth restaurant website should cost.