Complex WordPress sites often depend on far more than WordPress itself. In one pre-migration audit, the site combined a customized Salient theme, WPBakery, 33 active plugins, multiple analytics and advertising platforms, age-verification tools, email infrastructure, and a business-critical ecommerce storefront supplied by Jane Premium / Bloom.
The most important result of the audit was not a large code change. It was establishing ownership boundaries. The Jane storefront was working and was vendor-hosted, so the safest approach was to leave its plugin, page mapping, and redirects intact while escalating Jane-hosted React errors to the vendor rather than trying to repair the storefront application inside WordPress.
Issue background
The WordPress site was being reviewed ahead of a migration and handoff. Because the existing setup was unfamiliar and supported several critical customer workflows, the team performed a detailed technical audit before making changes.
The site included:
- Salient 18.0 with a customized child theme.
- Salient WPBakery 8.6.1.
- Jane Premium 0.0.17 for the live ecommerce storefront.
- Age Gate and WP Terms Popup for age and compliance workflows.
- Advanced Custom Fields and custom content features.
- WP Mail SMTP using Brevo/Sendinblue.
- Google Site Kit, GA4, Microsoft Clarity, and StackAdapt.
- Header Footer Code Manager with global tracking and integration snippets.
The business-critical flow was unusual for a typical WordPress ecommerce site. Shopping, product detail pages, customer accounts, cart, and checkout were powered through Jane’s vendor-hosted storefront rather than a conventional WooCommerce stack.
Diagnosis
The audit identified several technical and operational risks that needed to be understood before migration.
The largest ownership question involved Jane Premium / Bloom. The plugin connected WordPress to Jane’s production storefront, mapped the store to a WordPress page, and supported separate menu experiences. Runtime testing showed that the storefront was functioning, but the Jane application was logging repeated React errors, including errors #418 and #423.
The developer’s conclusion was that these errors belonged to Jane’s hosted application layer rather than to custom WordPress code. Because Freshy did not own the storefront application itself, the correct handoff strategy was to preserve the integration and escalate vendor-side errors to Jane support.
The audit also surfaced several additional concerns:
- Defender and Redirection log tables together occupied roughly 978 MB of database space.
- The Jane storefront responses were unusually large, around 1.8–2.1 MB, with roughly 0.9–1.24 seconds to first byte on tested store and menu routes.
- Ten plugin updates were pending, including nine active plugins.
- Four WordPress administrator accounts remained and required ownership review.
- The Jane plugin documentation listed WordPress compatibility only through version 6.8, while the audited site was running WordPress 7.0.1.
- The site had several handoff-sensitive third-party integrations whose account ownership needed to be documented.
The audit did not find malware or altered WordPress core files. Core checksums passed, suspicious PHP matches were attributable to established plugin libraries, and PHP files under uploads were either empty or protective index files.
Resolution steps
Because this task was an audit and handoff review, the documented work focused on determining what should and should not be changed.
- Identify the business-critical integration first. The Jane storefront handled the site’s primary shopping and checkout experience, so any migration work needed to preserve that integration before addressing lower-priority cleanup.
- Confirm whether the ecommerce layer is actually WordPress-owned. In this case, Jane Premium acted as the integration layer for a vendor-hosted storefront rather than a normal self-contained WordPress shop.
- Leave working vendor-owned functionality intact. The developer recommended preserving the Jane plugin, its Shop page mapping, and the redirects that routed users into the vendor storefront.
- Escalate vendor application errors to the vendor. Repeated React errors in the Jane-hosted storefront were not treated as custom WordPress bugs. They should be documented and sent to Jane support.
- Document integration ownership. The audit identified Jane, Brevo/Sendinblue, GA4, Microsoft Clarity, StackAdapt, NextME, Google Site Kit, and other marketing or operational services that should have known account owners and support contacts.
- Review legacy administrator access before launch. Existing admin accounts, especially former developer or agency accounts, should be confirmed and unnecessary access removed.
- Plan log retention and cleanup. Large Defender and Redirection log tables were flagged for future retention limits and historical-data cleanup because of their database footprint.
- Apply pending plugin updates on staging. The audit recommended controlled batches with regression testing around ACF layouts, injected scripts, email delivery, redirects, and caching rather than updating everything directly on production.
- Confirm vendor compatibility before major WordPress upgrades. Because Jane’s documented compatibility lagged behind the site’s WordPress version, future platform upgrades should include vendor confirmation and storefront regression testing.
- Audit hard-coded and stale integrations in the child theme. The customized Salient child theme contained external links and a template reference to Elfsight even though no Elfsight plugin was installed, making that reference a candidate for later review.
The task notes also recommended future investigation into Jane’s large response payloads and route redirects, but those were follow-up opportunities rather than completed changes in this audit.
Final outcome
The audit established a safe handoff strategy for a complex WordPress installation with a vendor-hosted ecommerce dependency. The Jane storefront was confirmed as operational, and the development team recommended leaving its WordPress integration untouched while routing storefront-specific React errors to Jane’s support team.
The review also documented the site’s primary technical risks: oversized security and redirect logs, large storefront payloads, pending plugin updates, administrator-account cleanup, third-party account ownership, and the need to verify Jane’s compatibility with newer WordPress versions.
No broad performance or security overhaul was documented as completed in this task. Its value was in separating actionable WordPress maintenance from vendor-owned functionality so the migration team could avoid breaking a critical ecommerce flow.
If you are inheriting or migrating a complex WordPress site with private plugins, vendor-hosted ecommerce, custom theme integrations, or undocumented third-party services, contact Freshy. Our WordPress team can audit the stack, identify ownership boundaries, and plan a safer migration or takeover.
