The situation we observed
The original WordPress site used a Consultio-based theme and a large set of page-builder, commerce and service plugins.Read more
The initial audit covered 109 published URLs. The task was to make vendor-exit guidance and professional consultation clear while preserving useful content and functioning legacy routes.
What changed
We introduced a lightweight theme, a portable editorial catalogue, product and exit-plan pages, four browser-based planning tools and a private enquiry workflow.Read more
The editorial routes load only the plugins they use. Legacy membership and donation routes retain their required functionality; a global plugin purge would have risked breaking those areas.
Measured before and after the initial rebuild
In the initial homepage HTML checks, linked stylesheets fell from 73 to 1 and script tags from 123 to 4.Read more
The captured HTML response went from 248,004 to 46,083 bytes. These are measurements of those captured responses, not a guaranteed load-time improvement or a Core Web Vitals score. This later language and IGEARS update adds content, so current response sizes may differ.
What we checked before calling the first release complete
The first release checked all 73 new catalogue pages, their headings and metadata, internal links, tool calculations and enquiry validation.Read more
Existing URL outcomes were recorded as retained pages, relevant redirects or intentionally retired demo content. Mobile pages were checked for horizontal overflow, and the enquiry test records were removed from active enquiries.
The maintenance trade-off is explicit
The new catalogue is stored as portable JSON and rendered by a documented theme and plugin.Read more
Its generated page bodies are maintained through that source workflow, rather than the ordinary WordPress page editor; existing posts remain editable in WordPress. This makes handover files important. A lower dependency count is useful only if another team also receives the source, publishing instructions, backups and validation procedure.
What this means for another website
This was a rebuild of our own resource, not a claimed result for an unnamed client.Read more
Your site may have different commerce, membership, publishing and compliance requirements. IGEARS can inspect those constraints and compare retaining the current implementation with a scoped rebuild before making a recommendation.
Sources and verification
Policies and features can change. Verify the current terms and your installed edition before implementation.