Find out whether you need a rebuild before you buy one

Who this is for

Platforms that were fine at ten thousand nodes and are struggling at a hundred thousand. Sites where editors wait fifteen seconds to save. Organisations who have been told the answer is a rebuild and would like a second opinion before committing a six-figure budget to it.

What the audit covers

• Application profiling under realistic load — where the time actually goes
• Cache architecture: page cache, dynamic page cache, cache tags and contexts, what's invalidating everything
• Reverse proxy / CDN configuration and hit rate
• Database analysis: slow queries, missing indexes, table growth, entity query patterns
• Views and custom query review at real data volumes
• Search: index configuration, Search API and Solr tuning, facet performance
• Editorial performance — often the complaint that started this, and rarely the same cause as public-facing slowness
• Front-end budget: payload, render-blocking assets, image handling, Core Web Vitals
• Infrastructure sizing and configuration (AWS, Azure, or your provider)

Deliverable	Report with measured baselines, ranked findings, expected gain per fix, and effort estimate. The point is a prioritised list, not a list.
Duration	1–3 weeks depending on platform size
What I need	Codebase access, a database copy or staging environment, and access to whatever monitoring exists.
Then	Implementation, quoted from the findings. Or your team does it — the report is written to be executable by someone else.

Relevant experience

AWS and Azure infrastructure for an EU agency platform serving 500,000+ users with 150+ modules in production, configured alongside DevOps for uptime and scalability. Two years on Czech Radio's platform sustaining a 300,000+ listener audience through continuous publishing.

Cloud migrations, scaling work and performance tuning on platforms where downtime is not an acceptable outcome.