How I Took a Multilingual WordPress Site to 90+ on Google PageSpeed

Speed is one of the first things visitors notice — and one of the things Google measures. But on a real business website, speed work is never only about a score. You also have to protect the design, the features and the brand experience the client loves. In this article I share how I improved the speed of a large, four-language WordPress website and reached 90+ on Google PageSpeed for desktop, without changing the look of the site.

The project: a luxury real estate website in four languages

Since April 2026 I have been building and maintaining the website of Luxury Life Property Cyprus, a real estate company in Famagusta, North Cyprus. The website is not a simple brochure site:

• It runs in four languages — English, German, Turkish and Persian — with full right-to-left support for Persian, managed with WPML.
• It is built with a real estate theme and Elementor, with property listings, maps, search filters and a blog.
• It has a strong luxury identity: a hero video, elegant fonts, smooth animations and large, high-quality photos.

All of this is great for the brand — and heavy for performance. When I started the speed work, the homepage scored around 51 on mobile and 81 on desktop.

Rule number one: the design is a red line

The easiest way to get a perfect score is to remove videos, animations and fonts. That was not an option. The client’s luxury look comes first, so every change had to be invisible to visitors. Each step below was tested and compared before and after, and anything that changed the design was rolled back.

Step 1: Measure properly

PageSpeed results can jump by 10 points or more between two runs of the same page. Instead of trusting a single test, I ran each test several times and used the median score. This simple habit prevents a lot of wrong decisions — you know whether a change really helped or the score just moved by chance.

Step 2: Make sure caching really works

The site uses LiteSpeed Cache. During an audit I found that page caching was actually switched off, so every visit was building the page from scratch. Turning it on and verifying it for every language gave one of the biggest improvements of the whole project — a good reminder to always check the basics first.

Step 3: A CDN — configured carefully

A CDN delivers files from servers close to each visitor. After enabling it, I noticed a subtle problem: the CDN could serve the mobile version of a page to desktop visitors and the other way round. I fixed how HTML pages are cached so each device always receives the right layout, and I set up a routine to warm the cache after big updates so visitors never hit a slow, empty cache.

Step 4: Self-hosted fonts and a lighter logo

Loading fonts from external services adds extra connections before text can appear. I moved the fonts onto the website’s own server and preloaded the important ones, and I replaced a heavy logo file with a much lighter version that looks exactly the same.

Step 5: A “JavaScript diet”

Themes and plugins often load scripts on every page, even where they are not used. I identified scripts that were not needed on specific pages and stopped loading them there. I also tested delaying all JavaScript — but it broke some interactive features, so I reverted it. Honest testing matters more than a quick win.

Step 6: Smarter images

• Modern WebP images in the right sizes for each screen
• The main hero image preloaded, so the most important picture appears first
• Lazy-loading for images further down the page
• A soft fade-in effect, so images appear elegantly instead of “line by line”

The results

Mobile scores are naturally lower on a site with a hero video and rich animations, because PageSpeed tests on a simulated slow phone. The client made a clear choice to keep the luxury experience — and the site is still fast for real visitors on real devices.

Lessons you can use on your own website

• Check the basics first — caching, CDN and image sizes — before touching anything complex.
• Always measure several times and compare medians, not single scores.
• Change one thing at a time, test it, and keep a backup so you can roll back.
• Speed should serve the business, not destroy the brand.

You can see the full project in my portfolio: Luxury Life Property, a 4-language real estate website. Still choosing a platform for your own site? Here is why WordPress is still the best choice for business websites.

Is your WordPress website slow, or are you worried about your Google PageSpeed score? Get in touch — I can review your site and suggest safe improvements that keep your design exactly as it is.