Fix Hostinger Nullroute WordPress Issue

My Hostinger account has been null-routed because one WordPress domain is spiking CPU, memory and process counts. I already know exactly which site is responsible and have tried the obvious fixes—disabled almost every plugin, run database optimisation, and compressed large images—but the server still blocks traffic as soon as I ask for the nullroute to be lifted.

I need a WordPress performance specialist who understands Hostinger’s hPanel, LiteSpeed stack, and WP-CLI to dig deeper, pinpoint what is still chewing resources (rogue code, theme bottlenecks, cron jobs, malware, mis-configured cache—whatever it is) and implement a sustainable fix. You may also need to adjust PHP limits, set up object caching, or fine-tune LiteSpeed/Cloudflare settings if that proves decisive.

Deliverables
• Detailed diagnosis of the remaining resource drain
• All code, theme, plugin, or server-level changes applied and documented
• Nullroute lifted and site publicly accessible, holding below Hostinger’s CPU/memory thresholds for at least 24 hours
• Short hand-off report so I can maintain the optimisation going forward

If you’ve solved similar Hostinger nullroute situations before, let me know—speed and precision matter here.