Performance guide · Newcastle
Newcastle: the visitor's clock and the admin's clock
Your public pages are cached and quick. The team spends its day in the parts that are not, and nobody ever benchmarks those.
The short answer
Measure both sides: the visitor's experience, which caching largely solves, and the administrative side, which caching cannot touch at all. On a back-office-heavy operation the second one is where the working day actually goes, and it is invisible to every public speed test.
HostingFast runs NVMe storage behind LiteSpeed from a London origin, with SSH, WP-CLI and per-site PHP versions on the account — because the uncached half is fixed with tooling and profiling rather than with another cache.
By the HostingFast team · Reviewed 12 August 2026
99.9%
Uptime target, credited
24/7
Engineers at 04:00 too
Free
SSL, renewed for you
NVMe
Storage on every tier
A great deal of what gets built here is used by staff rather than customers — rota tools, claims screens, back-office dashboards on the quayside — alongside the public sites of a visitor economy that trades hardest at the weekend.
That mix produces a lot of internal tooling and a lot of logged-in traffic. This page deals with the visitor's clock first, then the admin's, then how to read a waterfall without deceiving yourself, then how to hold any host to its reliability claim.
Two clocks, and only one of them gets tested
The visitor's clock runs from a cold request to a readable page, and caching does most of the work: a LiteSpeed hit is answered before WordPress loads, so the public site is quick almost by default once coverage is wide.
The admin's clock runs all day, on pages that are logged in and therefore never cached. Every screen load runs the full PHP and database path. If saving a post takes four seconds, that is forty minutes a week per editor, and no public speed test will ever mention it.
Where the uncached time actually goes
Usually queries. A plugin adding a dozen lookups to every admin screen, a wp_options table with a bloated autoloaded row, an inefficient meta query behind a filtered list. Count them before you assume the server. On the top shared tier, PHP X-Ray on CloudLinux Pro will trace a live request and name the call.
The other half is anything that speaks straight to the origin regardless of caching: file manager sessions, SSH, FTP and any long stretch of control-panel work. Those feel the round trip directly, which for a UK team on a London origin is 5-15 ms and comfortably ignorable.
How to read a waterfall without fooling yourself
Open the Network panel, disable cache, reload, and look at the document request first — its waiting phase is time to first byte and nothing else. Then find the largest contentful element and trace backwards: what had to arrive before it could paint, and what blocked that.
Ignore the total. A page can post a respectable total while the one request that matters arrives late, and a page can look busy while every request is small and parallel. The shape tells the story; the sum rarely does.
Holding a host to its number
We hold a 99.9% uptime target under constant monitoring and pro-rate a credit back to your account when a month falls short. That is a commitment with arithmetic behind it rather than a slogan, and you should verify it independently.
Point your monitor at a URL that cannot be cached, so the check exercises PHP and the database. A green light on a cached home page proves the cache is warm and tells you nothing about whether the application is answering.
Built for the uncached half as well
Server-level caching handles the public side, and the account gives you what the private side needs: SSH with Git and Composer, WP-CLI, per-site PHP versions, staging copies and daily backups that restore from the panel without a ticket.
Support is on shift at every hour, with a first reply inside two hours and inside one when a site is down — which matters when the people affected are your own team at eight in the morning.
- .co.uk registered and renewed alongside the plan
- SSH, Git, Composer and WP-CLI on the account
- Per-site PHP version switching from the control panel
- First reply inside two hours, inside one when a site is down
Why HostingFast
Standard on every plan
Fast where the cache cannot reach
NVMe storage and a low accounts-per-server count keep logged-in screens responsive, which is where your own team spends the day.
Profiling rather than guessing
PHP X-Ray on CloudLinux Pro at the top shared tier traces a live request and names the slow call instead of leaving you to bisect plugins.
A short hop for admin work
Control-panel, SSH and file-manager sessions always speak to the origin. From the North East that is 5-15 ms, so the interface keeps its rhythm.
Uptime you can audit
A 99.9% target with a pro-rated credit when a month misses, and nothing stopping you from monitoring it yourself against an uncached URL.
Command line included
SSH, Git and Composer on the account with WP-CLI available, so routine work is scripted rather than clicked.
Restores without a queue
Daily backups restore from the panel in minutes — one file, one database or the lot — at whatever hour it broke.
Quick Start
From order to online
- 1
Time an admin screen
Load the busiest logged-in page with DevTools open and read the waiting phase. That number is your team's actual working speed.
- 2
Count the queries
Profile the page, look at query count and the autoloaded options row, and deal with whichever is unreasonable before considering hardware.
- 3
Fix the public side with coverage
Sample x-litespeed-cache across real URLs and eliminate the causes of misses. The public clock is largely a coverage problem.
- 4
Monitor something uncacheable
Point the external check at a page that must reach the application, then compare what you record against the 99.9% target.
Built In
Loaded onto every plan
- An admin screen timed and recorded, not just the home page
- Query count and autoloaded options checked before buying capacity
- SSH, Git and Composer on the developer-focused plans
- Per-site PHP version switching from the control panel
- External monitoring pointed at a page that cannot be cached
- LiteSpeed caching built into the server rather than patched in by plugin
- A daily backup you can restore without waiting for anybody to be awake
- Human support on duty every hour of every day
- 99.9% uptime as the target, with a pro-rated credit when a month misses
- NVMe SSD storage on every tier, not just the expensive ones
Frequently Asked
What people ask us most often
Why is the WordPress dashboard slower than the public site?
Because it is logged-in traffic, and logged-in traffic is never cached. Every admin screen runs the full PHP and database path that a cached page skips entirely. The cause is usually plugin queries or a bloated autoloaded options row rather than the server, so profile it before you upgrade anything.
What should our external monitor actually check?
A URL that cannot be cached — a status endpoint, or any page that must run a query. Monitoring a cached home page confirms the cache is warm and will happily stay green while the database is refusing connections. Check content as well as status code, so a themed error page cannot pass as healthy.
Does the London origin slow down our admin work from Newcastle?
By 5-15 ms per round trip, which you will not perceive. Control-panel, SSH and file-manager sessions do speak directly to the origin every time — no cache is involved — but at UK distances that is far below the threshold where an interface starts to feel laggy.
How do I find which plugin is costing us time?
Profile rather than bisect. On the top shared tier, PHP X-Ray on CloudLinux Pro traces live requests and attributes time to specific calls, which usually identifies the culprit in one sitting. Failing that, a query monitor on a staging clone with plugins disabled in halves will get you there, just more slowly.
Keep reading
Web Hosting in Athens
Greek audiences, .gr, and the eastern Mediterranean round trip in numbers.
Web Hosting in Brighton
Small studios on the south coast, portfolio payloads and client hosting.
Domain and Hosting on One Order
Buying a name and hosting together, and what that saves you in DNS work.
WordPress Hosting
Managed WordPress on NVMe and LiteSpeed, with staging and backups included.
Domain Names
Find, register and transfer domains — first year free with annual hosting.
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.
Fix both clocks, not just the public one.
NVMe under server-level caching, SSH and WP-CLI on the account, and engineers who answer at whatever hour it broke.
View WordPress Hosting plans