Title: Options table BLoat
Last modified: June 4, 2026

---

# Options table BLoat

 *  Resolved [kierancalv](https://wordpress.org/support/users/kierancalv/)
 * (@kierancalv)
 * [4 days, 1 hour ago](https://wordpress.org/support/topic/options-table-bloat/)
 * Hi Guys, Any plans to fix the 197 autoload options your plugin adds? Odd decision
   for a speed optimisation plugin, I have to say:) Why not just serialise the options?

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Support [litetim](https://wordpress.org/support/users/litetim/)
 * (@litetim)
 * [4 days ago](https://wordpress.org/support/topic/options-table-bloat/#post-18928319)
 * [@kierancalv](https://wordpress.org/support/users/kierancalv/) 
   The aspect of
   serialization has beent talked with the developers and is taken into considerations.
   From what I see, the options have **auto** by default.How recently did you installed
   the plugin?We are a cache and optimization plugin. The ideea is that cache is
   generated, then there will no need to run all the code all over again and be 
   served faster.
 *  Thread Starter [kierancalv](https://wordpress.org/support/users/kierancalv/)
 * (@kierancalv)
 * [3 days, 23 hours ago](https://wordpress.org/support/topic/options-table-bloat/#post-18928412)
 * Thanks for getting back to me.
 * The plugin was installed today on this site, but I’ve added it to around 20 sites
   over the past month as I’ve moved back to using LITESPEED on the Server. It’s
   only now that I noticed the options issue.
 * On inspection, the plugin is creating 197 separate options. On sites running 
   WooCommerce and several other plugins, this can push the options table much closer
   to recommended limits than it needs to be.
 * I spend a lot of time optimising the options table to improve admin performance,
   particularly on sites with a large number of resource-heavy plugins. Having this
   plugin add 197 individual options when they could potentially be stored as a 
   much smaller number of serialised options makes optimisation significantly more
   difficult.
 * Ideally, related settings should be consolidated into serialised options rather
   than being stored as hundreds of separate entries. This would reduce the overall
   option count, keep the database cleaner, and improve scalability on larger WordPress
   installations.
 *  Plugin Support [litetim](https://wordpress.org/support/users/litetim/)
 * (@litetim)
 * [3 days, 21 hours ago](https://wordpress.org/support/topic/options-table-bloat/#post-18928550)
 * [@kierancalv](https://wordpress.org/support/users/kierancalv/) I totally agree
   with you.
   Changing how options are saved is something we are looking into and
   one of the things we are going to change.I cannot give you a timeline about the
   change
 *  Thread Starter [kierancalv](https://wordpress.org/support/users/kierancalv/)
 * (@kierancalv)
 * [3 days, 19 hours ago](https://wordpress.org/support/topic/options-table-bloat/#post-18928671)
 * Thanks for the update 🙂
 * Cheers

Viewing 4 replies - 1 through 4 (of 4 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Foptions-table-bloat%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [kierancalv](https://wordpress.org/support/users/kierancalv/)
 * Last activity: [3 days, 19 hours ago](https://wordpress.org/support/topic/options-table-bloat/#post-18928671)
 * Status: resolved