Antes de publicar reproducimos cada paso en al menos dos marcas si depende del proveedor. o dos veces en días distintos si no. Capturamos errores de consola, etiquetas que cambian por región y actualizamos si mueven un botón. Rutas y capturas se revisan trimestralmente. En DNS, SSL o pagos verificamos opciones de recuperación y enlazamos la documentación oficial.
No amount of optimisation fixes fundamentally slow hosting. Your hosting determines your base TTFB (Time to First Byte). The time before your server starts sending any data. Quality hosts using LiteSpeed (Hostinger) or Google Cloud infrastructure (Kinsta) deliver 80–150ms TTFB; poor shared hosting can exceed 800ms. If your host is the bottleneck, migrate first.
Caching stores pre-generated HTML pages and serves them without executing PHP and database queries on every request. For most hosts: WP Super Cache (free, simple) or W3 Total Cache (advanced). For LiteSpeed servers: LiteSpeed Cache (free, most powerful). For Nginx-based hosts: Nginx FastCGI Cache via your host's dashboard. Enable page caching and browser caching at minimum.
Images are typically the largest page elements and the easiest to fix. Install Imagify, ShortPixel, or Smush. all compress uploaded images automatically. Convert images to WebP format (Imagify handles this automatically). Set lazy loading for images below the fold (WordPress 5.5+ adds lazy loading natively). Avoid embedding full-resolution images where thumbnails suffice.
A CDN serves your static assets (images, CSS, JS) from servers geographically close to each visitor, reducing download latency. Cloudflare's free plan is the easiest starting point. install the Cloudflare plugin in WordPress and enable it. SiteGround and Hostinger both include free CDN in their plans. Kinsta and WP Engine use Cloudflare CDN built into the infrastructure.
Minification removes whitespace, comments, and unnecessary characters from CSS and JS files, reducing their file size. LiteSpeed Cache, W3 Total Cache, and Autoptimize all offer minification settings. Enable carefully. aggressive JS minification can break scripts. Test after enabling by checking all forms, sliders, and interactive elements still work.
Every active plugin adds PHP execution overhead. Audit your plugins: deactivate and delete any unused ones. Replace multiple single-purpose plugins with all-in-one solutions where possible. Use Query Monitor or Plugin Performance Profiler to identify which plugins are causing the most load time. 20–30 well-chosen plugins is fine; 60+ poorly-coded plugins will slow any site.
Heavy themes with excessive CSS and JS load on every page. Switch to a lightweight base theme: Astra (free version under 50KB), GeneratePress, Kadence, or Hello Elementor. Avoid themes with built-in sliders, counters, and animation libraries if you don't use them. They load their scripts regardless.
Over time, WordPress accumulates post revisions, auto-drafts, trashed items, and orphaned metadata that bloat your database. Install WP-Optimize or Advanced Database Cleaner to remove this overhead. Enable the setting to limit post revisions (add `define('WP_POST_REVISIONS', 5);` to wp-config.php). Run the optimizer monthly.
PHP 8.2 is significantly faster than PHP 7.x. Typically 15–25% faster execution for WordPress. Check your PHP version in your hosting dashboard (cPanel → PHP Version Manager, or Hostinger/SiteGround dashboards). Upgrade to PHP 8.2 (first test on a staging site to confirm plugin compatibility. most modern plugins fully support it).
Test your changes using Google PageSpeed Insights, GTmetrix, or WebPageTest after each optimisation to measure impact. Target: LCP (Largest Contentful Paint) under 2.5 seconds, CLS (Cumulative Layout Shift) under 0.1, and TTFB under 200ms. Set up ongoing monitoring with a free tool like UptimeRobot to catch any future regressions.