< WordPress Optimization />

Optimizing your WordPress or WooCommerce site allows you to solve concrete problems with your site, those that impact your loading times, and therefore user experience and SEO visibility. It is the simplest way to quickly and lastingly correct the weaknesses of your theme and plugins.

No, quite the opposite! A majority of slow WordPress sites use Page Builders, and we have developed optimization tools that specifically target them. The results are particularly excellent with Elementor and Divi, which are very popular. But we also optimize sites built with WPBakery, Visual Composer, tagDiv Composer, Brizy, and Oxygen Builder.

Our extensive experience with the WordPress CMS allows us to implement performance fixes quickly and transparently. This is why we strongly recommend optimization by us rather than an audit followed by implementation by your own development teams. Since the cost of the 2 packages is the same, the return on investment is faster this way.

Yes! Optimizing the web performance of a WordPress site helps to decarbonize it, that is to say, to reduce its carbon footprint. Our services therefore perfectly meet the requirements of a website decarbonization project. We also systematically include an "ecological impact" component in our deliverables.

WordPress optimization costs between €1,500 and €3,500 before tax, depending on the number of templates, the plugins in place, and whether or not a page builder is used. This is a fixed-price package, including three to four days of analysis and fix deployment. We will provide you with a quote upon request.

Proceed in order of gains: activate page caching, check that the hosting is not shared, update PHP with a properly sized OPcache, then optimize images and plugins. The first two levers change the order of magnitude, the following ones refine.

Page caching is the most cost-effective action: it saves the final HTML and serves it again without re-executing WordPress or querying the database. A page that used to take hundreds of milliseconds now takes a few. However, it only covers anonymous visitors: for administration and logged-in users, object caching takes over.

Next comes what cannot be fixed with a plugin: lighten the markup produced by the page builder, prioritize the first screen image, defer third-party scripts, and purge unnecessary background tasks. These actions require technical intervention, but they are the ones that last over time.

It's not the number of plugins that matters, but what they do. Four families weigh heavily: page builders, security plugins that analyze the file structure, those that log every 404 error or redirect, and link checkers that continuously recrawl the site. All of them work in the background, out of your sight.

The mechanism is always the same: a database write or a disk read on the critical path of the request. A site that logs its 404s executes an insert into the database for each visit to a non-existent page, including bots. The volume increases without real traffic increasing, and the concerned table eventually slows down all requests.

The good news is that these behaviors are almost always default settings, adjustable in the interface of each extension: reduce log retention, space out scans, enable low-resource mode. Uninstalling is not always necessary; it is the original setting that is at fault, rarely the tool itself.