A written report you can act on without us.
A fixed-price technical audit of your WordPress site: performance, security, code quality, plugins, hosting and accessibility, with a prioritised fix list at the end.
The problem
You don’t know what you don’t know.
Most business owners can tell when a WordPress site feels slow or looks dated. Almost nobody can tell why. Is it one plugin? The hosting? The way the site was built in the first place? And almost nobody can spot a security gap just by looking at the front end.
Without a proper look under the bonnet, you’re guessing. You might spend money fixing the wrong thing. Or you spend nothing, and carry a risk you don’t know exists until it becomes a hacked site.
An audit swaps the guessing for a written, specific list. What’s actually wrong. How much it matters. What to do about it, in an order that makes sense for your budget.
You get a document, not a verbal opinion, so you can share it with your team or another developer and everyone’s working from the same facts.
What you get
What the audit covers.
Performance
Page speed, Core Web Vitals, hosting response times and what’s actually slowing the site down, not just a single score with no explanation.
Security
Outdated plugins and themes, weak configuration, exposed files and anything else that leaves the site open to being compromised.
Code quality
How the theme and any custom plugins are built, and whether they follow WordPress conventions or have been patched together in a way that will cause problems later.
Plugins and hosting
Which plugins are worth keeping, which are dead weight, and whether the current hosting is actually suited to the site running on it.
Technical SEO basics
Indexing, redirects, structured data and the technical fundamentals that affect whether search engines can find and understand your content.
Accessibility
Colour contrast, keyboard navigation, image alt text and other basics that affect real visitors, including some your business could be legally required to fix.
Process
How the audit runs.
Access and scope
You give us WordPress admin access and, if relevant, hosting access, and confirm anything specific you want us to look at.
Technical review
We run performance, security and code checks across the site, then a developer works out which findings actually matter for your business.
Prioritise findings
Every issue gets rated by impact and effort, so the report tells you what to fix first, not just what’s wrong.
Written report
You receive a plain-English report with findings, ratings and a prioritised fix list, ready to hand to any developer.
Why Maku
Why a written report, not just a call.
A verbal summary is easy to forget and impossible to hand to someone else. We write everything down, specifically enough that you or another developer can act on it without needing us to translate.
- No obligation to hire us afterwards. The report is written to stand on its own.
- Technical scanning and log analysis run with AI assistance, so the report covers the whole site rather than a sample of it.
- Findings are prioritised by real impact, not ordered to make the biggest line item look most urgent.
- If the audit turns up bigger issues, see our security page for ongoing hardening or our speed optimisation page for performance fixes specifically.
Who this suits
Useful even if nothing’s obviously wrong.
An audit is worth running before a redesign, before you commit budget to a rebuild, when you’ve inherited a site from a previous developer and don’t fully trust it, or simply once a year as a check-up. It’s also useful when everything looks fine on the surface. Some of the most expensive problems, a security gap, a plugin quietly slowing every page down, don’t announce themselves until they’ve already cost you traffic, conversions or a hacked site.
It’s a good first step if you’re not sure whether your site needs a small fix, a proper rebuild, or nothing at all. Rather than guessing based on a hunch or a single complaint from a customer, you get an honest, independent view before you spend a dollar on the next step.
Next steps
Turning findings into action.
Once you have the report, the next move is yours. Some clients hand the fix list to their existing developer and never talk to us again, which is fine. Others ask us to quote on the fixes directly, in which case the audit becomes the scope document for that work rather than a separate cost. Either way, nothing in the report is written to steer you towards hiring us. It’s written to tell you the truth about your site.
What’s actually in the audit report?
A plain-English written report covering performance, security, code quality, plugins, hosting, technical SEO basics and accessibility, each with a rating and specific findings. It ends with a prioritised fix list, ordered by impact, not by what happens to be easiest for us to sell.
How long does an audit take?
We review the site, run the technical checks, and write the report as one fixed-price, fixed-scope piece of work rather than an open-ended engagement. We confirm the turnaround with you when we quote, so the delivery date is agreed before we begin.
Do I have to hire you for the fixes afterwards?
No. The report is written so any competent developer, including your existing one, can act on it. If you’d like us to do the work, we can quote separately, but the audit stands on its own.
What access do you need to run the audit?
Usually a login to WordPress admin and, if performance is a concern, access to the hosting control panel. We don’t need access to anything beyond what’s necessary to assess the site.
Is an audit worth it if the site seems to be working fine?
Often, yes. A lot of what an audit finds doesn’t show up until it becomes a problem: a plugin nobody’s updated in years, a security gap, or a performance issue that’s quietly costing you conversions without an obvious symptom.
Will the audit tell us if we should rebuild instead of patch?
Yes, if that’s the honest answer. The report includes our view on whether the site’s foundation is worth building on or whether a rebuild would cost less than years of ongoing patching. See our custom development page if a rebuild turns out to be the right call.