Keeping the Luxury, Losing the Lag: A WordPress PageSpeed Case Study
A slow website loses people before they read a single word, and Google keeps score too. Yet on a real client project, chasing a number is never the whole job — the design, the features and the feeling of the brand have to survive the process. This is the story of how a large WordPress website in four languages climbed to 90+ on Google PageSpeed for desktop while looking exactly the same as before.
The starting point
Since April 2026 I have been working on the website of Luxury Life Property Cyprus, a real estate company based in Famagusta, North Cyprus. It is far from a simple one-page brochure:
- Visitors can read it in English, German, Turkish and Persian, with the Persian version laid out right-to-left — all handled by WPML.
- A real estate theme and Elementor power property listings, maps, search filters and a blog.
- The brand is unmistakably premium: a video in the hero, refined typefaces, soft animations and big, high-resolution photography.
Beautiful for buyers, demanding for browsers. When the performance work began, the homepage was scoring about 51 on mobile and 81 on desktop.
The one rule we never broke
Stripping out the video, the animations and the custom fonts would have produced a fast, forgettable site. That was never on the table: the luxury look was the red line. Speed work here is a bit like mixing a song — you can clean up and balance every track, but you must not lose the melody. So every change had to be invisible to visitors. Each one was compared before and after, and anything that altered the design was undone.
Trust the median, not a single test
Run PageSpeed twice on the same page and the score can swing by 10 points or more. Reacting to one lucky — or unlucky — result leads to bad decisions. So every measurement was repeated several times and judged by its median. That small discipline tells you whether a change truly helped or the number simply drifted.
Caching that was quietly switched off
The website runs LiteSpeed Cache, but an audit revealed that page caching itself was disabled — every visitor was forcing the server to assemble the page from scratch. Enabling it and confirming it worked in all four languages was one of the largest single gains of the project. Lesson learned: check the foundations before reaching for anything clever.
A CDN, with an eye on the details
A CDN serves files from locations close to each visitor, which is great — until something subtle goes wrong. After switching it on, we noticed that a desktop visitor could occasionally receive the mobile version of a page, or the reverse. Adjusting how HTML pages are cached made sure every device always gets its proper layout. On top of that, a routine now warms the cache after large updates, so nobody lands on a cold, slow copy.
Fonts at home, a lighter logo
Fonts fetched from outside services mean extra connections before any text can appear. Hosting them on the site’s own server and preloading the key ones removed that delay. The logo got the same treatment: a much smaller file that is visually identical to the original.
Trimming JavaScript that had nothing to do
Themes and plugins love to load their scripts everywhere, whether a page needs them or not. Scripts with no job on a given page were stopped from loading there. Delaying all JavaScript was tested as well — it broke some interactive features, so it was rolled back. A reliable site matters more than a quick extra point.
Images that arrive gracefully
- WebP files, sized correctly for each screen
- A preloaded hero image, so the most important visual shows up first
- Lazy-loading for everything further down the page
- A gentle fade-in, so pictures appear smoothly rather than “line by line”
Where the numbers landed
| Start | Now | |
|---|---|---|
| Homepage, desktop | ~81 | 92–97 depending on language |
| Homepage, mobile | ~51 | up to 76 depending on language |
| Visible design changes | — | None |
Why is mobile lower? PageSpeed simulates a slow phone on a slow network, and a site with a hero video and rich animation will always feel that most. The client consciously chose to keep the luxury experience, and on real phones in real hands the website still loads quickly.
What you can take to your own site
- Start with the fundamentals — caching, CDN, image sizes — before anything advanced.
- Test repeatedly and compare medians instead of trusting one score.
- Make one change at a time, measure it, and keep a backup ready to roll back.
- Performance exists to serve the brand, never to replace it.
You can see this project in my portfolio: Luxury Life Property, a 4-language real estate website. Still choosing a platform? Here is why I still recommend WordPress for business websites.
Is your WordPress site dragging its feet, or is a low PageSpeed score keeping you up at night? Send me a message — I can look at your website and suggest careful improvements that leave your design untouched.