Rio Staffing's website ran on three WordPress sites. In tests, the home page took 3.9 seconds to show its main content on a desktop and 10.9 seconds on a slow phone. I rebuilt it as one Next.js site with the same design. On launch day it scored 100/100 for Lighthouse performance on desktop on every page I tested, and the home page became about 5x lighter. All 364 old addresses redirect to their new pages, and the site went live six days after the project started.
This case study is for business owners whose site runs on WordPress and feels slow or hard to manage. Results come first. The technical details are in one short section near the end.
The Client
Rio Staffing LLC is a boutique direct-hire recruiting firm in Hollywood, Florida, run by Managing Partners Martin Oliveira and Edward Tolosa. It has two divisions:
- Aviation: mainly aviation maintenance (repair stations, A&P and IA mechanics, avionics technicians and maintenance leaders), then aviation manufacturing.
- Nurse: mainly school nurses and summer camp nurses.
Rio has a 4.8 rating from 32 reviews on Google. Its website didn't reflect that. Martin and Edward hired me through Upwork, and they agreed to let me share this case study.
It Started as an SEO Audit
The project began as a technical SEO and AI search (AEO) audit. Here's what I found:
- Three sites instead of one. A WordPress multisite on a premium theme was split across riostaffing.com (7 pages), an aviation subdomain (6 pages) and a nurse subdomain (9 pages and 11 posts). Google saw three thin sites instead of one strong one.
- Mixed signals. Some aviation pages had healthcare wording and descriptions, and the theme's demo menu (Dental, Cardiology) was still on all three sites.
- Missing SEO basics. Generic titles, missing or wrong H1 headings, no structured data, no social preview images, empty blog and job pages in Google's index, broken redirects and dead phone links.
- Slow, heavy pages. Each page downloaded 2 to 3 MB.
- Hard to manage. Rio couldn't easily edit the site or see how it was performing.
I gave Rio two roadmaps: fix the WordPress sites, or rebuild on Next.js. After the audit and a meeting, we decided together to rebuild. Most of the problems came from the setup itself, so fixing them one by one would have meant working against it. The rebuild also let me build the SEO and AI search improvements in from the start.
Same Design, New Engine
Rio asked for a close copy of the old look, and that's what they got. Visitors see the same layout, photos and colors. That matters for this case study: the speed came from the technology, not from stripping the site down.

The Speed Results
I measured both sites with Lighthouse 12.8.2 on launch evening, 10 November 2026. I ran each page 3 times and kept the middle result. I tested the old WordPress site on its old server at the same time, from the same computer, so both faced the same network.
The "main content" column is Largest Contentful Paint (LCP): how long it takes for the biggest piece of content on the screen to appear. My LCP guide explains it in more detail.
| Page | Score: WordPress → new | Main content shown: WordPress → new |
|---|---|---|
| Home | 71 → 100 | 3.9 s → 0.6 s |
| Aviation | 69 → 100 | 3.3 s → 0.7 s |
| Nurse | 70 → 100 | 3.8 s → 0.7 s |
| Contact | 75 → 100 | 3.1 s → 0.6 s |
I also ran the same four pages on desktop with no throttling at all. The new site scored 100 on every page and showed its main content in 0.5 seconds. WordPress scored 64 to 69 and took 2.6 to 3.7 seconds.
Lighthouse's mobile test is much harder: it simulates a slow 4G connection and a phone CPU 4 times slower than a computer. Most real visitors have faster connections than this, but it shows how the site copes with a slow phone.
| Page | Score: WordPress → new | Main content shown: WordPress → new |
|---|---|---|
| Home | 52 → 91 | 10.9 s → 2.3 s |
| Aviation | 64 → 86 | 4.0 s → 2.9 s |
| Nurse | 66 → 90 | 3.7 s → 2.4 s |
| Contact | 67 → 93 | 3.5 s → 2.1 s |
The first launch-day phone scores were lower, between 67 and 75. Google Analytics was loading at the same time as the page and competing with it on a slow phone. I set Analytics to load after the page, and the scores above are from after that fix. Analytics still records every visit.
Much of the speed comes from sending less. Every page now downloads a fraction of what it did:
| Page | WordPress | New site |
|---|---|---|
| Home | 3,143 KB, 94 files | 603 KB, 60 files |
| Aviation | 2,239 KB | 622 KB |
| Nurse | 2,339 KB | 611 KB |
| Contact | 1,913 KB | 462 KB |
The other Lighthouse scores moved too: accessibility went from 76 to 84 to 100, best practices from 75 to 79 to 96, and SEO from 92 to 100 to 100 on every page.
Moving Without Losing Pages
A faster site is no use if Google loses track of the old one. This is how I moved three sites onto one domain without leaving any page behind:
- One domain. Everything now lives on riostaffing.com, with /aviation-staffing/ and /nurse-staffing/ sections, one About page, one Jobs page and articles under each division.
- 364 old addresses redirected. Each one goes in a single step (a 301 redirect) to its new page. I tested all 364 automatically before launch and again after: 364 of 364 passed.
- No lost history. I kept the same Google Analytics property. I set up Google Search Console for the whole domain (there wasn't one before) and linked it to Analytics.
- Quick pickup by Google. I submitted the new sitemap on launch day, and Google read all 38 URLs right away. By the next day, Search Console showed the home page, both division pages, both services pages, the jobs page and a guide as indexed. It reported the breadcrumb and job markup as valid.
- Every page complete. Each page has its own title, description, one H1 heading, canonical address, social preview image and structured data.
A site move usually takes 1 to 3 months to settle in Google, so it's too early for traffic results. I'll add them in a follow-up. For the full process, see my website migration SEO checklist.
Ready for AI Search
More people now ask ChatGPT, Gemini, Claude, Perplexity or Google's AI Overviews to recommend a recruiter. I set the site up so these tools can find Rio and describe it correctly:
- Structured data describes the business (Organization and EmploymentAgency, with the Google Business Profile and separate contacts for employers and candidates), each job (JobPosting), the FAQs and the breadcrumbs. My schema markup guide explains what each type does.
- An llms.txt file gives AI assistants a plain-text summary of Rio's key facts, how it works and the roles it fills.
- AI search crawlers are allowed in robots.txt, including OpenAI's and Anthropic's search bots. My AI crawlers guide explains which ones matter.
- IndexNow sends every new or changed page to Bing and other IndexNow search engines automatically.
- Bing Webmaster Tools is set up and verified. Bing's index feeds ChatGPT search and Copilot.
- ChatGPT Business Hub: OpenAI launched it on 10 November 2026. Rio is claiming its business profile, and the domain check is in place.
An Editor Rio Can Actually Use
Rio edits every page and article in Sanity, an editor that lives at riostaffing.com/studio. Published changes reach the live site within seconds, and a live preview shows edits before they go out.
- Approval step. Martin approves content in the editor. If anyone changes it later, it shows as "changed since approval", and publishing unapproved content asks for confirmation.
- SEO checks built in. The editor flags missing image alt text, short articles, missing subheadings, articles with no links to or from other pages, and content not updated in a year.
- Performance at a glance. An overview screen shows live Google Analytics and Search Console numbers inside the editor, with no API keys stored anywhere.
- One place for key facts. Facts like the replacement guarantee are stored once, so a single change updates every page.
- Live jobs. Open positions come in every hour from Rio's recruiting software, Recruiterflow, each with Google job markup, including the pay range where Rio lists one.
- Leads tracked. Forms go straight to Rio's inbox with the lead source attached. Calls, emails, bookings and job applications are tracked in Google Analytics.
- Safe and documented. Content is backed up to GitHub every night, and the team has a PDF editor guide and a video tour.
Timeline
| Date | What happened |
|---|---|
| 4 Nov | Audit, kickoff meeting and the decision to rebuild |
| 5 Nov | First working preview online, built in a day |
| 6 to 9 Nov | Rio reviews the preview; content, design and redirect checks |
| 10 Nov | Martin approves the preview in writing, and the new site goes live the same afternoon |
The original plan had launch on 1 or 2 December, so the site went live about 3 weeks early. Rio wanted to stop paying for the old server as soon as possible, so I moved the launch up. Switching the domain caused no downtime. Before the old server is shut down, the whole WordPress site (database and files) is archived in Rio's own Google Drive.
The Technology, in Short
- Next.js builds every page ahead of time, so visitors get a ready-made page instead of one assembled on each visit. It's served from Vercel's global network.
- Sanity is the editor Rio uses to write and publish content.
- Vercel hosts the site.
- Rio owns every account: GitHub, Sanity, Vercel and the domain. Nothing is locked to me.
- Security headers are in place, including an enforced Content Security Policy.
Moving off WordPress isn't the answer for every site. Many slow WordPress sites can be fixed where they are. For Rio, with three sites, a heavy theme and an editor the team found hard to use, a rebuild was the faster route to a site that's quick, easy to edit and easy for search engines to read.
Is Your WordPress Site Slow or Hard to Find?
Rio's project started with an audit. My technical SEO audit ($255, 2-day delivery) finds what's holding your site back, from speed to indexing, and gives you a prioritized fix list. If the platform itself turns out to be the problem, I can rebuild it the way I rebuilt Rio's. For a first look, request a free website review.
Request a free website reviewFrequently Asked Questions
Related Guides
- Plan a website migration without losing rankings.
- Understand Core Web Vitals.
- Make your main content load faster.
- See what gets a site cited in ChatGPT.

