I've audited a lot of local business websites in Northern Greece. The pattern is consistent: the site looks fine on desktop, was probably built five years ago on WordPress, and loads in eight seconds on a 4G connection. The business owner knows it's slow but doesn't know what that's actually costing them.
Here's what a slow site costs in concrete terms, and what a rebuild actually fixes.
Google's ranking signal you can't ignore
Core Web Vitals became a confirmed Google ranking factor in 2021. The three metrics that matter most are:
- LCP (Largest Contentful Paint) — how long until the main content is visible. Target: under 2.5 seconds.
- CLS (Cumulative Layout Shift) — how much the page jumps around while loading. Target: under 0.1.
- INP (Interaction to Next Paint) — how responsive the page feels to clicks. Target: under 200ms.
For a search query like κατασκευή ιστοσελίδων Ξάνθη or εστιατόριο Ξάνθη, Google uses these scores as a tiebreaker between pages with similar content relevance. Two businesses with comparable content and backlinks — the faster one ranks higher.
Most local business sites I've looked at in the region score below 40 out of 100 on mobile. A rebuilt site on a modern stack (Next.js, Vercel) typically scores 85–95. That difference is visible in rankings within three to four months.
The bounce rate you're not measuring
Most business owners check page views but not session quality. A site that takes six seconds to load on mobile has a 60–70% bounce rate — meaning the majority of visitors who click your link leave before they see any content. Those visitors never convert to enquiries, phone calls, or walk-ins.
Google Analytics shows you how many sessions occurred. It doesn't automatically surface how many people bounced before GA's tracking code even finished loading — which happens on sites that load analytics scripts synchronously in the head.
A faster site doesn't just rank better. It retains the visitors who do find it.
What "mobile-first" actually means for a Greek local business
About 70% of local search traffic in Greece comes from mobile devices. The user is on the street, they searched for your business category, and they have maybe four seconds of patience before they go back to the results and click a competitor.
"Mobile-first" doesn't mean your desktop site is also readable on a phone. It means the site was designed for a phone and works well on desktop as a secondary concern. That's a layout decision, a font size decision, a tap target decision, and a performance decision — all made at the design stage, not added afterwards.
WordPress themes with large sliders, parallax effects, and multiple embedded fonts are designed for desktop. They're bolted onto mobile. You can see the difference.
The enquiry form problem
I've seen local business sites where the contact form doesn't work on iOS Safari. The user fills in their name, phone number, and message, taps Submit, and nothing happens. No confirmation, no error — the form just resets.
This is almost always a JavaScript error caused by a form plugin that hasn't been maintained and isn't compatible with current browser versions. The business owner has no idea because they don't test the form themselves, and the customers who hit the bug just close the tab.
Enquiry forms should be tested on iOS Safari and Chrome for Android before a site launches and after every plugin update.
What a rebuilt site actually delivers
When I rebuild a local business site from scratch on Next.js with Tailwind and Vercel hosting, the deliverables are:
- Sub-2-second LCP on mobile — measurable before launch using Lighthouse in the build pipeline
- Bilingual support (Greek/English) — Xanthi is a tourist and trade hub; English-language visitors are not negligible
- Google Search Console wired up — so the owner can see what queries are bringing people in
- A contact form that sends email — tested on all major mobile browsers, with a real confirmation screen
- A sitemap and robots.txt — the basics that a lot of DIY or cheap-agency sites miss
None of this is magic. It's the result of using a current stack correctly rather than piling functionality onto a platform that wasn't designed for it.
A note on cost
A proper rebuild is more expensive upfront than maintaining an existing slow site. The return shows up in enquiry volume, not in a line item you can point to. It's easier to justify if you're running any advertising — putting Google Ads spend behind a slow site is paying to deliver visitors to a page that loses them.
If you're running a local business in Xanthi, Kavala, Komotini, or anywhere in the region and your site hasn't been rebuilt in the last three years, it's worth getting a performance audit. I do these for free for businesses I'm considering working with — it gives both sides a concrete starting point.