Speed Up Corporate Sites: Cleaning Database Bloat & Unused Assets

How We Pruned 12GB of Legacy Bloat on a Consulting Site Rebuild

A few months ago, a boutique corporate consulting firm hired me to salvage their website. The site was sluggish, taking over eight seconds to load a simple contact page on mobile devices. After digging into the back-end, I realized they were suffering from a classic agency issue: years of stacking conflicting visual editors, redundant sliders, and unoptimized database queries.

Instead of patching a broken system, we decided to perform a hard audit, wipe the database clean of legacy transients, and rebuild the front-end with a performance-first mindset. Here is how we did it.

Step 1: The Database Post-Mortem and SQL Purge

Our first diagnostic run showed that the wp_options and wp_postmeta tables were massively bloated. Old page builders love to leave thousands of orphaned metadata rows even after you delete the plugin. This bloat forces the database to scan millions of rows for simple queries, raising server response times (TTFB).

To fix this, I bypassed the admin dashboard entirely and ran a cleanup directly in the database. First, we cleared out orphaned postmeta records:

DELETE pm FROM wp_postmeta pm
LEFT JOIN wp_posts wp ON wp.ID = pm.post_id
WHERE wp.ID IS NULL;

Next, we purged accumulated transients and expired site options:

DELETE FROM wp_options WHERE option_name LIKE '_transient_%';

Running these commands immediately dropped our database size by over 40%, cutting down query execution time significantly.

Step 2: Transitioning to a Streamlined Theme

Next was the visual layer. We needed to ditch the heavy, legacy page builder that was generating 15 levels of nested <div> tags (DOM depth). I searched for layout bases that used native block editors or very clean grid structures. While browsing several options in the WooCommerce Themes Collection, we realized we did not need a massive e-commerce setup. We just needed a fast, highly-structured business presentation.

We settled on the Cosion WordPress Theme for this specific build. What made this theme work for our audit was its minimal CSS layout footprint. Instead of loading heavy Javascript files to render basic accordions and team profile grids, it uses native, lightweight stylings. By switching to Cosion, our DOM node count dropped from 2,100 to just under 650 on the homepage, which is well below Google's recommended threshold.

Step 3: Script Management and Asset Control

Even with a clean theme, corporate sites tend to slow down once you install marketing, CRM, and tracking scripts. To manage this asset creep, we used a combination of custom code hooks and a few Premium WordPress Plugins to selectively dequeue scripts.

For instance, contact form scripts do not need to load on the "About Us" page. We configured conditional asset loading using native API hooks recommended in the WordPress Developer Resources. This ensures that heavy third-party tracking scripts and form styles only execute on the precise pages where they are needed.

The Realistic Verdict

After stripping the old codebase and deploying the new setup, the site's mobile PageSpeed score climbed from a dismal 34 to a steady 89. Is it a magic fix? No. A clean theme like Cosion gives you an excellent starting block, but you still must be disciplined about database maintenance, image compression, and script management. If you let marketing teams stack random plugins unchecked, you will end up right back where you started.