Work / Healthcare · Egypt · 2026
Clinic website: page caching cut server response time from 0.6 s to 0.1 s
I built a clinic website in WordPress and then tuned the server. With server-level page caching, the server’s response time (TTFB) dropped from 0.6 s to 0.1 s.
- Role
- Solo: build, content and server tuning
- Date
- 2026
- Stack
- Tools: Elementor, Premium WordPress theme, LiteSpeed Cache (server-level page cache)
- Result
- Server response time (TTFB) 0.6 s → 0.1 s with page caching
- Status
- Live · umeniclinic.com
More pages from this project
Context and problem
A clinic needed a new website its team can update.
My role
Solo: building the site with Elementor and a premium theme, content and server configuration.
What I did
- Built the site in WordPress with Elementor.
- Configured and verified server-level page caching with LiteSpeed Cache.
About the number
TTFB is how fast the server starts to answer. It is not one of Google’s Core Web Vitals. The pages are still heavy on mobile, so front-end work (images, JavaScript, LCP) is the next step.
Results
| Metric | Before (no page cache) | After (page cache) |
|---|---|---|
| Time to first byte (TTFB), home page | 0.6 s | 0.1 s |