Directory-review naming and source-availability compliance update.<\/p>","1.4.0":"
Adds conservative importable optimization profiles for supported cache plugins and verifies the real result through Site Problem Scanner instead of assuming a settings import fixed the site.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3677160,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3677160,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3677160,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3677160,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3677160,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.4.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3677160,"resolution":"1","location":"assets","locale":"","width":1365,"height":768},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3677160,"resolution":"2","location":"assets","locale":"","width":1365,"height":768},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3677160,"resolution":"3","location":"assets","locale":"","width":1365,"height":768},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3677160,"resolution":"4","location":"assets","locale":"","width":1365,"height":768},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3677160,"resolution":"5","location":"assets","locale":"","width":1365,"height":768}},"screenshots":{"1":"Autoload Health Overview - health score, total autoload size, option count, and protected\/review classifications.","2":"Monitor & Tools - audit trends, watched options, review workspace, diagnostics, and safety controls.","3":"Cache & Optimization Advisor - detected cache layers, server fit, purge guidance, and verification signals.","4":"Site Problem Scanner - bounded page-by-page scan progress, response timing, cache evidence, and review status.","5":"Optimization Profiles - supported cache-plugin readiness, conservative import guidance, and manual findings."}},"plugin_section":[],"plugin_tags":[1328,146,153,247,151481],"plugin_category":[52,54,59],"plugin_contributors":[],"plugin_business_model":[],"class_list":["post-359377","plugin","type-plugin","status-publish","hentry","plugin_tags-autoload","plugin_tags-cache","plugin_tags-database","plugin_tags-performance","plugin_tags-site-health","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_committers-wpzenora"],"banners":{"banner":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/banner-772x250.png?rev=3677160","banner_2x":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/banner-1544x500.png?rev=3677160","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/icon.svg?rev=3677160","icon":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/icon.svg?rev=3677160","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/screenshot-1.png?rev=3677160","caption":"Autoload Health Overview - health score, total autoload size, option count, and protected\/review classifications."},{"src":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/screenshot-2.png?rev=3677160","caption":"Monitor & Tools - audit trends, watched options, review workspace, diagnostics, and safety controls."},{"src":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/screenshot-3.png?rev=3677160","caption":"Cache & Optimization Advisor - detected cache layers, server fit, purge guidance, and verification signals."},{"src":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/screenshot-4.png?rev=3677160","caption":"Site Problem Scanner - bounded page-by-page scan progress, response timing, cache evidence, and review status."},{"src":"https:\/\/ps.w.org\/loadvexa-autoload-diagnostics\/assets\/screenshot-5.png?rev=3677160","caption":"Optimization Profiles - supported cache-plugin readiness, conservative import guidance, and manual findings."}],"raw_content":"\n
Loadvexa is a WordPress performance toolkit for auditing autoloaded options, diagnosing database and cache issues, finding page-specific performance problems, and verifying whether fixes actually worked. It combines autoload health monitoring, cache guidance, page-by-page diagnostics, conservative optimization profiles, and snapshot-backed restore tools in one workflow.<\/p>\n\n
Loadvexa does not delete option values, does not automatically change unknown options, does not install third-party cache plugins, does not crawl external domains, and does not silently import configuration into another plugin.<\/p>\n\n
X-LiteSpeed-Cache-Control: no-cache\/private<\/code> as a BYPASS signal inside Loadvexa diagnostics.<\/li>\n- Plugin-specific fix instructions for common cache plugins.<\/li>\n
- Re-check one page or a safe batch of problem pages after making a change.<\/li>\n
- Verified \u201cFixed after re-check\u201d state.<\/li>\n
- Optimization Profiles for supported native cache-plugin import formats.<\/li>\n
- WP Rocket site-specific JSON profile generation for high-confidence scanner-linked changes.<\/li>\n
- LiteSpeed Cache native
.data<\/code> profile generation for high-confidence scanner-linked changes.<\/li>\n- Profile generation is blocked until Site Problem Scanner reaches 100% for the current scan.<\/li>\n
- Profile diff preview shows current setting, recommended setting, and the finding that justifies the change.<\/li>\n
- A zero-change profile result is a valid outcome; Loadvexa does not present an import as necessary when no safe change exists.<\/li>\n
- Actionable manual findings are separated from informational cache-evidence checks.<\/li>\n
- JSON and CSV autoload diagnostic exports without option values.<\/li>\n
- WordPress Site Health integration and diagnostics.<\/li>\n
- Multisite-aware active plugin detection.<\/li>\n
- WP-CLI tools:
wp aulonexa status<\/code>, wp aulonexa top<\/code>, and wp aulonexa audit<\/code>.<\/li>\n- No external account, ads, telemetry, or frontend assets.<\/li>\n<\/ul>\n\n
Optimization Profiles<\/h4>\n\n
Optimization Profiles connect diagnosis to a controlled configuration workflow.<\/p>\n\n
Loadvexa first requires the current Site Problem Scanner run to reach 100%. It then examines the saved findings and checks whether the active cache plugin has a native import format that Loadvexa explicitly supports. A downloadable profile is offered only when a finding maps to a high-confidence configuration change.<\/p>\n\n
For example, if a dynamic commerce URL is actually detected as a shared full-page cache HIT, Loadvexa can propose adding that exact path to the cache plugin's exclusion setting. It does not enable aggressive JavaScript\/CSS optimization simply because those switches exist.<\/p>\n\n
Current profile adapters include:<\/p>\n\n
\n- WP Rocket: JSON settings profile based on the site's current WP Rocket configuration, with issue-linked changes applied.<\/li>\n
- LiteSpeed Cache: native
.data<\/code> import profile using LiteSpeed's current import format, containing the version marker and only the setting keys Loadvexa intentionally changes.<\/li>\n<\/ul>\n\nLoadvexa shows the native import path in the WordPress dashboard only when an importable change is actually ready. The administrator downloads and imports the file manually, purges cache, then returns to Site Problem Scanner and re-checks the problem pages. Loadvexa does not mark a problem fixed merely because a file was downloaded or imported.<\/p>\n\n
A settings file cannot safely repair every problem. HTTP errors, redirects, slow PHP\/database work, hosting limits, and external API latency remain manual findings. An UNKNOWN cache status is kept as an informational evidence gap unless a stronger signal establishes a real cache problem; UNKNOWN by itself does not justify mutating cache settings.<\/p>\n\n
Site Problem Scanner<\/h4>\n\n
The Site Problem Scanner turns cache and response diagnostics into a page-by-page workflow.<\/p>\n\n
A scan can include the home page, configured front\/posts pages, published public post types such as pages, posts and products, and key WooCommerce pages. Loadvexa processes only a small batch at a time to reduce load and caps a scan at 300 public URLs.<\/p>\n\n
For each scanned URL, Loadvexa can report:<\/p>\n\n
\n- HTTP response status.<\/li>\n
- Server-side probe duration.<\/li>\n
- Cache HIT, MISS, BYPASS, STALE, detected\/unclassified, or unknown state where cache headers are available.<\/li>\n
- Whether repeated anonymous requests warm a public page to a cache HIT.<\/li>\n
- Unexpected cache bypass on ordinary public pages.<\/li>\n
- Shared-cache HIT on dynamic WooCommerce pages.<\/li>\n
- Cache-evidence uncertainty on dynamic WooCommerce pages when no explicit signal is exposed.<\/li>\n
- Restrictive
Cache-Control<\/code> on ordinary public pages.<\/li>\n- Page-specific fix steps and the exact cache-plugin menu path to review.<\/li>\n<\/ul>\n\n
After following a fix, use \u201cRe-check this page\u201d or \u201cRe-check problem pages\u201d. Loadvexa runs the same diagnostic again and can mark a previously detected issue as fixed when the problem is no longer present.<\/p>\n\n
The scanner recognizes guidance paths for LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache, WP Fastest Cache, Breeze, Speed Optimizer, and WP-Optimize. If no recognized WordPress page-cache plugin is active, Loadvexa points the administrator toward host\/CDN cache controls instead of inventing a plugin-specific fix.<\/p>\n\n
Cache & Optimization Advisor<\/h4>\n\n
The advisor separates page cache, persistent object cache, asset-optimization capability, cache drop-ins, and public cache\/CDN response signals.<\/p>\n\n
Loadvexa can detect common cache\/optimization plugins and show where their cache controls live. For integrations with a stable callable purge API, an administrator can purge from Loadvexa and immediately run a two-request front-end verification. If no supported API is available, Loadvexa shows the manual menu path instead of attempting an unsafe workaround.<\/p>\n\n
Loadvexa does not install cache plugins automatically. On LiteSpeed\/OpenLiteSpeed servers, LiteSpeed Cache may be suggested as a natural server-integrated option. Existing stable cache setups are favored over unnecessary plugin switching.<\/p>\n\n
Safety model<\/h4>\n\n
Loadvexa never displays or exports WordPress option values in its autoload diagnostic reports. Autoload changes are administrator initiated, snapshot backed, applied through WordPress APIs where available, and verified afterward.<\/p>\n\n
Optimization profile generation is a separate administrator-requested export. A profile is created only for a detected supported cache plugin and is downloaded directly to the administrator. It is not sent to Loadvexa or an external service and is not imported automatically. WP Rocket profiles are based on the site's current WP Rocket settings and should be treated as private site-specific configuration files.<\/p>\n\n
The page scanner is restricted to URLs on the same WordPress site. It uses anonymous requests and stores response metadata needed for diagnosis rather than page content. It does not follow links into external domains.<\/p>\n\n
Cache recommendations are advisory. Hosting-level caches, CDNs, reverse proxies, logged-in behavior, custom rules, security products, and commerce sessions can change the best setup. Test important storefront, checkout, account, form, and admin workflows after performance changes.<\/p>\n\n
Source Code and Build<\/h3>\n\n
All PHP, JavaScript, and CSS used by this plugin is included in this distributed package in human-readable, editable form. Loadvexa does not ship compiled or minified custom runtime assets and does not require npm, webpack, transpilation, or a separate build step to regenerate the distributed code.<\/p>\n\n\n
\n- Upload the
loadvexa-autoload-diagnostics<\/code> folder to \/wp-content\/plugins\/<\/code> or install the ZIP from Plugins > Add New Plugin > Upload Plugin.<\/li>\n- Activate Loadvexa.<\/li>\n
- Open Loadvexa in the WordPress admin menu.<\/li>\n
- Use Overview and Monitor & Tools for autoload diagnostics.<\/li>\n
- Use Optimization Advisor for cache-stack guidance.<\/li>\n
- Use Site Problem Scanner for page-by-page checks and guided verification.<\/li>\n
- Complete the current scan, then open Optimization Profiles if a supported cache-plugin import profile is useful.<\/li>\n<\/ol>\n\n\n
\nDoes Loadvexa delete database options?<\/h3><\/dt>\nNo. It does not delete option values.<\/p><\/dd>\n
Does Loadvexa automatically disable options?<\/h3><\/dt>\nNo. Unknown or third-party entries are never changed automatically.<\/p><\/dd>\n
Does Loadvexa install or force a cache plugin?<\/h3><\/dt>\nNo. Recommendations are advisory. Loadvexa never automatically installs a third-party cache plugin and never requires a paid cache product.<\/p><\/dd>\n
Which cache tools can Loadvexa recognize?<\/h3><\/dt>\nThe optimization advisor recognizes several common WordPress cache\/optimization plugins, including LiteSpeed Cache, WP Rocket, WP Super Cache, W3 Total Cache, WP Fastest Cache, Breeze, Speed Optimizer, WP-Optimize, and Autoptimize. Site Problem Scanner provides detailed cache-setting\/exclusion paths for common page-cache tools.<\/p><\/dd>\n
Which plugins can receive an Loadvexa import profile?<\/h3><\/dt>\nVersion 1.4.0 includes explicit profile adapters for WP Rocket JSON settings imports and LiteSpeed Cache native .data<\/code> settings imports. Other detected cache plugins continue to receive guided manual instructions until their import format and safe behavior are explicitly supported.<\/p><\/dd>\nWhy must the Site Problem Scanner finish before profile download?<\/h3><\/dt>\nA partial scan could miss a dynamic page or a conflicting problem and produce an incomplete recommendation. Requiring the current scan to reach 100% makes the generated profile reflect the full bounded scan set rather than the first few pages.<\/p><\/dd>\n
Why does Optimization Profiles sometimes show zero safe changes?<\/h3><\/dt>\nThat is a valid result. It means the scan did not find a high-confidence cache setting change that Loadvexa can safely encode into the detected plugin's native import format. Do not import a configuration file merely because the plugin supports imports; address only genuine actionable findings and re-check them.<\/p><\/dd>\n
Does Loadvexa import the profile automatically?<\/h3><\/dt>\nNo. Download, review, import, and cache purge remain explicit administrator actions. After import, use the Site Problem Scanner re-check workflow to verify the actual result.<\/p><\/dd>\n
Will the profile enable every optimization setting?<\/h3><\/dt>\nNo. Aggressive CSS\/JS, delay, combine, image, crawler, or object-cache switches are not enabled merely because they exist. Loadvexa limits generated changes to high-confidence findings that map directly to a known setting.<\/p><\/dd>\n
What does Site Problem Scanner change on my site?<\/h3><\/dt>\nNothing automatically. It sends anonymous same-site diagnostic requests, evaluates response\/cache metadata, and shows fix instructions. You choose whether to change a cache-plugin or server setting.<\/p><\/dd>\n
Can it scan every site regardless of size?<\/h3><\/dt>\nA scan is deliberately capped at 300 public URLs and processed in small batches. This keeps the tool practical for typical sites without turning diagnostics into a high-load crawler. Very large sites should prioritize representative\/key URLs or use dedicated performance monitoring tooling for exhaustive crawling.<\/p><\/dd>\n
How does fix verification work?<\/h3><\/dt>\nLoadvexa stores the previous diagnostic result. After you change the cache\/server configuration, re-check the page. If the previously actionable condition is no longer detected, Loadvexa marks it as fixed after re-check.<\/p><\/dd>\n
Does the scanner store my page content?<\/h3><\/dt>\nNo. It stores page identity plus response metadata required for the diagnostic result, not the page body.<\/p><\/dd>\n
Why is object-cache flush separate?<\/h3><\/dt>\nPersistent object cache differs from page cache. Flushing it can temporarily increase database\/server work while objects warm again, so Loadvexa keeps it behind a separate explicit confirmation.<\/p><\/dd>\n
Does it use an external service?<\/h3><\/dt>\nNo external account or service is required. Optional page\/cache probes request only URLs on the WordPress site itself.<\/p><\/dd>\n
Does it work with multisite?<\/h3><\/dt>\nLoadvexa recognizes network-active plugins when estimating ownership and detecting cache integrations. Audits and settings are maintained per site. Profile imports should be reviewed in the context of the cache plugin's own multisite behavior.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.4.1<\/h4>\n\n\n- Renamed the plugin to Loadvexa - Autoload & Cache Diagnostics with a distinctive directory identity.<\/li>\n
- Updated the WordPress.org text domain\/package identity for the pending directory review.<\/li>\n
- Replaced the compressed advanced admin script with human-readable source.<\/li>\n
- Documented the public development source and packaging process.<\/li>\n<\/ul>\n\n
1.4.0<\/h4>\n\n\n- Added Optimization Profiles for supported cache-plugin native import formats.<\/li>\n
- Added WP Rocket JSON profile generation based on current site settings and high-confidence scanner-linked changes.<\/li>\n
- Added LiteSpeed Cache native
.data<\/code> profile generation for high-confidence scanner-linked changes.<\/li>\n- Added exact import paths and import\/purge\/re-check workflow guidance.<\/li>\n
- Added profile diff preview with current setting, recommended setting, and reason.<\/li>\n
- Blocked profile generation until the current bounded Site Problem Scanner run reaches 100%.<\/li>\n
- Kept slow responses, HTTP\/route errors, UNKNOWN cache states, and other non-deterministic findings out of automatic profile changes.<\/li>\n
- Separated actionable manual findings from informational cache-evidence checks.<\/li>\n
- Added a dedicated no-import-needed state when a completed scan produces zero safe profile changes.<\/li>\n
- Recognized LiteSpeed
X-LiteSpeed-Cache-Control: no-cache\/private<\/code> as BYPASS evidence inside Loadvexa scanner requests.<\/li>\n- Normalized pre-release dynamic UNKNOWN Info promotions back to their real underlying severity; UNKNOWN alone is not treated as a cache-setting failure.<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- Added Site Problem Scanner for page-by-page diagnostics.<\/li>\n
- Added safe batch scanning with a 300-public-URL safety cap.<\/li>\n
- Added scanning for home\/front\/posts pages, published public post types, and key WooCommerce pages.<\/li>\n
- Added HTTP 4xx\/5xx and redirect checks.<\/li>\n
- Added page-level response-time checks.<\/li>\n
- Added repeated-request cache warming checks and page-level HIT\/MISS\/BYPASS\/STALE interpretation.<\/li>\n
- Added unexpected public-page bypass and restrictive Cache-Control review.<\/li>\n
- Added dynamic WooCommerce page protection checks for shared cache HITs.<\/li>\n
- Added plugin-specific purge, cache-setting, and exclusion paths for common cache plugins.<\/li>\n
- Added Re-check this page and Re-check problem pages workflows.<\/li>\n
- Added verified Fixed after re-check state.<\/li>\n
- Added same-site URL validation and no-content-storage scanning model.<\/li>\n<\/ul>\n\n
1.2.1<\/h4>\n\n\n- Added two-request warm-cache verification.<\/li>\n
- Added HIT\/MISS\/BYPASS\/STALE cache classification.<\/li>\n
- Added Next Best Action guidance.<\/li>\n
- Refined asset-optimization capability reporting and overlapping-cache wording.<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- Added Cache & Optimization Advisor, cache-stack detection, site-fit recommendations, safe purge integrations, manual purge paths, object-cache flush, and WooCommerce-aware cache guidance.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Added monitoring\/audit trends, search\/filtering, watch\/ignore, read-only mode, custom protection, CSV export, diagnostics, Site Health Info, and WP-CLI tools.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release with health score, scanner, ownership heuristics, protected options, snapshots, restore history, Site Health integration, and JSON export.<\/li>\n<\/ul>","raw_excerpt":"Audit autoloaded options, diagnose database and cache issues, scan slow pages, and verify WordPress performance fixes safely.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/359377","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=359377"}],"author":[{"embeddable":true,"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/wpzenora"}],"wp:attachment":[{"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=359377"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=359377"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=359377"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=359377"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=359377"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/hau.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=359377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}