HTML Optimization
This step focuses on low-risk cleanup: reduce HTML noise, remove unused features, and simplify the head so later CSS/JS work is easier.
Choose One Place to Do "Cleanup"
You can remove emojis, embeds, head tags, etc. via a performance plugin, your theme, or small snippets.
Pick one owner so you do not duplicate behavior across multiple tools.
Safe HTML Cleanup Targets
Common low-impact targets:
- emojis
- embeds
- unnecessary head metadata (generator, shortlink, WLW/RSD)
caution
Do not remove query strings from static assets as an "optimization". It often breaks cache busting.
Optional: Remove Common wp_head Tags
Remove selected wp_head tags (optional)
remove_action('wp_head', 'wp_generator');
remove_action('wp_head', 'rsd_link');
remove_action('wp_head', 'wlwmanifest_link');
remove_action('wp_head', 'wp_shortlink_wp_head');
Reduce Plugin Surface Area
If you are carrying plugins that inject a lot of scripts/styles (analytics wrappers, page builders, popups), decide whether they are actually required.
This is not about "plugin count". It is about:
- how much CSS/JS they add
- whether they run on every page
- whether they block rendering or add long tasks
Verification
- Frontend renders correctly (header/footer, primary navigation).
- Console shows no new errors.
- Critical flows still work (forms, search, login, cart/checkout if applicable).