NEWIntroducing Client Dashboard — sign up, order services and manage everything in one place. Get started free→
Nishka Skin & Hair Clinic logoNishka Skin & Hair Clinicnishkaskinclinic.com ↗
Case Study · Healthcare — dermatology & skin clinic

Nishka Skin & Hair Clinic: From WordPress & WP Amelia to a Fast Custom Dermatology Website — Bangalore Case Study

How we moved a leading Bangalore dermatology clinic off WordPress and the WP Amelia booking plugin onto a fast, custom Next.js website — with one-tap WhatsApp and call booking that lifted enquiries by 10%.

By Dharmendra Asimi·Published October 20, 2026
Nishka Skin & Hair Clinic website redesign by Aapta Solutions — a fast, custom Next.js site for a BTM Bangalore dermatology clinic led by Dr. Shilpa R K, with one-tap WhatsApp and call booking

Outcomes

+10%
Enquiries
after migration (client-reported)
Custom Next.js
Platform
from WordPress
One-tap WhatsApp + call
Booking
replaced WP Amelia
Faster loads
Performance
prerendered, no plugins
Physician + LocalBusiness
Structured data
built in
66 treatments + blog
Content
structured

Engagement: Website rebuild & migration — WordPress + WP Amelia → custom Next.js Industry: Healthcare — dermatology & skin clinic Stack: Custom Next.js on Netlify · one-tap WhatsApp & call booking · Physician/LocalBusiness schema Result: Faster load times and a client-reported 10% increase in enquiries

At a glance

Nishka Skin & Hair Clinic is a dermatology clinic in BTM 2nd Stage, Bangalore, led by consultant dermatologist Dr. Shilpa R K. Its old website ran on WordPress, with the WP Amelia plugin handling appointment booking and a stack of other plugins doing the rest. It worked — but it was heavy, slow, and the booking flow put friction exactly where a first-time patient hesitates.

We rebuilt it as a fast, custom Next.js website, replaced the Amelia booking calendar with one-tap WhatsApp and click-to-call, and gave the clinic proper medical structured data. The clinic reports a 10% increase in enquiries since the switch.

Client Nishka Skin & Hair Clinic, BTM 2nd Stage, Bangalore
Led by Dr. Shilpa R K (MBBS, DDVL), consultant dermatologist
Previous platform WordPress + WP Amelia booking plugin
New platform Custom Next.js on Netlify
Reported outcome +10% enquiries after migration

The client

Nishka Skin & Hair Clinic is led by Dr. Shilpa R K — an MBBS, DDVL consultant dermatologist with 14+ years in practice and specialist skin and laser surgery training in Thailand. The clinic's promise is set out in its own words: skin and hair care, diagnosed before it's treated — acne, pigmentation, hair fall, lasers and aesthetic care, each planned after a proper examination and followed up until it works.

That ethos shapes everything about the brand. There are 66 treatments on offer — from acne and acne-scar care, pigmentation, melasma and dark circles to PRP hair treatment, laser hair reduction, chemical peels, HydraFacial, and dermatology for conditions like psoriasis and fungal infections — but the positioning is deliberately un-salesy: no packages pushed, a plan that fits you. Patients, many of whom have been coming for years, consistently describe the same thing in reviews — time taken to explain, honest advice, and treatment that actually works.

For a clinic like this, the website carries real weight: it's usually the first encounter a nervous, searching patient has with the practice, and it has to do two jobs at once — build trust, and make it effortless to take the next step.

Nishka Skin & Hair Clinic — logo

The starting point: WordPress, a booking plugin, and friction

The previous site was built the way most clinic sites are: WordPress, with the WP Amelia plugin bolted on for appointment booking and several more plugins layered on for everything else. It functioned — but it carried the familiar costs of that approach:

  • Plugin weight and slow pages. WordPress plus a booking plugin plus a handful of supporting plugins means a lot of code, styles and scripts loading on every visit. On the phones most patients use, that shows up as a slower, heavier site.
  • A booking flow with too many steps. Amelia is a capable calendar plugin, but its multi-step flow — pick a service, pick a staff member, pick a slot, fill a form — asks a lot of a first-time visitor who simply wants to talk to the dermatologist first. Every extra step is a place to drop off.
  • A maintenance and security burden. A WordPress install with multiple plugins needs constant updating, and each plugin is another moving part that can break or be exploited — an avoidable risk for a small clinic.
  • Limited control over trust and SEO. Getting a WordPress-plus-plugins site genuinely fast and cleanly structured for local medical search is a constant fight against the platform's defaults.

The clinic didn't need a prettier theme. It needed a lighter, faster site and a booking experience that matched how patients actually behave.

Our approach: custom, fast, and friction-free to book

We rebuilt the site as a custom Next.js application — no WordPress, no page builder, no plugin stack — and made one decision central to the whole project: remove friction from booking.

  • Custom and lightweight. A purpose-built Next.js front end, server-prerendered and served from a CDN, so there's very little for a phone to download or run.
  • Booking reimagined around how patients behave. Instead of a multi-step calendar plugin, the new site makes the next step a single tap — WhatsApp or click-to-call — backed by clear Book a consultation calls to action. For a clinic where the first step is a conversation, not a transaction, that's the natural path.
  • Trust, designed in. Dr. Shilpa's credentials, real patient reviews, the clinic's ethical "no packages pushed" positioning, and clear location and hours are placed where a hesitant patient needs them.

The build

Tech stack

  • Next.js on Netlify — a custom, component-based front end with no WordPress and no plugin runtime, prerendered and served from the edge for fast, consistent load times.
  • One-tap WhatsApp + click-to-call booking — the WP Amelia calendar replaced with the lowest-friction path to an enquiry: a tap to chat on WhatsApp or to call the clinic directly, plus prominent Book a consultation CTAs throughout.
  • Physician + LocalBusiness schema.org — the site describes itself to Google and AI engines as a real dermatology clinic: a named Physician, the practice's address, opening hours and location, so it reads as a genuine local medical business.
  • A symptom-led experience — a "What brings you in today?" entry point guides patients to the right treatment by concern, rather than making them hunt through a menu.
  • Structured treatments library + blog — all 66 treatments organised cleanly, plus a blog that answers the skin and hair questions patients search for.

What a visitor can now do

  • Start from their concern — acne, pigmentation, hair fall, lasers — and land on the right treatment.
  • See who they'll be treated by — Dr. Shilpa's qualifications, experience and training, up front.
  • Trust before they commit — real reviews from long-term patients, and a clear, no-upsell promise.
  • Book in one tap — WhatsApp or call, from any page, without a multi-step form.

Booking, reimagined: from a plugin calendar to one tap

This is the change that moved the number. The old Amelia flow treated booking like a transaction — several screens of service, staff and slot selection before a patient could get in touch. But a first visit to a dermatologist usually starts with a question, not a confirmed slot.

The new site matches that reality. The primary action everywhere is to start a conversation — one tap to WhatsApp, or one tap to call — with Book a consultation as the clear next step for those ready to commit. Fewer steps between "I'm worried about this" and "I've reached the clinic" means fewer people give up along the way. Combined with faster pages and clearer trust signals, that's what the clinic credits for its 10% rise in enquiries after the migration.

Faster on every device

A clinic's patients are almost always on a phone, often searching with a specific worry in a spare moment. The old plugin-heavy WordPress site made them wait; the custom build doesn't.

Because the front end is a lean Next.js application — prerendered and served from Netlify's CDN, with no theme to parse and no plugin runtime to execute — pages arrive quickly on an ordinary mobile connection, and the tap-to-book actions respond instantly. For a hesitant patient, that speed and ease is the difference between an enquiry and a closed tab. (The same Core Web Vitals discipline sits behind every build we ship — see our note on website speed optimisation.)

SEO, GEO and AEO: built to be found locally

For a single-location clinic, being found is overwhelmingly a local problem — and increasingly an AI one, as patients ask assistants for recommendations. We built Nishka to compete on both, the same way we approach every project in our Generative Engine Optimization (GEO) 2026 guide:

  • Medical + local structured data. The site ships Physician and LocalBusiness-style schema with the clinic's name, address, opening hours and location — exactly what Google and AI engines look for to treat it as a real, rankable local practice.
  • Local-intent content. Titles and pages built around how patients actually search — "dermatologist in BTM, Bangalore", "laser hair reduction Bangalore", "acne scar treatment near me".
  • A treatments library and blog that answer specific patient questions in direct, quotable language — the kind of content AI answer engines lift and cite, and that ranks for the long tail of skin and hair searches.
  • A fast, mobile-first, prerendered build — the technical baseline Google now rewards.

You can measure any site's AI-readiness the same way we do, with our free GEO readiness scanner.

Outcome — before and after

Before (WordPress + WP Amelia) After (custom Next.js)
Platform WordPress + plugin stack Custom Next.js on Netlify
Booking Multi-step Amelia calendar One-tap WhatsApp + click-to-call
Page weight Plugin-heavy Lean, prerendered, CDN-served
Structured data Plugin-dependent Physician + LocalBusiness schema
Content Theme-bound 66 treatments, structured + blog
Enquiries Baseline +10% (client-reported)

The clinic moved from a slow, plugin-laden site with a multi-step booking flow to a fast, custom site where booking is a single tap — and the enquiries followed.

The takeaway

For a local clinic, the website has one real job: turn a worried search into a booked consultation. WordPress with a booking plugin can stand that up, but it tends to arrive slow and friction-heavy — and friction is the enemy of a first-time patient. A lightweight custom build, organised around the lowest-friction way to make contact, does the job better: it loads fast, it earns trust, and it gets out of the way at the moment of decision.

That's what the Nishka rebuild delivered — and the same thinking runs through our work for Arun Sharma Guruji, Epic Gymnastics Academy, The Platos School and The Global Economics.

If your clinic gets visits but not enough enquiries, let's talk about a rebuild, or get a tailored quote.

Frequently asked questions

What platform is the new Nishka Skin Clinic website built on?

It's a custom Next.js website hosted on Netlify — server-prerendered and served from a CDN, with no WordPress and no plugin stack. Booking runs on one-tap WhatsApp and click-to-call rather than a booking plugin. This replaced a WordPress site that used the WP Amelia plugin for appointments.

Why move the clinic off WordPress and WP Amelia?

WordPress plus a booking plugin plus supporting plugins makes a site heavy and slow, and the WP Amelia calendar adds several steps before a first-time patient can simply get in touch. Those two things — slow pages and a high-friction booking flow — both cost enquiries. A lightweight custom build fixes the speed, and a one-tap booking path fixes the friction.

How does booking work on the new site?

The site's primary action is to start a conversation: one tap to message the clinic on WhatsApp, or one tap to call, with clear Book a consultation calls to action on every page. For a dermatology clinic, where a first visit usually begins with a question rather than a fixed slot, this matches how patients actually behave — and removing steps is what reduces drop-off.

Did the migration actually increase enquiries?

Yes — the clinic reports a 10% increase in enquiries since moving to the custom site. The gain comes from the combination of faster pages, clearer trust signals (credentials and real reviews), and a booking path that's a single tap instead of a multi-step form.

Is the new website faster?

Yes. The front end is a lean Next.js application with no theme or plugin runtime, prerendered and served from Netlify's CDN — so pages load quickly on an ordinary phone connection, which is where most patients search and book.

That's what the structured-data and content work is for. The site ships Physician and local-business schema with the clinic's name, address and hours, local-intent pages (e.g. "dermatologist in BTM, Bangalore"), a treatments library and a blog — the signals Google and AI engines use to surface and cite a real local clinic.

Can you rebuild my clinic's WordPress site like this?

Yes — moving a clinic off WordPress and a booking plugin onto a fast custom site with low-friction booking is exactly this kind of project. Get a tailored quote or read about an ongoing technology partnership.

Project credits

Built by Aapta Solutions · Founder: Dharmendra Asimi · Bengaluru & Hyderabad, India

Visit the live site: nishkaskinclinic.com

Want a similar build for your clinic? Talk to us or run a free GEO readiness scan on your current site to see where you stand today.

Have a project that needs this kind of build?

Static, fast, AI-search-ready websites for businesses across India, the USA and the UK. The quote builder takes 5 minutes; we send a tailored proposal within 2-3 business days.