Skip to main content

Server Performance

Good code on a badly tuned server still loads slowly

We tune the software stack on your server, from PHP workers to web server and database settings, so pages are generated quickly and the server degrades gracefully instead of failing under load.

PatchedCPU 32% · Disk 48%

Business impact

Your server sets the floor for how fast any page can be

Front-end optimisation cannot start until the server responds. A slow time to first byte delays everything that follows, and an untuned server tends to fail abruptly when traffic spikes.

High time to first byte

If the server takes a long time to begin responding, every page and every visitor waits, regardless of how well the front end is built.

Outages during peak demand

Exhausted PHP workers or memory cause 502 and 504 errors exactly when campaigns, sales or seasonal traffic bring in the most visitors.

Unclear hosting decisions

Without tuning and measurement it is hard to tell whether you need a bigger server or simply a better configured one.

Common issues

Problems we regularly solve

PHP-FPM pool misconfiguration

Too few child processes queue requests; too many exhaust memory and push the server into swap. Default values rarely match real workloads.

OPcache disabled or undersized

Without enough OPcache memory, PHP recompiles scripts repeatedly, wasting CPU on every request.

Outdated PHP versions

Older PHP releases are slower and, once past their end-of-life date, no longer receive security fixes.

Web server not doing its share

Missing compression, no HTTP/2 or HTTP/3, poor static file caching headers or Apache .htaccess rules evaluated on every request.

MySQL competing for memory

Database, PHP and caching services sized independently on the same machine, so together they exceed available RAM.

Unexpected traffic from bots

Aggressive crawlers and automated requests consume workers that should be serving customers.

What's covered

What's included in server performance optimisation

We work on self-managed VPS, cloud and dedicated servers, and within the limits of managed hosting where configuration access is restricted. Ongoing server care is covered by server management.

PHP runtime tuning

PHP version upgrades planned with compatibility testing, PHP-FPM process manager settings sized to memory, OPcache sizing and realpath cache settings.

Web server configuration

Nginx, Apache or LiteSpeed tuned for keep-alive, compression with Brotli or gzip, HTTP/2 or HTTP/3 and long-lived caching for static assets.

Server-level caching

FastCGI cache, LiteSpeed Cache or Varnish for full pages, with sensible exclusions for carts, accounts and logged-in users.

Database server settings

InnoDB buffer pool, connection limits and temporary table sizes balanced against PHP and cache memory on the same host.

CDN and edge configuration

Offloading static assets and, where appropriate, cached HTML to a CDN such as Cloudflare to reduce origin load and latency for distant visitors.

Load and bot management

Rate limiting and bot rules to protect PHP workers, plus controlled load testing to understand where the server reaches its limits.

Maintenance activities

What we do, and how often

Exact frequencies depend on your plan and platform. This is a typical schedule.

On onboarding

  • Resource baseline: CPU, memory, disk I/O and PHP worker usage
  • Configuration review of PHP, web server and database
  • Access log analysis for heavy endpoints and bot traffic

On demand

  • Configuration changes applied with rollback plan
  • PHP version upgrades after staging compatibility tests
  • Controlled load tests before major campaigns or launches

Monthly

  • Review of resource graphs and error logs
  • Check of PHP worker saturation and slow request logs
  • Server performance notes in the monthly report

Quarterly

  • Capacity review against traffic trends
  • Recommendation on scaling or hosting changes if needed

Our methodology

How we work

01

Baseline the server

We gather metrics on response times, worker usage, memory pressure and error rates to understand normal and peak behaviour.

02

Find the constraint

We determine whether CPU, memory, disk, PHP workers or the database is the limiting factor, because tuning the wrong layer achieves little.

03

Tune incrementally

Settings are changed one area at a time with configuration backed up, so each change can be measured and reversed if needed.

04

Test under load

Where appropriate, we run controlled load tests against staging or during quiet periods to confirm the server behaves predictably.

05

Document the configuration

Final settings and the reasons for them are documented, so future changes and hosting moves start from a known state.

Business benefits

What you gain

Lower server response times

A well-tuned stack generates uncached pages faster and serves cached ones almost instantly.

More predictable behaviour under load

Correctly sized pools and caches are designed to slow down gradually rather than fail suddenly during traffic peaks.

Better value from existing hosting

Tuning often recovers capacity you are already paying for before you consider larger servers.

A documented, reproducible setup

Clear configuration records make troubleshooting, scaling and migrations faster and less risky.

Technologies supported

  • PHP-FPM
  • PHP OPcache
  • Nginx
  • Apache
  • LiteSpeed
  • Varnish
  • MySQL and MariaDB
  • Redis
  • Cloudflare
  • HTTP/2 and HTTP/3
  • Brotli
  • Ubuntu and Debian
  • AlmaLinux and Rocky Linux
  • k6

Running something not listed? Ask us – we'll tell you honestly if it's a fit.

Who it's for

Who needs server performance optimisation?

Businesses on VPS or cloud servers

Organisations running their own servers on AWS, DigitalOcean, Hetzner or similar without a dedicated systems administrator.

Stores preparing for peak trading

E-commerce teams who want confidence before seasonal sales or major campaigns.

Agencies hosting client sites

Agencies running many client sites on shared servers they manage themselves.

Industry guidance: E-commerce · Digital Agencies · SaaS Companies

FAQs

Server Performance Optimisation: common questions

Can you optimise a server on managed or shared hosting?
Partly. On shared and some managed hosting, server settings are controlled by the provider, so we focus on what can be changed, such as PHP version, caching and application settings, and tell you clearly where the hosting itself is the limit.
What is TTFB and what affects it?
Time to first byte is how long the browser waits before the server starts sending the page. It is affected by network distance, server load, PHP execution, database queries and whether a cached copy can be served.
Will upgrading PHP break our website?
It can if themes, plugins or custom code are incompatible. That is why we test upgrades on staging, review error logs and fix or replace incompatible components before upgrading production.
Do you run load tests against our live site?
Only with your agreement and usually against staging or at agreed quiet times, because load testing a live server can affect real visitors and may breach some hosting terms.
Which web server do you recommend?
Nginx, Apache and LiteSpeed can all perform well when configured properly. We usually optimise what you have, and only recommend a change when there is a clear benefit for your workload and hosting.

Get more from the server you already have

Book a consultation to review your server metrics and configuration with one of our engineers.