Case Study: An Ambulance Booking System That Works on a Weak Network

Surokkha Ambulance runs a 24/7 ambulance service across Dhaka and Bangladesh: ICU, CCU, NICU, PICU, ALS, BLS, AC, freezing and air ambulance. They needed a complete system, not just a brochure site.

The two requirements that shaped everything

An emergency service needs two things from its website. It has to load on a weak mobile network, and the call button has to be reachable in one tap. Every technical choice on this project was measured against those two.

What we built

• The public booking website
• An admin panel for bookings, ambulance and driver records, service areas, pricing and content
• A REST API that feeds the site and the operations team from the same source

Why Qwik for the frontend

The frontend runs on Qwik, so the page is interactive almost instantly, and the layout is served as static HTML from the edge. On a slow connection the visitor sees the page and the call button without waiting for a large script to download.

A page for every search people actually make

Nobody searches for an ambulance company by name at 2 AM. They search for the type they need and the place they are in. So every ambulance type and every service area has its own landing page, with proper structured data: LocalBusiness, Service, FAQ and breadcrumbs.

How it turned out

• 100 on Lighthouse SEO
• Core Web Vitals passing on mobile
• A booking flow that works over 3G

You can check the live site yourself: surokkhaambulance.com

What other businesses can take from this

Decide what the visitor must be able to do in their worst moment, and build for that first. For an ambulance service it is one tap to call. For a clinic it may be booking a serial, and for a shop, finding the price. Speed and clear pages follow from that decision. The same thinking went into XpressAmbu, our ready-made ambulance booking product.