Object Cache on Hostinger uses LiteSpeed Memcached (LSMCD) to store WordPress database query results in memory, so pages that cannot be page-cached (WooCommerce cart, admin, membership dashboards) skip the database on repeat requests. The toggle sits in hPanel, but it only appears if you are on the right plan tier, LiteSpeed Cache is already active, and the LSCWP plugin is installed. This guide covers all three preconditions, how to flip the switch, how to confirm Object Cache is actually storing data, and what to do when the toggle refuses to appear or a plugin fights it.
Prerequisites
Three conditions must be met before Object Cache is even visible in hPanel. Miss any one and the toggle either does not show or does nothing:
- Plan tier: Business Web Hosting, Business WordPress, WordPress Pro, or any Cloud Hosting plan. Single and Premium shared plans do not include Object Cache; upgrading to the Business plan unlocks it. VPS plans manage caching at the server level and do not use the hPanel toggle.
- LiteSpeed Cache active: LSMCD hooks into the LiteSpeed cache stack. If LiteSpeed Cache is off, the Object Cache toggle is disabled. Turn LiteSpeed on first; the LiteSpeed Cache walkthrough covers the hPanel and plugin steps in how to enable LiteSpeed Cache on Hostinger.
- LSCWP plugin installed: The LiteSpeed Cache WordPress plugin ships pre-installed on hPanel-created WordPress sites. If your site was migrated in and the plugin is missing, install it from the WordPress.org plugin directory before enabling Object Cache from hPanel.
Step 1: Enable Object Cache in hPanel
Log in to hPanel, open Websites, and click Dashboard on the site you want to speed up. In the sidebar, go to WordPress > Overview. In the Core section, confirm that LiteSpeed is switched ON, then toggle Object cache ON. Hostinger's own docs note the Object Cache switch is only visible after LiteSpeed is enabled, so if you do not see it, that is the fix.
The switch takes effect immediately. There is no server restart and no need to purge the LSCWP cache; the LSMCD daemon starts caching queries on the next request. If the toggle greys out or throws an error, jump to Common Issues below.
Step 2: Verify Object Cache Is Storing Data
Enabling the toggle is not the same as caching. Two quick checks confirm LSMCD is doing work:
WordPress admin check
Open LiteSpeed Cache > Cache > Object in the WordPress sidebar. You should see Object Cache set to ON and the connection Test Object Cache button returning "Passed". If it says "Failed", LSCWP cannot talk to the LSMCD daemon; the most common cause is a conflicting Redis Object Cache or W3 Total Cache install that has claimed the object cache slot in WordPress.
Terminal check with WP-CLI
If you have SSH access (Business plan and above), run:
wp cache typeThe response should include a reference to LiteSpeed Object Cache or Memcached. If the output says "WordPress Object Cache" (the default in-memory PHP array), Object Cache is not wired up even though the toggle is on. Deactivate any competing object-cache plugin and retest.
Step 3: Confirm Which Pages Benefit
Object Cache does not speed up guest visits to already-cached pages. Those are already served from LiteSpeed's page cache before PHP runs. Object Cache pays off on the pages that page cache cannot touch:
- Logged-in WordPress admin pages: dashboard, editor, plugin screens. Query-heavy admin views can drop from 800 ms to under 200 ms with Object Cache on.
- WooCommerce cart, checkout, and account pages: excluded from page cache by default because they contain per-user data. Object Cache stores product meta, session data, and cart totals in memory instead of hitting the database on every load.
- Membership dashboards (MemberPress, LearnDash, BuddyPress): same pattern. Personalised pages that were previously slow to render become responsive.
- REST API endpoints: especially useful if the site is a headless backend feeding a decoupled frontend or a mobile app.
A static blog with no logged-in traffic will see little visible change from Object Cache alone. If most of your visitors are guests reading posts, focus on page cache and image optimisation first.
Step 4: Handle Persistent Object Cache Plugins
WordPress ships with an in-memory object cache that resets on every request. LSMCD replaces it with a persistent store. If your site was previously running the Redis Object Cache plugin or the W3 Total Cache object-cache module, those must be deactivated before LSMCD takes over, or WordPress ends up with two persistent caches competing for the same key space and returning stale reads.
Deactivation order matters. In WordPress admin, first deactivate the competing plugin. Then delete the wp-content/object-cache.php drop-in file if it did not clean itself up (some plugins leave it behind). Then toggle Object Cache OFF and back ON in hPanel to let LSMCD write its own drop-in file. Verify with the LSCWP Test Object Cache button.
Common Issues and Fixes
Object Cache toggle is missing or greyed out
Two causes account for almost every case. Either your plan does not include Object Cache (Single or Premium shared) and you need to upgrade, or LiteSpeed Cache is off, hiding the toggle. Turn LiteSpeed on first, then look again. If the switch still does not appear on a Business or Cloud plan, contact Hostinger support with your account and domain; there is a rare provisioning bug that requires a manual re-enable on their side.
Object Cache is on but LSCWP says "Failed"
The Object test inside the LSCWP plugin failed to connect to LSMCD. Nine times out of ten the cause is a conflicting plugin (Redis Object Cache, W3 Total Cache, WP Rocket Object Cache add-on) that has taken over the object cache drop-in. Deactivate the conflicting plugin, delete wp-content/object-cache.php, and re-toggle Object Cache in hPanel.
Site behaviour changes after enabling Object Cache
Some poorly-coded plugins store transient data that expects to be non-persistent. Once Object Cache turns those transients persistent, stale values can hang around. Symptoms: outdated notices, wrong stock counts in WooCommerce, missing dashboard widgets. Fix by purging with LiteSpeed Cache > Toolbox > Purge Object Cache. If it recurs, the plugin is the problem and needs an update or replacement.
Should I disable Object Cache in a staging environment
Yes. Hostinger's own docs recommend disabling caching in staging while actively developing, so you see changes on refresh instead of waiting for cache expiry. Toggle Object Cache off in hPanel on the staging site, or use the LSCWP setting Enable Object Cache to disable at the plugin level without touching hPanel.
Does Object Cache replace LiteSpeed Cache?
No, they are complementary. LiteSpeed Cache stores fully-rendered HTML for guest pages so PHP is skipped entirely. Object Cache stores database query results for the pages PHP still has to run. Together they cover both cached and dynamic requests. The rest of the speed stack, including hPanel toggles for PHP OPcache and Brotli, is covered in the Hostinger WordPress Optimization Guide.
