Is auditing the same as fixing?
In the ratioweb.ca case every finding was fixed and measured again. Whether your brief is the report only or the fixes too is agreed when we talk about scope.
I audit WordPress sites with Lighthouse and a code review: mobile performance, accessibility, bilingual SEO and security. Every finding is fixed and measured again, not left in a report. On ratioweb.ca, mobile performance went from 51 to 88 and all 131 audit findings were closed.
Performance, accessibility, SEO, security and best practices
Lighthouse on mobile and desktop, and five auditors in parallel
Every finding fixed and measured again
Remote from Havana
Concrete problems that already came up in a real project, not a list of promises.
On ratioweb.ca the first measurement was 51 out of 100 on mobile, with a 15.6 s LCP. Among other things, 13 PNGs became WebP and one variable font replaced six files.
Over 80 unescaped outputs across seven templates, jQuery 3.5.1 with known vulnerabilities and no security headers. All closed from the theme itself.
Mobile accessibility was 76 out of 100 at the start: invisible focus, a mobile menu built with a div and several H1s per page. Thirty-five fixes later.
Duplicate headings, a broken hierarchy and the same placeholder meta description on 11 pages. Twenty-one changes: headings, metas, breadcrumbs, hreflang and structured data.
Lighthouse measured on www.ratioweb.ca, in production, on 17 October 2026: mobile 88, 100, 100 and 100. The initial 51, 76, 74 and 85 were measured locally on 16 July, before the audit, and there is some variation between runs.
You tell me what site you have and what worries you. We agree whether you want only the report or the fixes too, because the scope changes.
I run Lighthouse on mobile and desktop before touching anything. That way we know where we start and every improvement can be compared with a number.
Five auditors review the code at once: security, SEO, accessibility, performance and best practices. Each finding goes into a work list with its own code.
I fix each finding in the theme itself and tick it off the list. Anything third-party, like the client’s plugins, stays read-only and the changes go in as a patch.
I measure again in production and compare with the first run. I hand over the real scores, with their variation between runs, not a promise of 100.
In the ratioweb.ca case every finding was fixed and measured again. Whether your brief is the report only or the fixes too is agreed when we talk about scope.
No. On ratioweb.ca mobile performance ended at 88 and accessibility and best practices at 100, with some variation between runs. I promise to measure before and after, not a score.
On one of the stores, an audit’s fixes reached the client’s plugins and I reverted them: those plugins stay read-only and the changes are kept as a patch.
Lighthouse and /wp-audit, the claude-wp-builder command, which covers seven areas: security, SEO, accessibility, performance, best practices, GEO and usability. Each finding carries its code in a work list.
Tell me what you sell, to whom and what has to happen. I reply within 24 h.