The layer most agencies hand to a hosting company and stop thinking about. We run our own, which is the only reason we can promise anything about speed and mean it.
Nobody notices infrastructure until it fails. That is precisely why it deserves attention before it does.
Your site on a server we configure — not shared hosting where a thousand other sites compete for the same CPU. Tuned for what you are actually running.
Caching, compression, image handling, database indexing and PHP tuning. The work behind a score going from the fifties to the nineties.
Ubuntu, Nginx, PHP-FPM, MariaDB, certificates and firewall, configured properly rather than left on defaults. Defaults are safe, not fast.
SSH keys with password login disabled, firewall rules, intrusion protection, and permissions set so a compromised application cannot take the machine.
Scheduled and stored off the server. A backup nobody has ever restored is a hope, not a backup.
Uptime, disk, memory and certificate expiry watched. We would rather find out before you do.
Records configured correctly, including SPF, DKIM and DMARC so your email reaches inboxes rather than spam folders.
Moving from shared hosting or another provider, sequenced so the site does not disappear mid-transfer.
Server response, database queries, asset sizes, or simply the wrong host. Guessing at performance problems wastes money on the wrong fix.
Not the biggest instance available, and not the cheapest. Enough headroom for your traffic pattern, which is usually less than people fear.
Nginx tuned, PHP-FPM pools sized, OPcache on, database indexed. Default configurations are written to be safe everywhere, which means fast nowhere.
Firewall, key-only SSH, intrusion protection, least-privilege database users. Done at setup, because retrofitting security is how things get missed.
Both configured and verified before the site goes live, rather than after the first incident makes the case for them.
DNS lowered in advance, files and database moved, tested on the new server before the switch. Downtime measured in minutes, not hours.
If the site earns you money, usually yes. Shared hosting is fine for a brochure site nobody depends on. Once you are taking bookings or selling, the difference between a two-second and a six-second load shows up in revenue — and shared hosting cannot be tuned.
No, and we mean that. Hosting with us is how we can promise speed, but every build can be deployed wherever you like. We hand over the code and help you set it up.
We monitor uptime and get alerted before most clients notice. Backups are off-server so a failed machine does not take your data with it. We do not offer a formal SLA — a small studio honestly cannot — and we would rather say that than pretend.
Usually. We run a diagnostic first and tell you whether the problem is the server, the code or the theme. Sometimes the honest answer is that the site is beyond tuning and rebuilding costs less than fighting it.
It runs your URL through Google’s PageSpeed Insights and shows the real score, Core Web Vitals and the biggest opportunities. Same data Google uses. It is genuinely useful on its own, and it is free because it is how most people find us.
The free tool on our homepage tells you where you stand in about a minute, using Google’s own measurements.
Only to see which pages help and which don’t. Nothing is sold, nothing is used for advertising, and declining changes nothing about how the site works. More in our privacy policy.