phpinfoFile
Get a Free Server Check

PHP server case studies.
Start with the evidence.

A slow store. A failed upgrade. An error with no clear cause. Good server work starts by finding what changed.

These are illustrative repair scenarios, not published client results. They show how we approach PHP problems and what to check before calling a fix complete.

Get a Free Server Check

PHP guidance since 2010 · Audits, fixes & optimization

Three problems. Three paths to a fix.

For site owners, agencies and software teams: use these scenarios to frame the issue, then test against your own site.

Slow store pages

01 / Performance review

Pages drag when traffic rises. The cause may sit in PHP, the database or the cache.

Before: capture
Record slow page requests and server load under a known test.
Investigate
Review database queries and OPcache, which stores compiled PHP code for reuse.
After: verify
Repeat the same test. Compare response times and check that checkout still works.
Explore performance work

An upgrade breaks the site

02 / PHP version review

A new PHP version reveals old code or a missing extension. Changing versions alone will not resolve every fault.

Before: capture
Note the old and new versions, error logs and the steps that trigger failure.
Investigate
Check app requirements and test code changes on a separate copy of the site.
After: verify
Test key journeys, scheduled tasks and a rollback plan before the live move.
Explore PHP upgrades

Uploads keep failing

03 / Configuration review

A file fails to upload even though the app accepts its format. Several server limits can affect one request.

Before: capture
Record the file size, error message and active PHP settings.
Investigate
Compare upload limits, request limits and web server rules with the app’s needs.
After: verify
Retry the same file. Check that larger files still meet the intended limits.
Explore configuration work

A useful result needs context.

A faster number means little if the test changed. Keep the same page, load and cache state when comparing results.

See how we work
  1. 01

    Keep a baseline

    Save the starting settings and test results before making changes.

  2. 02

    Track the change

    Record what was fixed and why, so the next review has a clear starting point.

  3. 03

    Check the whole task

    Confirm that forms, payments and background jobs still work as expected.

Have a server problem like these?

Share your site URL, the symptom and any recent changes. Leave passwords and private server details out of your message.

Audit → Fix → Optimize → Support

Get a Free Server Check