Skip to content
Get Ranked On TopIllustrative case studySignal plan

A fictional business. The figures are a modelled scenario, not a client result.

Sarang KopitiamKopi · kaya toast · nasi lemak

Heritage kopitiam chain, 14 outlets · Penang

How a Penang kopitiam chain poured its menus out of an empty JavaScript shell and into Google

From 10 to 98 indexed pages, then +71% organic orders

9 months · Asia-Pacific · Signal plan

  • Server-side rendering
  • Outlet URL architecture
  • Core Web Vitals
  • Structured data

Kopi tarik: pulled from mug to mug until it runs smooth.

10 → 98Pages indexed (of 100) · month 9

01The challenge

A full kopitiam, an empty glass.

A JavaScript ordering site showed Google an empty shell, 14 outlets shared one URL and mobile LCP topped 6 seconds, so outlet and menu pages barely indexed.

Every morning Sarang's fourteen outlets sell out of kaya toast by ten, yet on Google the chain barely existed. Its ordering site was a single-page app: the server sent an empty shell and a 1.4 MB script, and menus, prices and opening hours only appeared once that script had run on the customer's phone. Every outlet lived at the same address behind a query parameter, so Google folded fourteen locations into one page.

What Googlebot fetched first
<head><title>Sarang Kopitiam</title></head>
<body>
  <div id="root"></div>
  <script src="/static/app.3f9c1e.js"></script>
</body>

12 words of readable text

What a customer saw, 6.4 s later
  • Kaya toastRM 3.20
  • Nasi lemakRM 8.50
  • Char koay teowRM 9.90
  • Kopi pengRM 3.40

1,900 words once the script had run

Fourteen outlets, one address

Before: every outlet behind /outlets?id=

Google treated the parameter as noise, followed the canonical to the list page and indexed only that.

After: one page per outlet, such as sarangkopitiam.example/outlets/gurney

  • /gurney
  • /lebuh-chulia
  • /tanjung-bungah
  • /air-itam
  • /balik-pulau
  • /pulau-tikus
  • /jelutong
  • /bayan-lepas
  • /batu-ferringhi
  • /gelugor
  • /tanjung-tokong
  • /butterworth
  • /seberang-jaya
  • /bukit-mertajam

02Diagnosis

The audit, called out like an order.

Regulars order in code: kopi-o, kopi-c, kosong, peng. We wrote the site's four problems up the same way.

KOSONG

kosong: nothing in it

Rendering

12 words

The server's HTML held twelve words: the site name, a cookie line and an empty root div. Menus, prices and hours existed only after 1.4 MB of JavaScript ran. Google's renderer got there on a few pages, days later, and gave up on most.

Finding 1 of 4

KOPI-O

kopi-o: one plain cup

URLs

1 URL

All fourteen outlets loaded at /outlets?id=1 to ?id=14, each canonicalised to /outlets. Sort, language and table-booking parameters multiplied that into 8,600 crawlable variants, which took 63% of Googlebot's visits.

Finding 2 of 4

KAW

kaw: far too strong

Speed

6.4 s

Mobile LCP at p75 was 6.4 s: a 900 KB photo carousel waited behind the whole bundle. INP was 420 ms because the cart hydrated on load, and late web fonts shifted the menu (CLS 0.27).

Finding 3 of 4

SIEW DAI

siew dai: much less

Index coverage

10 / 100

Of 100 outlet and menu pages a customer could reach, 10 were indexed: the outlet list and nine dishes. A search for “nasi lemak balik pulau” found delivery apps and food blogs instead.

Finding 4 of 4

03The strategy

Four changes to the recipe.

Built on our Signal plan: technical SEO for sites where rendering, crawl paths and speed decide what Google can see.

  1. Chit 101

    Server-side rendering

    Menus, prices, opening hours and outlet details rendered on the server and sent as HTML; the ordering cart hydrates only when a customer taps Order. The raw HTML of a menu page went from twelve words to about 1,900.

  2. Chit 202

    Outlet URL architecture

    One clean URL per outlet (/outlets/gurney, /outlets/balik-pulau) and per dish, self-referencing canonicals, a 301 from every ?id= variant, sort and language parameters kept out of the crawl, and sitemaps split into outlets and menu.

  3. Chit 303

    Core Web Vitals

    The hero photo served as a sized, preloaded AVIF instead of a carousel, the 1.4 MB bundle split so a menu page ships 200 KB, and font fallbacks matched so the menu no longer jumps. Field data watched per template.

  4. Chit 404

    Structured data

    Restaurant markup on each outlet page with address, geo, opening hours and a menu link; Menu and MenuItem markup with prices in ringgit; breadcrumbs that mirror the new URLs. Each Google Business Profile now links to its own outlet page.

04Pull the perfect kopi

Pour from client-side to server-side rendering until every layer settles under the line.

Each layer in the glass is one measurement on a mid-range phone over 4G: the thicker it is, the further it sits over Google's “good” threshold. Drag the pour, or use the arrow keys, to add the fixes in the order we shipped them.

Order: KOPI KAW KAW

Client-side rendering

As found: an empty shell and 1.4 MB of JavaScript. Nothing useful paints until the whole bundle has downloaded and run.

CLS · layout shift
0.27Over
good ≤ 0.1
INP · response to a tap
420 msOver
good ≤ 200 ms
LCP · largest paint
6.4 sOver
good ≤ 2.5 s
JavaScript before content
1,480 KBOver
budget ≤ 300 KB

4 layers still over the line

Order codes as called across a Penang kopitiam: kaw is strong, siew dai is less sweet, C is with evaporated milk, peng is iced.

05Month by month

9 months, cup by cup.

Pages indexed, out of 100
  1. Month 1

    Audit

    Raw and rendered crawls of all 100 pages, twelve weeks of server logs, field Core Web Vitals per template and online orders by landing page.

  2. Months 2–3

    Render

    Server rendering for the outlet and menu templates, built behind a flag and compared page by page against the old app.

  3. Month 4

    Re-address

    Fourteen outlet URLs and 86 dish URLs go live; 8,600 parameter variants are redirected or kept out of the crawl.

  4. Months 5–6

    Speed

    Image pipeline, bundle split, cart on tap and font fallbacks. Field LCP passes from month 6.

  5. Months 7–9

    Mark up and measure

    Restaurant and Menu markup, Business Profile links to each outlet page, monthly index and ranking checks from Penang.

06Results

Under the line, and on the map.

Pages indexed (of 100)

10 → 98

Outlet pages 1 → 14, dish pages 9 → 84

Mobile LCP (p75)

6.4 s → 2.1 s

INP 420 ms → 160 ms, CLS 0.27 → 0.05

Organic sessions / month

+142%

9,800 → 23,700 sessions a month

Orders from organic search

+71%

1,240 → 2,120 orders a month from organic visits

Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.

Organic sessions per month
010,00020,000Outlet URLs liveM1M2M3M4M5M6M7M8M923,700

Core Web Vitals, field data

  • Before
  • After
LCP (p75, mobile)6.4 s → 2.1 s
INP (p75)420 ms → 160 ms
CLS (p75)0.27 → 0.05

The dark tick marks Google's “good” threshold.

Outlet searches, before and after

OutletQueryBeforeMonth 9
Gurneykopitiam gurney drive–#2
Lebuh Chuliakopi tarik george town#31#3
Tanjung Bungahbreakfast tanjung bungah–#1
Air Itamroti bakar air itam–#2
Balik Pulaunasi lemak balik pulau#44#4
Bukit Mertajamkopitiam bukit mertajam–#3

– means not in the top 50. Positions checked on mobile from Penang; all fourteen outlets now rank in the top five for their own “kopitiam + neighbourhood” search.

Is Google getting an empty glass?

If your menus, listings or locations only appear after JavaScript runs, start with the Signal plan, or tell us what you are serving.

← All case studies