---
title: "WordPress audit: performance, SEO and security"
description: "A WordPress audit with Lighthouse and a code review: mobile performance, accessibility, bilingual SEO and security. Every finding fixed and re-measured."
url: https://lazarosantana.dev/en/services/wordpress-audit/
---

service · audit · performance, SEO and security

# WordPress audit *for your site*

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.

[Tell me your case](https://lazarosantana.dev/en/contact/#form) [See the case](https://lazarosantana.dev/en/cases/ratioweb/)

What I check

Performance, accessibility, SEO, security and best practices

How

Lighthouse on mobile and desktop, and five auditors in parallel

Result

Every finding fixed and measured again

Mode

Remote from Havana

// what it solves

## What it solves

Concrete problems that already came up in a real project, not a list of promises.

01

### Performance

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.

02

### Security

Over 80 unescaped outputs across seven templates, jQuery 3.5.1 with known vulnerabilities and no security headers. All closed from the theme itself.

03

### Accessibility

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.

04

### Bilingual SEO

Duplicate headings, a broken hierarchy and the same placeholder meta description on 11 pages. Twenty-one changes: headings, metas, breadcrumbs, hreflang and structured data.

// proof

## Real proof

**131*/131*** findings closed, none pending

**37*+*** mobile performance points, from 51 to 88 in production

**100** in SEO on mobile, in production

**2** languages, Spanish and English, on the same theme

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.

case 02 · corporate site · Canada

### A bilingual corporate site, audited

Security, accessibility, performance and SEO end to end: from 51 to 88 on mobile, with all 131 findings closed.

*ratioweb.ca*

Home page of ratioweb.ca, a technology services agency site

// how it works

## How it works

01 · case 02 · measure 03 · review 04 · fixes 05 · measure again

01

### Your case

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.

- scope
- report or fixes
- access

02

### Measure first

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.

- Lighthouse
- mobile and desktop
- starting point

03

### Parallel review

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.

- five auditors
- work list
- code per finding

04

### Fix

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.

- in the theme
- patches
- read-only

05

### Measure and hand over

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.

- production
- before and after
- no promises

I have a WordPress site in Spanish and English and it is slow on mobile

I measure it first with Lighthouse. Do you want just the report or the fixes too?

Both, if possible

We agree it in the scope and I tell you how we go on

example conversation

**Performance51 *to fix***

- 15.6 s LCP
- 13 unoptimized PNGs

**Accessibility76 *to fix***

- invisible focus
- several H1s per page

**Best practices74 *to fix***

- jQuery 3.5.1 with vulnerabilities
- no security headers

**SEO85 *to fix***

- same meta on 11 pages
- broken heading hierarchy

ratioweb.ca · initial measurement, local, 16 Jul

every finding with its code

real example: ratioweb.ca

**Performance88 *✓ measured***

- measured in production
- variation between runs

**Accessibility100 *✓ measured***

**Best practices100 *✓ measured***

**SEO100 *✓ measured***

ratioweb.ca · production · 17 Oct 2026

// questions

## Frequently asked

### 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.

### Do you guarantee a Lighthouse 100?

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.

### What about plugins or code that aren’t mine?

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.

### What tools do you use?

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.

// let’s talk

## Got something like this in mind?

Tell me what you sell, to whom and what has to happen. I reply within 24 h.

[Tell me your case](https://lazarosantana.dev/en/contact/#form)
