Mantys CoreGuides & knowledge base
Practical WordPress performance, explained without the jargon.
How to speed up a Divi site and improve its Core Web Vitals (step by step)
A Divi site can be fast if you optimize in the right order, images first, then CSS, then JavaScript, and start with the levers that cannot break anything before touching the ones that can.
Why does my burger menu only open on the second click?
If you turned on a JavaScript delay (loading scripts on the first click or after a timer), the very first tap on the burger wakes up the script loading, it does not open the menu. The menu only responds to the second tap. The fix: isolate the menu script and its dependencies out of the delay, or better, give it a vanilla menu with no dependency.
Which optimizations can you turn on without any risk of breaking your site?
There is a whole family of optimizations that cannot break your site, because they reduce file weight or give the browser hints, without ever changing what runs. Start with those: they win you the essentials, with your eyes closed.
Why did my critical CSS break my menu / overlay (it shows up open on load)?
Critical-CSS generators only keep the styles for what is visible at the top of the page on load. Your elements that are hidden by default and opened on click (mobile menu, search overlay, modal, drawer) are judged useless and removed. The result: on load, they show up open, broken, unstyled.
Why does PageSpeed Insights still say “Properly size images” when I have a srcset?
Srcset offers the browser a list of sizes, but it is the sizes attribute that tells it which one to pick. If sizes is missing, wrong, or ignored, the browser downloads the largest image in the list, and PageSpeed flags it, srcset or not.