As much as I would love to hit the 100 score for all sites, it can’t unfortunately be guaranteed.
To get the site at least to the green side of the score is the ultimate goal.
Hitting the perfect score is a possibility under certain conditions.
And here is why.
Google PageSpeed Insight idealizes how performance should be.
Planning for performance will bring you closer to the perfect score, as any component picked will be performance-driven.
Performance “fixing” is another story :)
It has to deal with patching whatever performance flaw and bottlenecks exist on a site. And sometimes, the faulty component can’t be fixable.
The primary cause is how themes, plugins, and web services focus more on functionality rather than performance. That decision comes with extremely bad implementation and practices that will make it hard, or even impossible, to fix.
Here are a couple of example:
– The extensive use of complex layouts and CSS properties by themes and page builders, especially when it’s used above the fold.
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 it fires.
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.