WP Options Table Optimisation – WPENGINE

This topic has 11 replies, 3 voices, and was last updated 1 years, 9 months ago ago by Olga Barlow

  • Avatar: websitedude1985
    WebsiteDude
    Participant
    June 24, 2022 at 07:25

    Hi Guys

    I saw this topic here
    https://www.8theme.com/topic/oversize-wp_options-autoload-row-et_studio_data-how-to-fix/#post-325436

    And wondered if the latest release now includes this?

    Major issues for us for the same reasons and so I hope that you folks have found a way of helping us not feel pain with oversizes options tables 🙂

    10 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    June 24, 2022 at 08:54
    Avatar: websitedude1985
    WebsiteDude
    Participant
    June 29, 2022 at 05:38

    Hi Rose

    thanks for the reply. Please see attached a link to my WP Options Table and you’ll see lots of X Store/theme related autoloaded Data entries – Can you advise if these are all necessary and if not then what I can do about them?

    I am assuming all ET entries are because of the theme?

    Also other items needed for the theme such as the Kirki entry. I’ll list below the ones I am curious about whether we can do anything about them…

    et_studio_data
    189025

    theme_mods_hg-child
    98733

    smile_modal_styles
    71270

    kirki_downloaded_font_files
    48888

    et_multiple_headers_old
    43212

    brainstrom_bundled_products
    37996

    theme_mods_xstore
    35629

    et_multiple_headers
    34622

    et_multiple_single_product
    22069

    smile_style_analytics
    17912

    the above entries I think are related to the theme and your plugins – e.g. Kirki – so can you advise how we can make this better and better performing?

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    June 30, 2022 at 07:01

    Hello,

    I’ve passed your question to our dev team. Waiting for comment from their side. We have a lot of requests these days, so it may take some time. Sorry for this delay.

    Regards

    Avatar: websitedude1985
    WebsiteDude
    Participant
    July 5, 2022 at 05:07

    Hi Guys – any response to this? I have a huge Autoload Data size and many of the DB rows are from the theme – it would be really helpful if your DEVS can take a look at whether or not these rows need to be autoloaded.

    Thanks

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 5, 2022 at 17:08

    Hello,

    et_studio_data – it was excluded from autoloading.

    theme_mods_hg-child – these are settings of some hg-child theme that you use or used

    smile_modal_styles, brainstrom_bundled_products, smile_style_analytics – it’s not related to our theme. We don’t have such things in our theme. Probably it comes from the third-party plugin.

    kirki_downloaded_font_files – it loads the fonts that you chose in theme settings. We can’t remove that from autoload.

    et_multiple_headers_old – we’ll remove that field in the next theme version

    theme_mods_xstore – these are settings of XStore theme. We can’t remove that from autoload.

    et_multiple_headers – you need that if you created multiple headers, to load them quickly on your pages. We can’t remove that from autoload.

    et_multiple_single_product – you need that if you created multiple single product templates, to load them quickly. We can’t remove that from autoload.

    Regards

    Avatar: websitedude1985
    WebsiteDude
    Participant
    July 5, 2022 at 17:30

    HI Olga

    thanks for the reply – that is super helpful.

    I guess this answers a lot then in terms of reliance of 3rd party plugins e.g. Kirki – as you can see it is Autoloading a fair bit and swallows up a lot of the allotted advise 0.8MB limit on autoloaded data on WPEngine who are said to be one fo the best WP hosts. So if your required plugins affect that a lot then this answers why some people suffer poor performance?

    I’m surprised the Child Theme is so large a size – as well as some of your other essential required DB table Rows – I wonder if this can be improved upon as at the moment I have removed lots from my site and turned off Autoload data where I can but the theme itself is swallowing up a lot of my autoloaded data 🙁

    https://share.getcloudapp.com/ApuXJxro

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 5, 2022 at 17:45

    Hello,

    Do you use a lot of different fonts on your site? Kirki is the options framework that we use but we are not developers of that and do not manage that moment with the fonts autoloading. You may ask the plugin developer about this moment here https://wordpress.org/support/plugin/kirki/

    Regards

    Avatar: websitedude1985
    WebsiteDude
    Participant
    July 6, 2022 at 07:07

    Lots of fonts? Not really – but we are about to remove fonts and upoad to Elementor instead so no need to call from Google.

    I see the Kirki autoload data is font related – do you use that in the theme? I wonder if I can disable autoload on this as I intend to use the fonts uploaded to Elementor for use on the site – not sure if Kirki needs to be autoloaded that’s all..

    Overall in XStore there are lots of rows that autoload – is there a way to make this more optimal/streamlined? Just a tohught

    Avatar: websitedude1985
    WebsiteDude
    Participant
    July 11, 2022 at 04:18

    Any update please? I reached out to Kirki but nothing and over 5 days

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 11, 2022 at 15:33

    Hello,

    Take our apologies for the delay in answering.
    We can’t disable autoload of the Kirki fonts via child theme just for you. At the same time, we can’t disable fons autoloading for all the users because many use global fonts, not Elementor fronts, and they need that.

    Regards

  • Viewing 11 results - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.Log in/Sign up

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.