Loadvexa - Autoload & Cache Diagnostics

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. 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. Highlights

• Autoload health score, total size, option count, and large-entry metrics.
• Largest 250 autoloaded option review workspace.
• Search, assessment filters, watch list, and ignore list.
• Likely plugin/theme ownership with confidence scoring.
• Protected, Review, Candidate, and Ignored assessments.
• Automatic protection for WordPress-critical role/capability options.
• Snapshot-before-change workflow with history and one-click restore.
• Read-only safe mode.
• Manual, daily, or weekly audit points and growth alerts.
• Cache & Optimization Advisor with server-aware guidance.
• Page-cache, persistent object-cache, cache-drop-in, asset-optimization capability, and cache/CDN signal detection.
• Two-request cache verification with HIT, MISS, BYPASS, and STALE classification when supported headers are exposed.
• Safe purge integration for supported active cache tools plus exact manual purge paths for others.
• Separate confirmed persistent object-cache flush.
• WooCommerce-aware cache guidance.
• Site Problem Scanner with page-by-page diagnostics and verification.
• Safe batch scanning of up to 300 public URLs per scan run.
• HTTP 4xx/5xx, redirect, response-time, cache-warming, cache-bypass, stale-cache, and restrictive Cache-Control checks.
• Dynamic WooCommerce page checks for Cart, Checkout, and My Account.
• Dynamic UNKNOWN/PRESENT cache states are treated as evidence uncertainty, not as an automatic configuration failure.
• LiteSpeed scanner probes recognize X-LiteSpeed-Cache-Control: no-cache/private as a BYPASS signal inside Loadvexa diagnostics.
• Plugin-specific fix instructions for common cache plugins.
• Re-check one page or a safe batch of problem pages after making a change.
• Verified “Fixed after re-check” state.
• Optimization Profiles for supported native cache-plugin import formats.
• WP Rocket site-specific JSON profile generation for high-confidence scanner-linked changes.
• LiteSpeed Cache native .data profile generation for high-confidence scanner-linked changes.
• Profile generation is blocked until Site Problem Scanner reaches 100% for the current scan.
• Profile diff preview shows current setting, recommended setting, and the finding that justifies the change.
• A zero-change profile result is a valid outcome; Loadvexa does not present an import as necessary when no safe change exists.
• Actionable manual findings are separated from informational cache-evidence checks.
• JSON and CSV autoload diagnostic exports without option values.
• WordPress Site Health integration and diagnostics.
• Multisite-aware active plugin detection.
• WP-CLI tools: wp aulonexa status, wp aulonexa top, and wp aulonexa audit.
• No external account, ads, telemetry, or frontend assets.

Optimization Profiles Optimization Profiles connect diagnosis to a controlled configuration workflow. 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. 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. Current profile adapters include:

• WP Rocket: JSON settings profile based on the site's current WP Rocket configuration, with issue-linked changes applied.
• LiteSpeed Cache: native .data import profile using LiteSpeed's current import format, containing the version marker and only the setting keys Loadvexa intentionally changes.

Loadvexa 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. 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. Site Problem Scanner The Site Problem Scanner turns cache and response diagnostics into a page-by-page workflow. 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. For each scanned URL, Loadvexa can report:

• HTTP response status.
• Server-side probe duration.
• Cache HIT, MISS, BYPASS, STALE, detected/unclassified, or unknown state where cache headers are available.
• Whether repeated anonymous requests warm a public page to a cache HIT.
• Unexpected cache bypass on ordinary public pages.
• Shared-cache HIT on dynamic WooCommerce pages.
• Cache-evidence uncertainty on dynamic WooCommerce pages when no explicit signal is exposed.
• Restrictive Cache-Control on ordinary public pages.
• Page-specific fix steps and the exact cache-plugin menu path to review.

After following a fix, use “Re-check this page” or “Re-check problem pages”. Loadvexa runs the same diagnostic again and can mark a previously detected issue as fixed when the problem is no longer present. 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. Cache & Optimization Advisor The advisor separates page cache, persistent object cache, asset-optimization capability, cache drop-ins, and public cache/CDN response signals. 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. 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. Safety model 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. 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. 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. 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.

1.4.1

• Renamed the plugin to Loadvexa - Autoload & Cache Diagnostics with a distinctive directory identity.
• Updated the WordPress.org text domain/package identity for the pending directory review.
• Replaced the compressed advanced admin script with human-readable source.
• Documented the public development source and packaging process.

1.4.0

• Added Optimization Profiles for supported cache-plugin native import formats.
• Added WP Rocket JSON profile generation based on current site settings and high-confidence scanner-linked changes.
• Added LiteSpeed Cache native .data profile generation for high-confidence scanner-linked changes.
• Added exact import paths and import/purge/re-check workflow guidance.
• Added profile diff preview with current setting, recommended setting, and reason.
• Blocked profile generation until the current bounded Site Problem Scanner run reaches 100%.
• Kept slow responses, HTTP/route errors, UNKNOWN cache states, and other non-deterministic findings out of automatic profile changes.
• Separated actionable manual findings from informational cache-evidence checks.
• Added a dedicated no-import-needed state when a completed scan produces zero safe profile changes.
• Recognized LiteSpeed X-LiteSpeed-Cache-Control: no-cache/private as BYPASS evidence inside Loadvexa scanner requests.
• Normalized pre-release dynamic UNKNOWN Info promotions back to their real underlying severity; UNKNOWN alone is not treated as a cache-setting failure.

1.3.0

• Added Site Problem Scanner for page-by-page diagnostics.
• Added safe batch scanning with a 300-public-URL safety cap.
• Added scanning for home/front/posts pages, published public post types, and key WooCommerce pages.
• Added HTTP 4xx/5xx and redirect checks.
• Added page-level response-time checks.
• Added repeated-request cache warming checks and page-level HIT/MISS/BYPASS/STALE interpretation.
• Added unexpected public-page bypass and restrictive Cache-Control review.
• Added dynamic WooCommerce page protection checks for shared cache HITs.
• Added plugin-specific purge, cache-setting, and exclusion paths for common cache plugins.
• Added Re-check this page and Re-check problem pages workflows.
• Added verified Fixed after re-check state.
• Added same-site URL validation and no-content-storage scanning model.

1.2.1

• Added two-request warm-cache verification.
• Added HIT/MISS/BYPASS/STALE cache classification.
• Added Next Best Action guidance.
• Refined asset-optimization capability reporting and overlapping-cache wording.

1.2.0

• Added Cache & Optimization Advisor, cache-stack detection, site-fit recommendations, safe purge integrations, manual purge paths, object-cache flush, and WooCommerce-aware cache guidance.

1.1.0

• Added monitoring/audit trends, search/filtering, watch/ignore, read-only mode, custom protection, CSV export, diagnostics, Site Health Info, and WP-CLI tools.

1.0.0

• Initial release with health score, scanner, ownership heuristics, protected options, snapshots, restore history, Site Health integration, and JSON export.