Real cases
Before and after: sites we have optimised
First, two sites with everything against them: a very heavy theme and page builder (Jupiter + WPBakery) and shared hosting that could not be changed. The data comes from PageSpeed Insights, and you can check it yourself right now. Then, sites on their own server where the bottleneck was the VPS.
On the server: IONOS VPS with Plesk
A new VPS ships with factory settings meant for small sites. With WooCommerce, WPML or Elementor, the PHP cache fills up, Plesk adds restrictions that slow down every disk access, and the object cache sometimes empties itself. They belong to clients of Orbitalia, the SEO agency we work with on the technical side. This is how they ended up after tuning their servers.
Corporate gifts catalogue: WooCommerce, WPML (ES/CA), Elementor and over 2,000 products, on an IONOS VPS with Plesk.
Server, cache, search, database and menu, all at once: PHP cache and Redis, gzip and Brotli compression, a mega menu that loads each panel only when it opens, and a search that uses its index. With the cache, the home page leaves the server in 0.03 s.
Server response without cache
−43 %
Main content on mobile (LCP, PageSpeed)
−29 %
PDF catalogue, cover on mobile
−56 %
Property portal with WPResidence, Elementor Pro and WP Rocket, on an IONOS VPS shared with other sites.
It started because the Google Ads agency complained that its landing page was slow. First the website: our own critical CSS, stylesheets the theme loaded without using removed, the listing gallery rewritten, and fonts and header images at the right size. Then the server: a PHP cache with enough memory and without the Plesk path restriction.
Main content on mobile, real users (LCP)
−61 %
Server response without cache
−67 %
Google Ads landing page, main content (LCP)
−46 %
Property listings, main content (LCP)
−84 %
Response to interaction, real users (INP)
−35 %
WooCommerce shop with WP Rocket, on an IONOS VPS shared with Barcino Designs.
A botnet requested URLs without the trailing slash, which bypassed the cache: the server was overloaded and even cached pages were slow. One nginx rule that redirects those URLs brought the load down within two minutes.
Main content on mobile, real users (LCP)
−75 %
Barcino Designs during the attack
−99 %
WooCommerce and WPML on an IONOS VPS with Plesk.
The PHP cache (OPcache) had factory settings and was full. With enough memory, the code is no longer compiled on every visit.
Server response without cache
−69 %
WooCommerce shop on an IONOS VPS with Plesk.
The same OPcache and PHP path settings, on the VPS it shares with Olé Mosaic.
Server response without cache
−68 %
WooCommerce with subscriptions and Elementor, on an IONOS VPS with Plesk.
PHP and PHP cache tuning on the server. It also speeds up the cart and forms, which go through admin-ajax.
Server response without cache
−36 %
Main content on mobile, real users (LCP)
−41 %
Multilingual WordPress with WPML and Redis, on an IONOS VPS with Plesk.
A WPML bug emptied the object cache on every visit: it was on but did nothing. Once fixed, it answers 97% of lookups.
Server response without cache
−31 %
Clinic website with Elementor and Redis, on an IONOS VPS with Plesk.
We built it optimised from day one: a PageSpeed mobile score of 99. Even so, hundreds of Elementor backups stored in the database made every page load 60 MB of data. Cleaning them up made pages build faster.
Server response without cache
−20 %
Server times measured on a page outside the cache (the worst case: what a visitor or Google gets when the cache is empty), before and after each change, September–October 2026. PageSpeed: average of the weekly mobile measurements before and after. Real users: Chrome field data (75th percentile, 28 days), with no simulation involved. Speed also depends on things beyond our control, so PageSpeed moves a few points from week to week.