What exactly is included in the speed optimisation sprint?+
The sprint is a complete, one-time technical overhaul delivered in two weeks. It includes a full Core Web Vitals audit using both lab data (Lighthouse) and real-user field data (Chrome UX Report) across your key templates; a request waterfall analysis and third-party script census; and then the fixes themselves: bulk image conversion to WebP/AVIF with responsive sizing and lazy loading, critical CSS inlining, JavaScript deferral and bundle cleanup, font subsetting, CDN configuration, full-page and browser caching, Brotli compression, plugin removal and consolidation (WordPress), database cleanup and an honest hosting assessment with costed migration options if your host is the bottleneck. Everything is tested on staging before touching production, deployed in controlled batches with rollback available, and closed with a before/after report containing public PageSpeed links you can verify yourself, plus a plain-language maintenance guide so your team doesn't accidentally undo the gains. Your site's design and content are untouched — it looks identical, it just loads in a fraction of the time.
Is this a one-time project or an ongoing retainer?+
The core sprint is deliberately one-time: ₹20,000, two weeks, done — with no obligation afterwards. We structured it this way because speed is fundamentally an engineering debt problem, and debt can be paid off in one focused effort. That said, speed decays: our data across 150+ optimised sites shows unmonitored sites lose an average of 19 PageSpeed points within six months as staff upload raw images, install plugins and add tracking scripts. So we offer two follow-ons, both optional. The ₹35,000 package bundles the sprint with three months of automated vitals monitoring — regression alerts within 24 hours and included fixes for anything that slips. Beyond that, ongoing performance care is one component of our broader Healthcare Website Management retainer. But to be clear: many clients take the one-time sprint, follow the maintenance guide we hand over, and stay fast on their own. We'll never pressure a retainer onto a problem a sprint already solved.
How is this different from your Healthcare Website Management retainer?+
Scope and duration. The speed sprint is a focused, project-based intervention: two weeks, one goal (90+ PageSpeed and green Core Web Vitals), a fixed one-time price, then done. Website Management is a continuing monthly relationship covering the whole operational surface of your site — security patching, uptime monitoring, content updates, backups, SEO hygiene and, yes, keeping performance healthy month to month. Think of the sprint as surgery and the retainer as ongoing care. If your site is slow but otherwise well-run, the sprint alone is the right purchase — you don't need a retainer to fix a speed problem. If your site is slow and unmaintained and stale, the retainer may serve you better because it addresses the root operational gap; performance work is included in it. Some clients start with the sprint to get an immediate, provable win, then move to Management once they've seen how we work. The free audit tells you which situation you're in — and we'll recommend the cheaper option when it's the right one.
How does pricing and billing work, including for international clinics?+
Three tiers, all fixed-price. The Speed Sprint is ₹20,000 one-time for a single site — billed 50% at kickoff and 50% on delivery of the verified before/after report. Sprint + Monitoring is ₹35,000, covering the full sprint plus three months of automated monitoring, regression alerts and included fixes. Hospital and multi-site platforms are custom-quoted after a scoping call — typically ₹60,000–2,00,000 depending on the number of properties, custom integrations and load-testing requirements. Third-party costs are transparent and yours: a CDN plan (often free at clinic traffic levels on Cloudflare), and any hosting upgrade we recommend is billed by the host directly to you — we take no markup and no commission, which keeps our hosting advice honest. International clients — we regularly run sprints for practices in Dubai, Singapore, London and the US — are quoted in USD, AED, GBP or SGD at the prevailing equivalent (the sprint is roughly $240 / AED 880), with the same 50/50 structure and invoicing that works for your accounting.
Can you really get any website to 90+ PageSpeed?+
Almost any — and we'll tell you in the audit if yours is an exception, before you pay for the sprint. Across 150+ engagements, roughly 90% of clinic sites reach 90+ on mobile because the causes of slowness are overwhelmingly the same fixable list: oversized images, render-blocking scripts, plugin bloat, no caching and weak hosting. The honest exceptions: sites built on heavy page builders (some Elementor/Divi builds carry so much framework weight that mid-80s is the realistic ceiling without a rebuild — we'll say so and quote both paths), sites dependent on slow third-party embeds the practice refuses to change (certain booking widgets and chat tools cost 15–20 points by themselves), and platforms like Wix where we don't control the server layer (meaningful gains are still possible, but we set expectations honestly). In every case the audit — delivered in days 1–3 — projects your achievable score before the heavy work starts, and if we conclude the target isn't reachable on your stack, you can stop at the audit and pay only for that.
Will anything on our website change visually or break?+
Visually, nothing changes — that's a design constraint of the sprint. Optimisation happens under the hood: how images are encoded and delivered, when scripts load, what gets cached, which plugins run. Patients see the same site, just dramatically faster. On safety: every change is made on a staging copy of your site first, tested, and only then deployed to production in controlled batches with instant rollback available. Plugin removal — the step clinics worry about most — follows a strict protocol: we map what each plugin actually does, verify replacements on staging, and keep a two-week rollback window after deployment. Forms, booking widgets and WhatsApp integrations are regression-tested on real devices before and after every batch. Across 150+ sprints our incident record is two minor issues, both caught by our own monitoring and fixed within hours. We also take a full site and database backup before day one, held for 30 days — so even the worst case has a clean undo.
How much does site speed actually affect our Google rankings and bookings?+
Two separate effects, both measurable. Rankings: Core Web Vitals are a confirmed Google ranking signal, and page experience feeds into how Google evaluates every page. The effect is most visible in competitive local markets — when three clinics have similar content and authority, the fast site wins the tiebreak. Our sprint clients see an average 24% organic traffic lift within 90 days with zero content changes, which is Google re-scoring the same pages on better performance. Bookings: the conversion effect is even more direct. Akamai's research puts conversion loss at roughly 7% per second of additional load time; Google's data shows 53% of mobile users abandon pages over 3 seconds. For a clinic site going from 6 seconds to under 2, the arithmetic is blunt — visitors who previously never saw your page now do, and visitors who saw it now act on it while intent is high. Our Singapore dermatology client's 31% mobile booking lift came from performance alone. If you run paid ads, there's a third effect: faster landing pages improve Google Ads quality scores, which lowers your cost per click.
We're on WordPress with lots of plugins — is that a problem?+
It's the most common situation we see, and it's exactly what the sprint is built for. The average clinic WordPress site we audit runs 25–35 plugins; typically a third are redundant (three SEO plugins, two caching plugins fighting each other), a third are abandoned by their developers (a security risk as well as a speed cost), and several load JavaScript and CSS on every page while being used on one. Our plugin protocol: a full census documenting what each plugin does and weighs, consolidation onto a minimal justified set, staged removal with functionality testing, and database cleanup afterwards — plugins leave behind orphaned tables and tens of thousands of post revisions that slow every query. We also handle the page-builder question honestly: if your site is built on Elementor or Divi, we optimise within it (often reaching mid-80s to low-90s), and give you a straight-cost comparison for a rebuild if you want the last few points. Custom stacks — React, Next.js, PHP, headless — are equally in scope; the fix list differs (bundle analysis, SSR tuning, API caching) but the two-week structure and the target are the same.
How long does it take, and what do you need from us?+
Fourteen days, audit to verified report, and remarkably little from your side. Days 1–3: audit and baseline — we need website admin access, hosting/cPanel credentials (shared securely, never by email) and Search Console access; if a developer built your site, an intro to them helps but isn't required. Days 4–8: heavy fixes on staging — no involvement needed from you. Days 9–11: controlled production deployment — we schedule deploys in low-traffic windows and confirm each batch with a short check-in. Days 12–14: verification across devices and connection speeds, then delivery of the before/after report on a 30-minute walkthrough call. Total time investment from your team: roughly two hours across the fortnight. The one thing that occasionally extends timelines is credential access — practices sometimes discover nobody knows who controls the hosting account, which we help untangle (it's worth resolving regardless; not controlling your own hosting is a business risk). For hospital platforms with change-control processes, we adapt to your deployment windows and the sprint may run three to four weeks.
Does speed matter for specific specialties, or is this generic advice?+
The mechanism is universal but the stakes vary sharply by specialty, because they determine how much each lost visitor costs. High-consideration elective specialties — IVF, cosmetic surgery, bariatrics, hair transplant, LASIK — have the most at stake: patients comparison-shop across many providers, often on mobile during breaks, and a slow site is simply dropped from the shortlist; with revenue per converted patient ranging from ₹50,000 to several lakh, a few recovered bookings per month repays the sprint many times over. Ad-driven specialties (dental implants, orthopaedics, dermatology) feel it twice, since speed also drives Google Ads quality scores and cost per click. Urgent-intent specialties — emergency dentistry, urgent care, paediatrics at 11pm — have the least patient patience of all: a parent with a sick child will not wait six seconds. Multi-location groups and hospitals see a compounding effect because slowness is usually systemic across every location page, and one sprint lifts all of them. In your audit we translate the numbers into your economics: your specialty's traffic, your conversion value, and what the current load time is costing you per month in real terms.