Performance guide · Leicester
Leicester: trade pricing is the page that cannot cache
Wholesale sites hide their real content behind a login, which is exactly the part a cache cannot help with — and exactly the part your buyers use every day.
The short answer
On a trade site the public catalogue caches cleanly and the account-only pricing never will, because per-customer pricing is per-session by definition. So the page your buyers spend their time on is the one running the full PHP and database path on every request, and it is almost never the page anybody benchmarks.
HostingFast runs NVMe storage behind LiteSpeed caching from London, with per-site PHP versions, stated database allowances and profiling on the top shared tier — because the uncacheable half is fixed with queries and hardware rather than more caching.
By the HostingFast team · Reviewed 12 August 2026
Free
Migration, with a control
24/7
Cover before the vans go
Daily
Backups, restored by you
$0
Setup charge
The buyers here do not browse. They log in, work from a list of part numbers and account-specific prices, and place the order before the van leaves — food manufacturing, textiles and wholesale distribution all working the same way.
Most of those firms sell business to business, which produces a very particular website: a public shell and a logged-in interior. This page is about making the interior quick, since that is where the orders come from.
Account-only pricing is uncacheable by definition
If the price depends on who is logged in, no shared cache can serve that page — and it should not try. Every request runs your code, hits the database for the customer's price band, and renders. That is correct behaviour, and it means the page's speed is entirely a function of query count and execution time.
Which is why a generic caching plugin makes trade sites feel unchanged. It is caching the pages that were already fast, and the interior your buyers actually use never touches it.
The B2B page nobody measures: the login
Time the login POST itself. It writes a session, often looks up account permissions and a price band, and sometimes calls an external system before it returns. A four-second login is a daily tax on every buyer, and it will not appear in any site-wide performance score.
Then time the first page after login, which is usually a dashboard or an order history and is usually the heaviest query on the site. Those two requests, measured properly, describe your buyers' experience better than the home page ever will.
Distance from Leicester, and what it is worth
About 5-15 ms of round trip to our London origin on a well-connected UK line — a range rather than a guarantee, and moved as much by your visitor's carrier as by geography. Against a logged-in page that takes two seconds to build, it is not the variable to chase.
Where it does count is the volume of small requests an interior page makes: an order form fetching stock levels per line pays that round trip repeatedly. Batch those calls and the distance stops mattering at all.
Change one thing, measure, keep the receipt
Baseline the login and the first interior page. Make one change — an index, a batched request, a plugin removed. Re-measure with the same tool from the same connection, three runs, median kept. If it did not move, revert it.
Keep a short log of what you tried and what it bought. On a site that will be maintained by somebody else in two years, that log is worth more than the optimisation itself.
Built for the logged-in half
NVMe storage on every tier, stated CPU, memory and database allowances, per-site PHP version switching and a deliberately low accounts-per-server count. When nothing can be cached, those are the numbers that decide how the page feels.
Migration is free and runs with the old site still serving, there is no setup charge, and daily backups restore from the panel without a ticket.
- .co.uk registered and renewed alongside the plan
- Stated CPU, RAM and database allowances per tier
- Per-site PHP version switching from the control panel
- Free migration with the old site left serving
Why HostingFast
Standard on every plan
Hardware for uncached pages
NVMe storage and a restrained accounts-per-server count keep logged-in pages responsive, which is where a trade site lives.
Stated allowances
CPU, memory and database counts published per tier, so a B2B application can be planned against numbers rather than adjectives.
Profiling on the top shared tier
PHP X-Ray on CloudLinux Pro traces a live request and names the slow call, which is how a two-second login gets diagnosed.
PHP version per site
Switch versions in the control panel and measure the difference, without one legacy integration holding the rest back.
Free migration with a control
Engineers move the site at no cost and keep the old one serving, so you can compare both before delegation changes.
No setup charge
No joining fee at any tier, and the rate you sign up at is the rate you renew at.
Quick Start
From order to online
- 1
Time the login
Submit real credentials with DevTools open and read the waiting phase on the POST. That number is a daily cost to every buyer.
- 2
Time the first interior page
Order history, dashboard, price list — whatever loads next. It is usually the heaviest query on the site.
- 3
Batch the small requests
An order form fetching stock per line pays the round trip repeatedly. One batched call removes the problem entirely.
- 4
Profile before upgrading
Find the expensive query first. A missing index costs nothing to add; a bigger plan costs every month.
Built In
Loaded onto every plan
- Login POST timed and recorded, not assumed
- The first page after login profiled for query count
- Per-line stock and price lookups batched into one request
- Per-site PHP version switching from the control panel
- Stated CPU, RAM and database allowances on the plan
- Your existing site moved over by our engineers, free of charge
- A daily backup restored from the panel before the trade counter opens
- NVMe SSD storage on every tier, not just the expensive ones
- Zero setup charges — there is no joining fee, ever
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
We added a caching plugin and nothing changed. Why?
Because the pages your buyers use are logged in, and logged-in pages cannot be served from a shared cache. The plugin is speeding up the public catalogue, which was probably fine already. Progress on a trade site comes from query work on the interior pages, not from another cache layer in front of them.
How do I make account-only pricing faster?
Reduce what the request does. Cache the price-band lookup per session rather than per line, add indexes on the customer and product keys the query filters on, and batch any per-row stock check into a single call. Profile first — on the top shared tier, PHP X-Ray on CloudLinux Pro will name the call that is costing you.
Is the login worth measuring separately?
It is one of the most valuable measurements on a B2B site and one of the least taken. The login POST writes a session, usually looks up permissions and a price band, and sometimes calls an external system. Every buyer pays that cost every day, and no site-wide score will ever mention it.
Does an ERP integration belong inside the page request?
Not if you can avoid it. An external call inside the request holds resources for its whole duration and puts a third party's availability in front of your page. Give it a deliberate timeout, cache the result for as long as is genuinely acceptable, and move anything that can wait into a background job.
Keep reading
Web Hosting in Prague
Czech connections, and what a cached page costs east of Frankfurt.
Web Hosting in Karachi
Pakistani connections, and what 120-200 ms means for a page that must still feel quick.
Registering a Domain Name
Registering a name, and the DNS records you will need the moment it resolves.
Domain Names
Find, register and transfer domains — first year free with annual hosting.
WordPress Hosting
Managed WordPress on NVMe and LiteSpeed, with staging and backups included.
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.
Make the logged-in half quick.
NVMe storage, stated allocations and live request profiling — plus free migration with the old site left running.
View Domain Names plans