---
title: "WordPress audit: mobile Lighthouse from 51 to 88"
description: "ratioweb.ca case: bilingual WordPress corporate site audited end to end. 131 findings closed and mobile Lighthouse performance from 51 to 88 in production."
url: https://lazarosantana.dev/en/cases/ratioweb/
---

case 02 · corporate site · Canada

# Bilingual corporate site, *audited*

ratioweb.ca is the website of a tech services agency, in Spanish and English. I inherited the theme already built, fixed its responsive design across the whole site and then measured it, corrected it and measured it again until mobile performance went from 51 to 88 in production.

[View live site](https://ratioweb.ca) [How I audited it](https://lazarosantana.dev/en/cases/ratioweb/#recorrido)

*ratioweb.ca*

Home page of ratioweb.ca, a bilingual corporate site for tech services

**131 */131*** audit findings closed

**51*→*88** mobile performance

**88** Perf.

**100** Access.

**100** Pract.

**100** SEO

Lighthouse mobile · ratioweb.ca in production

Client

Ratio Web, tech services agency in Canada

Starting point

Theme created in 2021 by the original team; I have been in charge of it since 2025

My role

Responsive, performance, accessibility, security, SEO, forms and maintenance

Languages

Spanish and English with Polylang, one theme, two sites

// the challenge

## It looked good but measured badly

The site worked and people liked it. But the first mobile measurement gave **51 out of 100 in performance**, an LCP of 15.6 seconds, accessibility and security failures nobody could see at a glance, and a layout that needed fixing on mobile and tablet.

An agency site sells trust. If it loads slowly or fails with the keyboard, the visitor notices before reading a single word.

01

### Performance

Mobile 51/100. FCP of 9.2 s and LCP of 15.6 s. Heavy PNG images, loose fonts and scripts that blocked rendering.

02

### Accessibility

Mobile 76/100. Borderline contrast, invisible focus, a mobile menu built with a div and several H1s per page.

03

### Security

More than 80 unescaped outputs across seven templates, jQuery 3.5.1 with vulnerabilities and no security headers.

04

### Bilingual SEO

Mobile 85/100. Duplicate headings, a broken hierarchy and the same filler meta description on 11 pages.

// audit walkthrough

## From 51 to 88 on mobile

Six fronts, the same method: measure, fix and measure again. Scroll down and watch them in order.

01 · measure

### Measure before touching anything

Lighthouse on mobile and desktop, and five auditors in parallel: security, SEO, accessibility, performance and best practices. They surfaced 55 findings, each with its own code in a work list.

/wp-audit · built Lighthouse · third-party

02 · security

### Close what you cannot see

Every output goes through `esc_html` or `esc_attr`, `$_SERVER` inputs are sanitized, jQuery is upgraded to 3.7.1 and the site sends security headers. XML-RPC and pingbacks are closed.

inc/performance.php · built templates · improved

03 · performance

### Less weight, less waiting

CSS split per page, 13 PNGs converted to WebP, one variable font instead of six files, scripts with `defer` and the LCP logo at high priority. One-year cache for whatever does not change.

inc/performance.php · built Tailwind per page · improved

04 · accessibility and SEO

### For people and for search engines

Thirty-five accessibility fixes: visible focus, skip link, mobile menu with a button and keyboard support, contrast and a single H1. In SEO, 21 changes: headings, metas, breadcrumbs, hreflang and structured data.

templates · improved Rank Math · configured Polylang · third-party

05 · responsive

### A layout that fits every screen

The theme did not adapt well to mobile and tablet. In three rounds, between November 2025 and July 2026, I adjusted navigation, home, MVP and web portal pages, typography, footer, cards and spacing, until mobile, tablet and desktop were covered.

CSS and templates · improved mobile menu · improved

06 · forms

### Forms that notify properly

The contact form uses Contact Form 7 with Turnstile and a honeypot trap. Each error is shown under its field, in both languages, and the notification to the team goes out by email and Telegram.

Contact Form 7 · improved Turnstile · third-party Fluent SMTP · third-party

**initial measurement · mobile** step 1 / 6

Performance **51**

Accessibility **76**

Best practices **74**

SEO **85**

5 auditors 55 findings

**security** step 2 / 6

~80 unescaped outputs 7 templates

jQuery 3.5.1 → 3.7.1 vulnerability

XML-RPC and pingbacks closed

Security headers send_headers

REQUEST_URI unsanitized sanitized

**performance** step 3 / 6

**−3.9 MB** 13 PNGs converted to WebP

**−158 KB** one variable font instead of six

**64–110 KB** CSS per page, previously 178 KB in a single file

**−1,050 ms** jQuery with defer off the critical path

figures from the optimization commits

**accessibility and SEO · mobile** step 4 / 6

**76** Accessibility

**85** SEO

35 accessibility fixes 21 SEO

**responsive** step 5 / 6

mobile tablet desktop Nov 2025 · Mar and Jul 2026

**contact** step 6 / 6

*Enter a valid email address*

Cloudflare Turnstile **verified**

submit → Contact Form 7 validates

→ error under each field, in the page language

**✓ Turnstile resets after the error is shown**

// real problems

## What breaks when optimizing

Six cases taken from my commits on this project. Each card carries the commit that solved it.

`fix · 27bcba48` built

### Animations waited for a gesture that never came

With AOS deferred, animations only started after a scroll or a click. Now they start on their own after a second, without double initialization.

`fix · 64daad4b` improved

### The async CSS trick left the site unstyled

Loading the stylesheet with `media="print"` made unstyled content flash on slow servers. With per-page CSS it was no longer needed, so I removed it.

`fix · e14b34cf` improved

### Turnstile wiped the form errors

The plugin reset its widget on the `submit` event and took the CF7 messages with it. A theme filter moves it to `wpcf7submit` without touching the plugin.

`fix · 55494cb4` improved

### The logo, which is the LCP, was lazy-loaded

PageSpeed flagged it with `loading="lazy"` and no priority. Since the WordPress filter does not act on SVG, the theme writes the logo directly in the three positions.

`fix · c823397c` improved

### Mobile broke on small details

Headers with too much space above, service cards that did not fit together and the mega menu without its touch selector. One commit closed it across four templates.

`fix · f3f8e4d1` improved

### The form was not styled in Spanish

The contact styles were loaded by slug, and in Spanish the page is called `contactenos`. They now load by template and work in both languages.

// under the hood

## What's behind the website

Where a visit goes

visitor**Browser** in Spanish or English, mostly from a phone

Ratio Web team**WordPress dashboard** site texts and options with ACF, without touching code

search engines**Google** sitemap, hreflang and structured data from Rank Math

// server

### WordPress + ratio_web theme

inc/performance.php*cache, headers, cleanup**built*

PHP templates*home, services, contact, 404**improved*

Tailwind 2 per page*CSS split per template**improved*

Rank Math*technical SEO and breadcrumbs**configured*

ACF Pro + Polylang*fields and two languages**third-party*

Megamenu*services menu**third-party*

build and review

Tailwind · PostCSS · pnpm Playwright · tests · improved Jenkinsfile · team

cache and bots**Cloudflare** page cache and Turnstile on the forms

email**Fluent SMTP** form notifications always arrive

notifications**Telegram** every new contact reaches the team chat

New Improved Existing

// method

## Measured, not assumed

### The cycle of every finding

Nothing is taken for granted. Every fix goes back through the same measurement that found it, and the work list is only closed with evidence.

01**Measure** Lighthouse and 5 auditors

02**Fix** one finding, one change

03**Measure again** and close with its result

### Rules I left in the theme

**Security headers** and XML-RPC closed from the theme itself

**One-year cache** for whatever does not change, with `immutable`

**Responsive images in WebP** with srcset, sizes and dimensions to avoid layout shifts

**Preloaded font** WOFF2 with `font-display: swap`

**Forms with a double filter** Turnstile and honeypot against bots

// result

## Audit by the numbers

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

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

**100** in SEO on mobile and in best practices on desktop

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

Lighthouse measured on www.ratioweb.ca, in production, on October 17, 2026: mobile 88, 100, 100 and 100; desktop 89, 100, 100 and 92. There is some variation between runs. The initial measurement of 51, 76, 74 and 85 was taken locally on July 16, before the audit.

WordPress PHP Tailwind CSS PostCSS ACF Pro Polylang Rank Math Contact Form 7 Cloudflare Turnstile Lighthouse Playwright

// next case

03 · stores · Cuba

### Three stores, one engine

A core plugin with Cuba's provinces, zones and rates, shared by three WooCommerce stores in production.

*tubandeja.com*

Home page of tubandeja.com, a WooCommerce store

[Need something like this? → WordPress audit](https://lazarosantana.dev/en/services/wordpress-audit/)

[← all cases](https://lazarosantana.dev/en/#trabajo) case 2 of 4

// your project

## Want something like this for your business?

Tell me what you need. I reply within 24 hours and, if it is a fit, you get a fixed written proposal.

[Request a quote](https://lazarosantana.dev/en/contact/#form) [See services](https://lazarosantana.dev/en/services/)
