Open your business website right now — on your phone, on a real 4G connection, not WiFi.
How long does it take to load? Can you read the text without zooming? Is there a tap-to-call or WhatsApp button visible without scrolling? Did anything jump around while the page was loading?
If you’ve never done this test, there’s almost certainly a problem you haven’t noticed — while your customers have been noticing it and leaving.
96% of Indonesian internet users access the web via smartphone. That means nearly every prospective customer meets your business on a 6-inch screen, not a 24-inch monitor. A website that isn’t optimised for that experience doesn’t just miss conversions — it actively pushes customers to competitors.
The 7 Mistakes
1. Unoptimised Images — The Most Common Loading Killer
Photos taken on a DSLR or modern smartphone are 2–8MB per image. On an average Indonesian 4G connection, a single 3MB image takes 4–6 seconds to load. Most pages have 5–10 images.
This is the single most common reason local business websites score poorly on PageSpeed Insights Mobile — and it’s entirely fixable without a developer.
The fix:
- Convert images to WebP format (use Squoosh.app — free, no account needed)
- Compress each image to under 200KB before uploading
- Add
widthandheightattributes to every<img>tag to prevent layout shifts
Optimising images alone typically improves LCP from “Poor” to “Good” and cuts loading time by 40–70%.
Don’t just resize images via CSS (
width: 200px). The full file still downloads. The file itself must be compressed before upload.
2. No Click-to-Call or WhatsApp Button
Users searching for local services on mobile are almost always in “ready to act now” mode — they need a doctor, want to order food, need a mechanic. Every extra step between intent and action causes some of them to give up.
Without a click-to-call button: see number → screenshot it → open dialer → type manually → call. Five steps.
With click-to-call: tap → call. One step.
<!-- Phone -->
<a href="tel:+6281234567890">Call Now</a>
<!-- WhatsApp with pre-filled message -->
<a href="https://wa.me/6281234567890?text=Hi%2C%20I'd%20like%20to%20enquire">WhatsApp Us</a>Place these buttons above the fold (visible without scrolling), in the footer, and on the contact page. A sticky button that follows the scroll is even more effective.
3. Missing or Misconfigured Viewport Tag
Without the viewport meta tag, mobile browsers render your website at full desktop width and then shrink it — producing a tiny, unreadable layout that requires pinching and zooming to use.
Check your page source (right-click → View Page Source) and look for this in the <head>:
<meta name="viewport" content="width=device-width, initial-scale=1">If it’s missing — add it. If it exists but contains user-scalable=no or maximum-scale=1 — remove those attributes. Preventing user zoom violates web accessibility standards and is a negative ranking signal under Google’s Mobile-First Indexing.
4. Layout Shift (High CLS): Buttons That Move When Tapped
Cumulative Layout Shift happens when page elements move from their original positions as content loads. The most damaging version for local businesses: a “Contact Us” or WhatsApp button shifts downward after a banner or ad loads — and the user taps where the button was, not where it moved to.
Main causes:
- Images without declared
widthandheightattributes - Web fonts that cause text to reflow when they load (FOUT)
- Dynamically loaded banners, ads, or chat widgets that push content down
Fastest fix: Add width and height to all <img> tags. This tells the browser how much space to reserve before the image loads, eliminating the most common source of CLS.
Check your CLS score at PageSpeed Insights. Target: below 0.1. Above 0.25 is “Poor” and a confirmed negative ranking factor.
5. Text Too Small to Read Without Zooming
A website designed on a 24-inch monitor with 12px body text looks elegant on the designer’s screen. On a 6-inch phone, that text is illegible without pinching to zoom.
Minimum safe sizes:
- Body text: 16px
- Secondary text / captions: 14px
- Nothing functional below 12px
Beyond size, check contrast. Light grey text on white background — common in minimal designs — becomes unreadable in outdoor light or on budget phone screens. Minimum contrast ratio: 4.5:1 (check with WebAIM Contrast Checker).
6. Tap Targets Too Close Together
The average human fingertip is 9–10mm wide. Google and Apple both recommend a minimum tap target size of 48×48px for all interactive elements. Navigation links, buttons, checkboxes, and icons smaller than this produce “fat finger” errors — the user taps the wrong thing.
Most damaging scenarios:
- Navigation menu items too close — user lands on wrong page
- “Cancel” and “Confirm” buttons adjacent on a form — accidental cancellation of a completed form
- Social icons too small in the footer — can’t tap accurately
- CTA button small on mobile but large on desktop
Check via PageSpeed Insights → “Tap targets are not sized appropriately” — it lists specific offending elements.
7. Non-Mobile-Friendly Forms
Contact forms, booking forms, and registration forms that aren’t optimised for mobile are conversion leak points. A user who’s decided to contact you — and then gives up because the form is unusable — is a loss that should never have happened.
Most common form mistakes on mobile:
- No
type="tel"on phone number fields — numeric keyboard doesn’t appear - Fields too small to tap accurately
- Labels only inside the field (placeholder) — they disappear when the user starts typing
- Too many required fields — simplify to name + phone for initial contact
- Submit button not visible without scrolling
The most effective local business contact form has two fields: name and phone number. Everything else can be asked via WhatsApp or phone call.
The 30-Minute Mobile Audit
Via PageSpeed Insights:
- Score LCP — under 2.5 seconds?
- Score CLS — under 0.1?
- Any “Text too small to read” warnings?
- Any “Tap targets not sized appropriately” warnings?
- Any “Properly size images” recommendations?
Visual check on your own phone (4G, not WiFi):
- How many seconds to first content?
- Readable without zooming?
- WhatsApp or call button visible above the fold?
- Press every button — any misfires?
- Scroll top to bottom — anything shift unexpectedly?
Source code check:
-
<meta name="viewport" content="width=device-width, initial-scale=1">present? - No
user-scalable=noin the viewport tag? - All
<img>tags havewidthandheightattributes?
Your mobile audit came back with problems? Our websites are built on Astro.js, which produces 90+ mobile PageSpeed scores by default — before any additional optimisation. Free consultation →
References
- DataReportal. (2025). Digital 2025: Indonesia. datareportal.com/reports/digital-2025-indonesia
- Google. (2025). Core Web Vitals. web.dev/vitals
- Google. (2025). Mobile-First Indexing best practices. developers.google.com/search/mobile-sites
Mobile Website Mistakes — Common Questions
How do I check if my website is mobile-friendly?
Two free tools: PageSpeed Insights at pagespeed.web.dev (enter your URL, select Mobile tab) and Google Search Console under Core Web Vitals. For a real-world check, open your website on your own phone on a 4G connection — not WiFi. If you squint, pinch to zoom, or misfire buttons, your visitors are doing the same.
What is CLS and why does it hurt local businesses specifically?
CLS (Cumulative Layout Shift) measures how much page elements unexpectedly move while loading. The most damaging scenario for local businesses: a WhatsApp or Call button shifts position just as a user taps it — they miss the button and hit an ad or blank space instead. Beyond user frustration, high CLS is a direct negative ranking factor in Google's Core Web Vitals assessment.
Does page speed actually affect Google Maps ranking?
Yes, indirectly. When users click your website from GBP and immediately leave because it loads too slowly, Google records that as a negative behavioural signal for your profile. Core Web Vitals also directly affect organic search ranking, which compounds the traffic loss.