• Resolved Ludovic Bablon

    (@maboutiquewp)


    Hi.
    To optimize the load speed of my WP websites, I need to have a deeper understanding of the autoload options and its impact.

    It seems that having many autoloaded options, especially big ones, slows the loading of all pages of a site.

    It seems to impact the TTFB (time to first byte), and it can be signaled as a problem in the health check.

    Is it true ?

    I disabled the autoload of many options with the plugin SweepPress, and it improved some Core web vitals.

    How is this problem related to the PHP server memory ? Shouldn’t a big memory (like 64mo) be far enough when the wp options reaches something 2 mo ?

    And, when I use an object cache on the server, like Redis Cache, does it store all the data that are NOT autoloaded, replacing the autoload function a better way ?

    What are exactly the consequences of disabling some autoloaded options ? A non-autoloaded option will cause a call to the database, and take more loading time than if it was autoloaded ?

    If someone could explain how those things are related – autoloaded options, server memory, object cache – I would make better choices in optimizing my sites and my customers’s sites !

    Thanks in advanced to anybody willing to get me out of this technical fog !

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)

The topic ‘Autoload, object cache and page speed optimization’ is closed to new replies.