Ooi Solutions · Case file
A multi-city hospital group whose website couldn’t show its scale. We spent 16 months fixing that - and measured all of it.
Baseline: Lighthouse mobile, /specialties/orthopedics. Today: Chrome UX Report field data, 28-day window, 15 Jul 2026.
Source: Medicover growth & performance report - GA4, Google Search Console and lead tracking, Nov 2023 → Feb 2025.
Admission notes
Medicover runs hospitals across Telangana, Andhra Pradesh, Maharashtra and Karnataka. Every location and specialty is its own search opportunity. Almost none of them were being captured.
Scope
Documented in full in the Medicover growth & performance report.
Before & after · the pages
These are the live Medicover pages as they were, and as we rebuilt them. Screenshots come straight from the client performance report.
A high-intent service with no page built to convert it.
A globally-searched service buried in dense copy.
Content existed, but nothing made it discoverable.
Screenshots: Medicover growth & performance report.
New capability · built from zero
Not a redesign - formats that didn’t exist on the site before.
Core Web Vitals
Google’s threshold for a good LCP is 2.5 seconds. The orthopedics specialty page was eight times over it.
Where those 20.8 seconds went
Source: Core Web Vitals SOP for Specialities.
Other notable metrics
Source: PageSpeed Insights, 15 Jul 2026 - real-user field data.
The 20.8s baseline is a Lighthouse lab test of one specialty page. The 0.5s is field data for the homepage. Different page, different measurement - a like-for-like re-run of /specialties/orthopedics would close the loop.
Lab performance sits at 65: render-blocking requests (~380ms), 272KiB unused JavaScript, 18KiB unused CSS, 7 long main-thread tasks and a lab CLS of 1.661 all remain open.
The fix list
Not recommendations - the actual changes specified, page by page, in the SOP, with the sample page as the reference implementation.
| Issue found | What we changed |
|---|---|
| LCP at 20.8s | Preload the banner image · move the CSS background to a real <img> · inline critical CSS |
| Render-blocking resources | Defer non-critical scripts · preload key stylesheets |
| Text compression failing | Brotli enabled at the CDN (Cloudflare → Speed → Optimization) |
| Heavy main-thread work | Move or defer scripts not needed for first render |
| Unused CSS | Extract critical CSS with Critical / Penthouse |
| Unused JavaScript | Strip and defer unused bundles |
| Images with no width/height | Explicit width & height, plus CSS aspect-ratio |
| Weak cache policy | Cache-Control: public, max-age=31536000, immutable |
| Oversized images | Serve correctly sized images per breakpoint |
| Offscreen images | Lazy-load anything below the fold |
The unglamorous part
Most of this engagement was infrastructure nobody sees. It’s also the reason the rest worked.
Repeated outages broke crawling and indexing. Rankings can’t hold on a site Google can’t reach.
G-Translator rewrote URL structure into local languages, creating canonical and index conflicts.
Missing pages were recovered from Wayback Machine backups and re-uploaded.
Rebuilt via database and PHP file upload rather than page-by-page.
Spam links identified and disavowed to protect domain authority.
Session drops, click decay and low-quality content tracked and fixed on a rolling basis.
Results
Every chart below is lifted from the client performance report, drawn from GA4, Google Search Console and lead tracking.
Nov 2023 → Feb 2025
Monthly, Nov 2023 → Mar 2025
Jan & Feb, 2024 vs 2025
Evidence
Search visibility and audience growth, straight from the consoles.
59.7M clicks · 3.29B impressions · 1.8% average CTR · average position 9
Google Analytics · monthly
54M new users · 8M returning
Ooi Solutions
16 months, 23 interventions, +79% leads - and every number on this page can be checked in GA4, Search Console or PageSpeed Insights. That’s the point.
ooisolutions.in · hello@ooisolutions.in