WordPress Optimization

Frequently Asked Questions

How much speed gain can I expect?

Nobody can give you a figure out of the blue.

I might have a broad idea about the speed gain after checking the website, but it remains theoretical until all the optimizations are done safely.

My target loading speed is less than 1 second if the page can be served from the cache. Uncached content will be up to the server’s capacity to process and return a response as well as the distance from the origin.

You can be sure, however, that we will explore all possible options to enhance the site’s speed and performance.

How long does it take?

Up to 5 business for 10 pages.

Up to 10 business days for 25 pages.

Up to 15 business days for 50 pages.

Fast delivery is available with a target turnaround of 3 days for an additional 100€. You can pick up the fast delivery at checkout.

Are there any additional costs?

Depending on the current setup bottlenecks and limits, I will recommend using additional 3rd party services as required.

Getting them is optional and will be up to your performance budget and goals.

I update my website regularly. Will it affect the optimizations once done?

Changes will impact performance only if the pages’ structure, markup, CSS, or JavaScript files are altered.

You can opt for the WordPress Optimizer+ for an ongoing performance monitoring and improvement effort.

What will you need to get started?

The following information will be requested once the service is ordered:

• WordPress login/password
• Hosting service login/password

Will I get the perfect mark on Google PageSpeed Insight?

As much as I would love to hit the 100 scores for all sites, it can’t, unfortunately, be guaranteed.

The ultimate goal is to get the site at least to the green side of the score.

Hitting the perfect score is a possibility under certain conditions.

And here is why.

Google PageSpeed Insight idealizes how performance should be.

The site’s HTML structure, CSS, JavaScript code, and server performance should ideally align with their recommendations to give the best performance possible. And the only way to do that is by working on a performance strategy and picking the right components while building the site.

Planning for performance will bring you closer to the perfect score, as any component picked will be performance-friendly.

Performance “fixing” is another story :)

It has to deal with patching whatever performance flaws and bottlenecks exist on a site. And sometimes, the faulty component can’t be fixed or even improved.

The primary cause is how themes, plugins, and web services focus more on functionality than performance. That decision comes with terrible implementation and practices that will make it hard or impossible to fix.

Here are a couple of examples:

• Extensive use of complex layouts and CSS properties by themes and page builders, especially when used above the fold. That can’t be improved unless the page builder is changed.
• Long executing and demanding JavaScript, with a non-modular implementation, especially when they can’t be deferred or delayed. That can’t be improved unless the JavaScript code is refactored to consider performance or at least facilitate deferring or delaying the scripts.

In both examples, parsing, calculating the layout, or executing the script by the browser will be demanding, and unfortunately, it can’t be controlled once the process starts.

It will take the computation and time it needs. And the longer it takes, the more negative impact will hit performance and scores.

For that reason, I can’t guarantee the performance score. But I will get you the closest possible to it.