[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fDzZjB3fkWvfl0EX5HzvXM7lMhxUyr011bCkyp_dxpLY":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"adelong01","https:\u002F\u002Fprofiles.wordpress.org\u002Fadelong01\u002F",1,0,100,30,94,"2026-04-03T19:21:11.590Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":7,"num_ratings":7,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":30,"download_link":31,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"quantumcache","QuantumCache","0.1.6","\u003Cp>QuantumCache speeds up WordPress by caching database query results (not full pages). It integrates with WordPress query execution to cache post ID lists and content fragments that WordPress uses to build pages, reducing database load while preserving correct invalidation.\u003C\u002Fp>\n\u003Cp>It is \u003Cem>not\u003C\u002Fem> an output buffer or page cache, and it does not replace existing page caching solutions.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Caches the results of the main front-end \u003Ccode>WP_Query\u003C\u002Fcode> for anonymous requests.\u003C\u002Fli>\n\u003Cli>Tag-based invalidation: purge by post ID, post type, or taxonomy.\u003C\u002Fli>\n\u003Cli>Fragment caching for \u003Ccode>the_content\u003C\u002Fcode> (classic) and core blocks such as \u003Ccode>core\u002Fpost-content\u003C\u002Fcode>, \u003Ccode>core\u002Flatest-posts\u003C\u002Fcode>, \u003Ccode>core\u002Farchives\u003C\u002Fcode>, and \u003Ccode>core\u002Fnavigation\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Multiple storage modes:\n\u003Cul>\n\u003Cli>Auto – use Redis if available, otherwise fall back to MySQL.\u003C\u002Fli>\n\u003Cli>Redis – fastest mode; uses the PHP Redis extension.\u003C\u002Fli>\n\u003Cli>MySQL – portable fallback using compact tables (\u003Ccode>qc_entries\u003C\u002Fcode>, \u003Ccode>qc_tagmap\u003C\u002Fcode>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Compatible with the Redis Object Cache drop-in.\u003C\u002Fli>\n\u003Cli>Avoids wp_options and postmeta storage – all cache data is stored in Redis or\u003Cbr \u002F>\nQuantumCache-owned database tables.\u003C\u002Fli>\n\u003Cli>Multisite-aware: per-site prefixes and per-site tables.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Performance summary\u003C\u002Fh3>\n\u003Cp>In benchmarks on a plugin-heavy WordPress site (WooCommerce + Yoast SEO),\u003Cbr \u002F>\nQuantumCache reduced per-request database queries by ~99% on cached pages\u003Cbr \u002F>\nand achieved cache hit rates exceeding 97% with Redis.\u003C\u002Fp>\n\u003Cp>Under production-like load with a networked database, Redis mode delivered\u003Cbr \u002F>\n13–18% lower TTFB at both median and 95th percentile versus uncached\u003Cbr \u002F>\nbaseline. MySQL fallback mode delivered 4–8% improvement under the same\u003Cbr \u002F>\nconditions.\u003C\u002Fp>\n\u003Cp>Actual results depend on theme, plugins, database topology, and traffic\u003Cbr \u002F>\npatterns.\u003C\u002Fp>\n\u003Ch3>Debug headers (optional)\u003C\u002Fh3>\n\u003Cp>Enable \u003Cem>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> QuantumCache \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Send X-QC debug headers\u003C\u002Fem> to view cache status in HTTP responses:\u003Cbr \u002F>\n* \u003Ccode>X-QC-Main: HIT | MISS | STORE\u003C\u002Fcode>\u003Cbr \u002F>\n* \u003Ccode>X-QC-Store: AUTO | redis | mysql\u003C\u002Fcode>\u003Cbr \u002F>\n* \u003Ccode>X-QC-Hydrated:\u003C\u002Fcode> number of posts loaded from cache\u003C\u002Fp>\n\u003Cp>Append \u003Ccode>?qc_nocache=1\u003C\u002Fcode> to any URL to bypass caching for that request.\u003C\u002Fp>\n\u003Cp>Debug headers are sent only when explicitly enabled in settings and contain no\u003Cbr \u002F>\npersonal or user-specific data.\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>QuantumCache does not collect, send, or log personal data.\u003Cbr \u002F>\nIt stores cache entries in Redis or its own MySQL tables.\u003Cbr \u002F>\nOther plugins on your site may handle cookies or data independently.\u003Cbr \u002F>\nNo remote requests are made, and no data is transmitted to external servers.\u003C\u002Fp>\n","Speeds up WordPress by caching database queries and fragments for anonymous visitors using Redis or MySQL, without storing cache data in wp_options.",143,"2026-03-02T20:45:00.000Z","6.9.4","6.0","8.0",[25,26,27,28,29],"caching","database","multisite","performance","redis","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquantumcache.0.1.6.zip",null,"2026-03-15T15:16:48.613Z"]