Latency notes · Electricians
Electricians: time to first byte is the hosting number
Half of what gets blamed on hosting is a plugin running a database query on every page load, and one measurement tells the two apart.
The short answer
Time to First Byte is the part of page speed a host owns, and it is the number to check before changing anything else. Under 800 milliseconds is the threshold to hold yourself to; on a cached LiteSpeed response you should comfortably beat it, and if you do not, the cause is nearly always PHP work happening on every request.
For an electrician's site that work is usually a quote form plugin, a certification-badge script or an end-of-life PHP version. Switch the site to the current PHP release from cPanel, audit what runs on every page load, and only then look at the server.
Every plan carries NVMe storage behind a LiteSpeed cache, free SSL, engineer-run migration and 24/7 support, with renewals billed at the original rate.
By the HostingFast team · Reviewed 12 August 2026
NVMe
Disk under the database
Free
Domain, year one included
99.9%
Uptime, and a credit if not
Flat
Renewal, no step up
An electrician's site is mostly small: service pages for rewires and consumer units, an EICR explainer, certification marks, a quote form, a few job photographs. It should be quick by default, and when it is not, the reason is specific rather than general.
That specificity is the useful part. The site is slow cannot be actioned. First byte is 1.4 seconds on an uncached hit because the quote plugin queries the options table twice per page load can be fixed in an afternoon.
So this page is about separation: which measurement tells you the server is the problem, which tells you the page is, and what to do in each case.
Separate the server from the page
There are two numbers and they answer two different questions. Time to First Byte is how long the server took to begin replying: DNS, connection, TLS, then PHP and the database. Largest Contentful Paint is how long the browser then took to draw the main thing on screen. A host can move the first; only the page can move the second.
Get both in one place. In Chrome DevTools, open Network, reload, click the document request and read Waiting for server response under Timing. That is your TTFB. Then read the LCP entry in the Performance panel, or take the field figure from PageSpeed Insights, which reports real Chrome visits at the 75th percentile.
What a quote form costs on every request
Form plugins are the usual reason an otherwise small site has a slow first byte. Many register hooks that run on every page rather than only on the page holding the form, and several add their own stylesheet and script to all of them. Install Query Monitor on a staging clone and look at the query count and the slowest queries on a service page that contains no form at all.
A well-behaved site does its database work in a couple of dozen queries. If a page with no form is running two hundred, you have found your afternoon's work. The same audit usually catches a review-badge script and an analytics plugin storing hits in your own database, which is the most reliable way there is to make a small site feel heavy.
PHP version is the cheapest change on the list
PHP version is switchable per site from the control panel, which means you can test it on one and leave the rest alone. Moving a site from an end-of-life release to the current one shortens the PHP portion of TTFB noticeably on most builds, and it costs nothing but a compatibility check.
Do it on a staging clone from WordPress Toolkit rather than live, load the quote form, submit a test enquiry, then check the error log before promoting the change. If a plugin has not been updated since PHP 7, this is where you find out, and finding out on a clone is considerably better than finding out on a Monday morning.
Hold a budget after you have won
Speed regresses. It regresses because someone adds a slider, a badge or a booking widget, and each addition looks small on its own. A written budget stops that: under 800 ms first byte, under 2.5 seconds largest paint on 4G, under 200 ms interaction, under 1 MB total on a service page.
Re-run the same measurement on the same URL once a quarter and after any theme or plugin change. Keep the screenshots. Being able to point at the run where the number moved is worth more than any amount of arguing about whether the site feels quick.
The parts of the stack you can actually tune
Per-site PHP version switching, a LiteSpeed cache in front of PHP, NVMe under the database, and SSH with Git and Composer if you would rather work from a terminal than a dashboard.
Free SSL renews itself, migration is run by our engineers at no charge, and support answers at any hour rather than during weekday office hours.
- MultiPHP sets the PHP version per domain from cPanel
- LiteSpeed answers ahead of every PHP request
- SSH with Git and Composer, Sprint upward
- A staging clone to test the version bump on
Why HostingFast
Standard on every plan
PHP you control
Switch version per site from the control panel and measure the difference in first byte yourself, rather than filing a ticket about it.
Cache before PHP
LiteSpeed answers a cached service page without starting the interpreter, which removes the plugin overhead entirely for most visits.
A terminal if you want one
Full SSH with Git and Composer included, so deployments and plugin audits do not have to happen through a browser.
Clone, test, promote
WordPress Toolkit staging lets you trial a PHP bump or a plugin removal without the live site ever seeing it.
Malware sweeps included
ImunifyAV+ scans every site, which also catches the injected script that quietly doubled your page weight.
Support that reads logs
Humans at any hour who will look at the actual error log rather than confirm the server responds to a ping.
Quick Start
From order to online
- 1
Record both numbers
Note TTFB from the DevTools Timing tab and LCP from PageSpeed field data. One of them is the host's job and the other is the page's, and knowing which is which saves you a week.
- 2
Audit what runs everywhere
Install Query Monitor on a staging clone and look at query counts on a page with no form. Anything running site-wide that only needs to run on one page is the first thing to go.
- 3
Bump PHP, then re-measure
Change the version on the clone, exercise the quote form, check the error log, promote it, and re-run the same TTFB test to confirm the figure moved.
Built In
Loaded onto every plan
- PHP version chosen per domain in cPanel's MultiPHP manager
- A LiteSpeed cache layer ahead of every PHP request
- NVMe SSD under the database on every plan
- Full SSH access with Git and Composer on tap
- WordPress Toolkit staging clones for testing a PHP bump
- Free SSL, issued and reissued without you asking
- A backup taken daily, restored in one click
- ImunifyAV+ malware sweeps running across every site
- Softaculous covers 240+ one-click application installs
- 24/7 human support with a two-hour first-reply target
Frequently Asked
What people ask us most often
How do I tell whether my host or my site is the slow part?
Read Time to First Byte on the document request in DevTools. If it is under 800 milliseconds and the page still feels slow, the delay is in what the browser downloads and renders afterwards, which is your theme, your images and your scripts. If TTFB is high on a cached hit, that is a server-side conversation.
Will moving from PHP 7.4 to a current version break my site?
It can, and that is exactly why you test on a staging clone first. Older form and gallery plugins are the usual casualties. Clone the site, switch the version, exercise the forms, read the error log, then promote. Doing it in that order makes it a twenty-minute job rather than an outage.
Is Query Monitor safe to run on a live site?
It is intended for development and it adds overhead, so run it on a staging clone where you can. The information it gives you about query counts and slow queries is the fastest route to finding the plugin doing work on every page load.
Does the LiteSpeed cache remove the need to fix plugins?
For logged-out visitors on cached pages, largely yes, and that is most of your traffic. It does nothing for pages that cannot be cached, for the admin area, or for the first visitor after a purge. Fix the underlying work as well as caching over it.
Keep reading
Car Detailers — Hosting Guide
Detailing galleries, before-and-after weight and the mobile numbers that matter.
DJs — Hosting Guide
Event sites, media payload and the traffic spike after a booking goes live.
Uptime · What It Measures
What uptime is actually measuring, and what a percentage buys you.
Mail Filtering — Built for Electricians
Spam filtering, delivery and keeping enquiry notifications out of junk.
VPS Hosting Plans
Root access, resources you do not share, and when the move is justified.
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.
Find the number, then fix the cause.
Per-site PHP switching, LiteSpeed in front of PHP and NVMe underneath, on every plan.
View Mail Filtering — Built for Electricians plans