case study · dental clinic website

A clinic that invests in technology got a website that takes 2.5 s to respond that keeps up with it

A new website for a private dental clinic in Sosnowiec, Poland: a custom design in the brand colours, two languages, a simple CMS without block-based page building, and online booking secured with a PLN 50 deposit via PayU.

Client
Stomatologia Tejman, Sosnowiec
Scope
Audit, design, frontend, CMS, booking, migration
Stack
Astro 5 · Payload CMS 3 · Postgres
Languages
Polish, English
The new Stomatologia Tejman website on desktop and phone: headline, photo of the dentists and a card with a tooth point cloud
Home page on desktop and phone. The “3D scan” card is an animated tooth point cloud drawn on canvas.

01 / starting point

A modern clinic with a 2020 website

The old site was WordPress with a dental theme and a page builder. The clinic owns a treatment microscope, a CBCT scanner and an intraoral scanner, yet none of it showed, and the first screen was a carousel of stock photos.

  1. 01Slow

    Around 2.5 s to first byte and over 100 requests on the home page, including 37 scripts and 14 font files, mostly icon fonts.

  2. 02Hard to read

    The main text colour had about 2.9:1 contrast. Not enough for older patients, a key audience for implants and All-on-X.

  3. 03Off-brand

    The identity is orange and the grey concrete wall with the logo at reception. The theme added navy, turquoise and blue.

  4. 04Hidden strengths

    Single-visit microscope root canal treatment, on-site CBCT and new teeth in one day were three clicks away from the home page.

  5. 05Bookings that never showed up

    The clinic had switched off its previous booking plugin because patients booked and did not come. A deposit was needed.

  6. 06Content to keep

    111 blog posts with local keywords, 47 pages and a full price list. Texts had to stay and old URLs had to redirect without losing SEO.

02 / numbers

Same content, six times fewer requests

Home page measured in Chromium (Playwright): the old tejman.pl and the new staging version, desktop and phone.

105 → 15
requests on the home page (desktop)
2.4 → 0.6MB
transferred on first visit
37 → 4
JS files the whole site is one bundle including animations
0.78 → 0.02
CLS on mobile (layout shift while loading)
111
blog posts migrated automatically with images and SEO metadata
37
301 redirects from old URLs, plus a rule for dated post URLs
123
price list items with search, edited in the CMS
2
languages shared routing and field-level translations in the admin
tejman.pl (WordPress)new websitefull width = old site result
HTTP requests105
15
Transfer2.4 MB
0.6 MB
Time to first byte~2.5 s
~0.03 s
LCP · mobile2.46 s
0.48 s

Measured from the server that hosts the new version, so its network timings are favourable. Request count, transfer size and CLS do not depend on that.

03 / design

Orange and concrete instead of a dental template

The colours stayed, because they are the identity of the whole clinic. Calm, light reading sections alternate with dark “lab” sections about the equipment. No rows of identical icon cards and no stock photos: only the team, the clinic and real treatment results.

04 / motion

Animation that says something

Transitions

No full page reloads

Astro View Transitions: content leaves upwards with a slight blur and the next page slides in from below. The header, menu and mobile action bar stay in place.

3D scan

A point cloud instead of an icon

A molar made of 2,600 points, drawn on canvas, rotates with the cursor while an orange scanning plane sweeps up and down. It pauses when off-screen.

Accessibility

Motion can be turned off

With prefers-reduced-motion everything is visible immediately, galleries scroll manually and the review carousel has buttons and a pause.

Performance

Animation never shifts layout

GSAP and Lenis animate only transform and opacity. Images carry dimensions and WebP variants, so mobile CLS dropped from 0.78 to 0.02.

05 / CMS

An admin for content, not for building pages

Payload CMS with a Polish interface. The home page is a designed layout with a tab per section: reception edits texts, photos and steps, but cannot break the design, because there are no WordPress-style blocks.

admin / home page / first visit
CMS admin: home page with section tabs and editing of the first visit steps
Home page in the admin. One tab per section. The Polski / English switch in the top right toggles every translated field.
Editing the root canal treatment page: title, lead, image, rich text editor, category and SEO fields
Treatment. Drafts and version history, rich text, prices, FAQ, treatment steps, a comparison table and SEO fields. Every field has a PL and EN version.
Dentist record in the admin: online booking toggle and weekly working hours
Dentist schedule. Free slots are computed from these hours, visit types, time off and existing bookings.

Changes show up immediately

The frontend caches API responses in memory. Every save in the admin calls an internal endpoint that clears the cache, so the site is fast and always current.

SEO in the editors' hands

Google title and description on every document, 301 redirects as a plain list in the admin, a sitemap with hreflang, and Dentist, FAQPage and BlogPosting structured data generated automatically.

06 / booking

The slot is yours once you pay PLN 50

A four-step wizard and a deposit via PayU, which the clinic already uses for instalments. The deposit is deducted from the visit price and refunded if you cancel at least 24 hours ahead.

Booking flow with deposit The patient picks a visit, dentist, time and enters details. The slot is held for 20 minutes and the patient is sent to PayU. After payment the booking is confirmed; without payment it expires and the slot is released. 1–4 · wizard visit, dentist, time, details Slot hold 20 min to pay 5 · PayU BLIK, transfer, card Confirmed notification + status page Expired slot back in the pool Cancel > 24 h deposit refunded via API COMPLETED no payment

Slots computed on the server

Free times come from schedules, visit length, time off and existing bookings. Before saving, the system checks the slot again, so two people clicking the same time cannot both get it.

PayU with signature checks

PayU notifications are verified by signature. If the patient returns before the notification arrives, the status page asks PayU for the order state itself. Sandbox and simulation modes switch in the admin.

Pain always means a phone call

The wizard says it on the first screen: “In pain? Don't book online, call us.” Urgent cases never wait for a free slot.

07 / architecture

Three containers behind one Caddy

Site architecture Caddy routes the admin and API to Payload CMS and everything else to Astro. Astro reads content from the CMS, the CMS stores data in Postgres and talks to PayU. After each save the CMS clears the Astro cache. Caddy · HTTPS Astro 5 SSR PL / EN website API response cache Payload CMS 3 /admin, /api booking, PayU Postgres 17 internal network only PayU orders, refunds REST purge

One route for two languages

Instead of duplicating page files per language, a single dynamic route maps the URL to a page type and language (e.g. /uslugi/implanty and /en/services/implanty). The language switch always leads to the equivalent of the current page.

Hardened containers

Read-only containers with no system capabilities and no public ports. The database lives on the internal network only, and a daily dump goes into the server backup.

Images optimised on upload

A photo uploaded in the admin becomes WebP in three sizes with a focal point. The frontend picks the size via srcset.

08 / delivery

From audit to a working staging version

  1. Audit and content inventory

    Measurements of the old site, contrast and structure review. All posts, pages and media pulled through the WordPress REST API, together with SEO titles and descriptions.

  2. Cleaning and import

    Page-builder HTML turned into clean structure: lists rebuilt from widgets, headings without bold, typos fixed (including one in the street name). Then converted for the CMS editor, with images attached as media.

  3. English version

    Treatments, equipment, team, prices and the home page translated and stored as a second language of the same documents. The blog stays Polish, and the English site says so openly.

  4. Screenshot-driven QA

    Every view checked in Playwright on desktop and phone. Screenshots caught a clipped italic in the headline, a price column pushing into the text and a race in the wizard where a step animation overwrote the loaded calendar. All fixed before hand-off.

  5. Payments in sandbox

    A test booking creates an order in the PayU sandbox and holds the slot. Going live only needs the clinic's PayU shop credentials.

technologies

  • Astro 5 SSR
  • View Transitions
  • GSAP · ScrollTrigger
  • Lenis
  • Canvas 2D
  • Payload CMS 3
  • Next.js
  • Lexical
  • PostgreSQL 17
  • PayU REST API
  • Docker Compose
  • Caddy
  • Playwright
  • Schema.org

Screenshots come from the working staging version before launch. Dentist schedules in the booking system are sample data and payments run in the PayU sandbox. Results were measured in Chromium on the home page. The new version runs on the same server it was measured from, so its network timings (TTFB, LCP) are more favourable than for an outside visitor.

next step

Facing a similar challenge?

Tell me what you want to achieve. I'll come back with a concrete proposal, a quote and a delivery plan.