Third-party profile · Taxi Firms
Taxi firms: the map embed is the heaviest thing you own
One interactive map above the fold can cost more than every other asset on the page put together, and it is usually decoration.
The short answer
An interactive map embed is typically the single heaviest component on a taxi firm's site: several hundred kilobytes of JavaScript plus tile requests, loaded before a passenger has asked for a map. Measure it, then decide whether it earns that, because on most pages a static image and an address does the same job for a fraction of the weight.
The test takes two minutes. Load the page with the DevTools Network panel open and note total requests and transfer, then block the map's domain in the request blocking panel and reload. The difference is what the map costs, stated in bytes rather than opinion.
Your own pages stay quick on NVMe behind a LiteSpeed cache, with free SSL, engineer-run migration, domain mailboxes and 24/7 support included, from $2.42/mo with flat renewals.
By the HostingFast team · Reviewed 15 August 2026
Free
Migration, no charge
24/7
Cover, round the clock
Daily
Backups daily
$0
To go live
Taxi booking is a mobile-first business with a slim margin for delay. Somebody standing outside a station at eleven at night either gets a number or a booking form quickly, or they open a different app.
The sites that lose that moment usually lose it to third-party components rather than to their own code: an interactive map, a fare calculator widget, a review badge, a chat bubble. Each was added for a reason and none of them were measured afterwards.
This page is about measuring them. What each third party costs, which ones to defer, when geolocation is worth a permission prompt, and why your best pages should be the plainest ones.
Price the third parties in bytes
Open DevTools, load your booking page, and read the request count and total transfer at the foot of the Network panel. Then open the request blocking panel, block the map provider's domain, and reload. Repeat for the chat widget and any review badge. Each reload gives you a cost.
Write those costs in a list next to what each component does for you. A map that shows your office location on a page nobody books from is a poor trade. A fare calculator that produces bookings might well be worth its weight, and now you know what that weight is instead of guessing.
Fixed-fare pages should be the fastest thing you have
Airport runs, station transfers, hospital journeys: these pages carry your highest-value searches, and they need almost nothing to work. A price, a journey time, a coverage note and a tappable phone number. Static content, fully cacheable, served by LiteSpeed without starting PHP.
Keep them that way. The temptation is to bolt the booking widget and the map onto every page for consistency, which converts your fastest pages into your slowest for no gain. Link to the booking page instead, and let the fare page do the one job it is very good at.
Geolocation costs a prompt, so make it earn one
Asking the browser for a location triggers a permission dialogue, and a dialogue on arrival is an interruption most passengers decline. Once declined, the answer is remembered, and your pickup field is worse off than if you had never asked.
Ask only after an intent signal: the passenger has tapped into the pickup field, or pressed a Use my location button. Then time what happens next in the Network panel, because a location lookup followed by a reverse-geocode round trip is two waits, and a passenger with a keyboard already open will usually beat both.
Measure on the network passengers use
Office wireless flatters everything. Set DevTools throttling to Slow 4G, disable cache and reload the booking page, then check where Largest Contentful Paint lands and how the call button responds. Under 2.5 seconds for the paint and under 200 milliseconds for the tap is the standard worth holding.
Field data closes the loop. PageSpeed Insights reports real Chrome visits over a rolling 28 days at the 75th percentile, which is the figure that reflects a passenger on a busy cell at closing time. Check it again a month after each change rather than judging by how the page feels on a laptop.
Your pages, and everybody else's scripts
The pages you own are served from a LiteSpeed cache on NVMe storage, so the only slow requests left on a taxi site are the ones you invited in from elsewhere.
Free SSL, engineer-run migration, daily backups and domain mailboxes come on every plan, and support is staffed at every hour rather than office hours.
- Fare pages served from cache, PHP untouched
- NVMe under the booking POST
- WebP conversion for fleet photography
- 24/7 support at closing time
Why HostingFast
Standard on every plan
Fare pages served as files
Static fixed-fare pages are fully cacheable, so LiteSpeed returns them without starting PHP at all.
NVMe under the booking path
A booking submission cannot be cached, so fast storage under the database is what keeps it responsive.
Images handled
Built-in WebP conversion keeps fleet photography light without adding another plugin to the stack.
Mail that gets through
MailChannels handles outbound delivery, so a booking confirmation reaches the passenger rather than their junk folder.
Late-night support
Humans on the desk at any hour, with first replies targeted at two hours and one hour when a site is down.
Flat pricing
No setup fee, and the rate you sign up on is the rate the account renews at.
Quick Start
From order to online
- 1
Cost each third party
Note total requests and transfer, then block the map, chat and badge domains one at a time and reload. Each difference is that component's price in bytes.
- 2
Strip the fare pages back
Remove widgets and maps from fixed-fare pages so they stay fully cacheable, and link through to the booking page instead.
- 3
Gate the location prompt
Ask for geolocation only after the passenger taps the pickup field or a Use my location button, then time the lookup and the reverse-geocode separately.
Built In
Loaded onto every plan
- LiteSpeed hands over a static fare page as a file
- NVMe SSD under the uncacheable booking request
- Built-in WebP conversion for fleet and vehicle photography
- MailChannels delivering the booking confirmation
- PHP version switchable per domain in cPanel
- Staging clones for trialling the removal of a widget
- Free SSL, issued once and reissued from then on
- One backup every day, restored in a single click
- No setup fee, and renewals at the sign-up rate
- 24/7 human support through nights and weekends
Frequently Asked
What people ask us most often
How much does an interactive map actually cost my page?
Usually several hundred kilobytes of JavaScript plus tile requests, and often more than everything else on the page combined. Measure it rather than accepting the estimate: block the provider's domain in the DevTools request blocking panel, reload, and compare the transfer totals.
Should the booking widget go on every page?
No. Fixed-fare and airport pages work best as plain, fully cacheable content with a tappable number and a link to the booking page. Adding the widget everywhere turns your fastest pages into your slowest without producing extra bookings.
When should the site ask for a passenger's location?
Only after they have shown intent, by tapping the pickup field or pressing a Use my location button. A permission prompt on arrival is usually declined, and a declined prompt is remembered, so you have made the pickup field worse permanently in exchange for nothing.
Which page should I test to judge a taxi site?
The booking page, on Slow 4G with cache disabled, and the call button on it. Those are the two things a passenger interacts with under time pressure. Aim for under 2.5 seconds to largest paint and under 200 milliseconds from tapping the button to the next paint.
Keep reading
Dance Studios — Hosting Guide
Class timetables, term signups and a site that stays quick when a course fills.
Furniture Stores — Hosting Guide
Large product photography, delivery options and a catalogue that loads well.
Best Hosting With Free SSL Included
Which hosts include the certificate as standard, and which add it at renewal.
Magento Hosting — Built for Taxi Firms
A heavier catalogue platform, and the resources it genuinely needs underneath.
VPS Hosting Plans
Isolated resources and root access, for when shared hosting stops fitting.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Price the scripts, then cut them.
Cached fare pages, NVMe under the bookings, and support awake at closing time.
View Magento Hosting — Built for Taxi Firms plans