Case study · rebuild and go-live
rgbcorp.eu: rebuilt on a staging copy and moved to production.
We rebuilt the site on a private copy, tested it, and moved it to production in a planned switch. Then we checked the live site and fixed what came up. These are lab numbers, not real-user data, and they are shown exactly as they ended up.
Send a site →Same client: the hacked-site cleanup →
- 28 Oct 2026Audit of the live site
- Staging copyEvery change made and tested on a private, password-protected copy
- 2 Nov, afternoonPlanned switch from staging to production
- 2 Nov, 21:38–21:48Live check and same-night fixes
The challenge
This is what we saw on the live site in our audit of 28 October:
- The mobile home page weighed 27.6 MiB and made 237 requests. Mobile score: 58.
- There was no cookie notice, and Google Analytics loaded before visitors could choose.
- It was still on WordPress 6.9.4, not the latest release.
- Spanish pages were not marked as Spanish for Google.
And it had to be improved without touching the live site while we worked.
What we did
- Staging copy
- Every change was made and tested on a private, password-protected copy, with a snapshot before each step.
- Planned switch to production
- On the afternoon of 2 November. We kept the previous tables and folders so we could roll back quickly. We rehearsed that rollback on the copy; it was not needed.
- Speed
- The cover video downloads once, in a light version. The full film only loads when you press Play. Home page images have responsive sizes and lazy loading.
- Privacy
- A cookie notice in English and Spanish, with Accept, Reject and Preferences at the same level. Analytics, embedded videos and Instagram wait for the visitor's consent.
- Legal pages and Spanish
- Legal notice, terms and cookie policy in both languages. Spanish pages paired with the English ones for Google. One shop per language: /shop/ redirects to /store/.
- Live check and same-night fixes
- Checking the site after the switch, we saw that Analytics was loading before consent again. We fixed it that night and measured again on 2 November between 21:38 and 21:48.



Results
Before = audit of the live site, 28 Oct 2026. After = check of the live site, 2 Nov 2026. Same tools, read-only. Only what we measured and verified is marked as improved.
Lighthouse 13.5.0 · 28 Oct vs 2 Nov 2026.
Before and after: the cookie notice
Before · 28 Oct 2026

After · 2 Nov 2026

About the data
There is no real-user data (CrUX). Everything above is lab data.
Is your site slow, loading things before consent, or a mystery inside?
We tell you what we see and what we would fix. The audit is $500, credited if you approve the repair within 14 days.
Send a site →info@remotemend.com
Figures come from the audit of 28 Oct 2026 and the checks of 2 Nov 2026 on the live site (Lighthouse 13.5.0, Chrome, wordpress.org). Technical observations, not legal advice.