Turbo: faster pages on your cloud hosting plan
Autoscaling decides how much capacity answers your traffic. Turbo decides how quickly each request is answered. It moves your site onto faster processors, pushes it out to every edge before anyone asks for it, and raises the database ceiling. There is nothing to rebuild and nothing to configure.
- Processors
- Standard compute
- Your site at the edge
- Cached when someone first asks
- Database room
- Your plan's quota
- Processors
- Up to 4.20 GHz
- Your site at the edge
- Pre-fetched to every edge
- Database room
- 5 GB across every database
The same site, the same plan. One click on, one click off.
Three upgrades on one switch
Turbo raises three ceilings at once: the speed your code runs at, how early your pages reach the people asking for them, and how much room your databases have. Same site, same plan, nothing to rebuild.
Faster processors
Your requests are routed through high-frequency compute nodes running at up to 4.20 GHz. This is the part that helps with work a cache can never help with: a checkout writing an order, a search running across a catalogue, an admin screen loading a report.
Pre-fetched, not cached on demand
Without Turbo, a page is cached in a region the first time somebody there asks for it, and that first visitor waits. With Turbo your site is pulled into every CDN location worldwide in advance, so the first visitor in a region gets the fast response rather than paying for it.
More room for the database
The storage quota your databases share rises to 5 GB, and it applies to every database on the package rather than to one of them. This is usually the ceiling a growing catalogue or a busy membership site meets first.
Turbo sits on top of the platform you already have. The global CDN, the free SSL and the autoscaling are on every plan without it.
What changes the moment you switch it on
Same site, same plan, same control panel. These are the only things that are different afterwards.
Your code runs on the platform's standard compute nodes.
Your code runs on high-frequency nodes at up to 4.20 GHz.
A page is cached in a region the first time somebody there asks for it, and that visitor waits for it.
Your site is pulled into every CDN location in advance, so nobody has to be the first one waiting.
Your databases share the standard storage quota.
Your databases share 5 GB, across every database on the package.
You find out a page is slow when it is already costing you.
A cache report shows you which pages are served from cache and which still reach your application.
The pages a cache cannot save
The gain lands on the pages that have to be built fresh for the person looking at them, which are usually the pages that earn you money.
Checkout and cart
Every step writes to the database and none of it can be served from a cache. This is where a slow processor costs you orders rather than seconds.
Search and filtering
Faceted search across a large catalogue is real work every time. Faster cores shorten it directly.
Admin and dashboards
The screens you and your staff sit in all day are never cached, so the whole difference lands on the processor.
Large catalogues
Thousands of products, variants and images push the database past what a standard quota comfortably holds.
Logged-in areas
Members, subscribers and customer accounts see personalised pages, which by definition cannot be shared from a cache.
Visitors far from Pakistan
Pre-fetching matters most for the audiences furthest from the origin, because those are the round trips the cache removes entirely.
One click, no downtime, reversible
- 1
Add it to the package
Turbo applies to the whole hosting package, so every site on it gets the faster processors, the pre-fetching and the larger database quota at once. Nothing goes offline while it applies.
- 2
Watch the cache report
The control panel shows which of your pages are being served from cache and which are still reaching your application. It is the honest measure of whether Turbo is earning its place.
- 3
Turn it off if it is not
The same single click removes it. We bill it monthly alongside the plan, so there is no term to serve out and nothing to cancel in writing.
If you would rather see the numbers before you commit, ask us. We will measure a handful of your real pages before and after and send you both.
One price, one package
Billed with your hosting, in rupees or dollars, and it moves with the plan rather than being a separate invoice to track.
- Processors up to 4.20 GHz for uncacheable requests
- Your site pre-fetched by every CDN location worldwide
- 5 GB database quota across every database on the package
- Cache report in the control panel
- One click on, one click off, no downtime either way
Turbo attaches to a cloud hosting plan. If you are not on one yet, the plans page has the sizes and prices, and every plan can take Turbo including the smallest.
Where Turbo is not the answer
- Turbo makes the same work finish sooner. A slow query or a heavy plugin still runs, it just runs faster.
- Capacity is a separate thing, and you already have it. Autoscaling handles traffic volume on every plan at no extra cost.
- A small site that rarely changes is already served from cache most of the time, so there is less left for Turbo to add.
Where Turbo fits
Cloud Hosting
The plans Turbo attaches to: autoscaling, no CPU or memory caps, free global CDN and free migration, from $25 a month.
Read more →Domain Registration
Register the name, point it at the hosting and let us handle the DNS. Free DNS and transfer lock on every domain.
Read more →Domain Pricing
Registration, renewal and transfer prices for every extension, shown in rupees or dollars.
Read more →Turbo, answered plainly
Does Turbo work on every cloud hosting plan?
Yes, including the smallest. It is priced per hosting package rather than per website, so every site on the package is covered by the one charge.
Does Turbo work on every cloud hosting plan?
Yes, including the smallest. It is priced per hosting package rather than per website, so every site on the package is covered by the one charge.
Add Turbo to a cloud hosting plan
Pick the plan that fits the sites you run, then add Turbo to the package when you want it answering faster. Both can change later without a migration.