Abre cualquier informe de velocidad de una web lenta y encontrarás casi siempre al mismo culpable: las imágenes. Suponen de media más de la mitad del peso de una página, y una sola foto subida directamente desde el móvil puede pesar más que todo el resto de la web junta. La buena noticia es que optimizar imágenes en WordPress es una de las mejoras con resultados más inmediatos y visibles: no requiere tocar código, se nota en los tiempos de carga desde el primer día y Google la premia en sus Core Web Vitals. En esta guía completa vamos a ver todo el proceso en orden: elegir el formato adecuado (con WebP como protagonista), redimensionar y comprimir antes de subir, aprovechar lo que WordPress ya hace por ti, activar el lazy loading correctamente y escoger un plugin de optimización que automatice el trabajo. Al terminar tendrás un sistema, no un apaño puntual: cada imagen que subas a partir de ahora llegará ligera y en el formato correcto.
Por qué las imágenes hunden tu velocidad (y tu SEO)
Cuando alguien visita tu web, su navegador descarga cada imagen de la página. Si la portada carga 4 MB en fotos, un visitante con conexión móvil media necesitará varios segundos solo para verlas, con la página saltando mientras se colocan. Eso impacta en tres frentes:
- Experiencia: cada segundo extra de carga aumenta el porcentaje de gente que abandona sin esperar.
- SEO: los Core Web Vitals (sobre todo el LCP, que mide cuándo se pinta el elemento más grande, normalmente una imagen) forman parte de la evaluación de Google.
- Costes: más peso es más ancho de banda, más ocupación de disco en el hosting y copias de seguridad más lentas.
La regla mental que lo resume: ninguna imagen de contenido debería superar los 100-200 KB, y las decorativas deberían quedar muy por debajo. Con las técnicas de esta guía, es un objetivo perfectamente alcanzable sin pérdida de calidad apreciable.
Formatos de imagen: cuándo usar JPG, PNG, WebP y AVIF
Elegir bien el formato es la mitad de la batalla al optimizar imágenes en WordPress:
| Formato | Mejor uso | Peso relativo | Support |
|---|---|---|---|
| JPG | Fotografías | Referencia | Universal |
| PNG | Gráficos con transparencia, capturas nítidas | Alto | Universal |
| WebP | Sustituto moderno de ambos | 25-35 % menos que JPG | Todos los navegadores actuales |
| AVIF | El siguiente salto de compresión | Hasta 50 % menos que JPG | Muy amplio y creciendo |
| SVG | Logos e iconos vectoriales | Mínimo | Universal (subida bloqueada por defecto en WordPress) |
WebP es hoy la elección por defecto: comprime mejor que JPG, soporta transparencia como PNG y todos los navegadores modernos lo muestran sin problema. WordPress admite subir archivos WebP de forma nativa desde la versión 5.8, y desde la 6.5 también AVIF si el servidor lo soporta. AVIF comprime aún más, pero su generación es más lenta y el soporte en herramientas todavía es menor: como norma práctica en 2026, WebP para todo y AVIF si tu plugin de optimización lo genera automáticamente. Si quieres profundizar en las tripas de cada formato, la guía oficial de formatos de imagen de MDN es la referencia.
¿Tienes un puñado de JPG o PNG y quieres pasarlos a WebP ahora mismo, sin instalar nada? Usa nuestro conversor gratuito de imágenes a WebP: funciona en el navegador, sin registro, y te devuelve los archivos convertidos y listos para subir a la mediateca. Es la vía rápida perfecta para las imágenes nuevas de cada artículo; para convertir en bloque toda una mediateca ya existente, un plugin (los vemos más abajo) es más práctico.
Redimensionar antes de subir: el paso que casi todos se saltan
Una cámara o un móvil actual genera fotos de 4000 píxeles de ancho o más. Tu web probablemente no muestra nada a más de 1200-1920 píxeles. Subir el original significa almacenar y procesar un archivo varias veces más grande de lo que jamás se mostrará. Antes de subir, redimensiona:
- Imágenes de contenido (dentro de entradas): 1200 píxeles de ancho suele ser suficiente.
- Cabeceras y fondos a pantalla completa: 1920 pixels.
- Thumbnails and logos: the actual size at which they are displayed, or double if you want sharpness on retina screens.
Any editor works (even Paint or Preview), and conversion tools usually allow resizing in the same step. While you're at it, rename the file with descriptive words separated by hyphens (tarta-queso-sin-horno.webp better than IMG_4832.webp): the file name is another SEO signal, and it will make it easier to find the image in the media library.
Then, when inserting it, always fill in the alternative text: describes the image for screen readers and for Google Images. It's accessibility and SEO in a single field.
What WordPress already does for you (and what it doesn't)
When you upload an image, WordPress automatically generates several copies in different sizes (thumbnail, medium, large, plus those registered by your theme) and serves them with the attribute srcset, so a mobile downloads the small version and a large monitor downloads the full version. It also applies native lazy loading (loading="lazy") to images since version 5.5, and limits giant images uploaded to 2560 pixels.
What WordPress not does by default: aggressively compress, convert your old JPG and PNG to WebP, or optimize what you already have in the media library. That gap is what optimization tools and plugins cover.
Two nuances of lazy loading worth knowing:
- The main image seen immediately upon entry (the LCP image) not should have lazy loading: delaying it worsens the metric. WordPress tries to exclude the first image automatically, and good optimization plugins manage it even better.
- CSS backgrounds and sliders do not use native lazy loading; there, a plugin's implementation does contribute.
Plugins for optimizing images in WordPress: comparison
An optimization plugin automates all of the above: it compresses each image upon upload, converts to WebP/AVIF, bulk optimizes the existing media library, and serves the modern format only to compatible browsers. The four names that dominate the field:
- Imagify: from the WP Rocket team. Very clear interface, three compression levels, automatic WebP and AVIF, and a very good quality-weight balance. Free up to 20 MB per month; paid thereafter.
- ShortPixel: the favorite of advanced users for its value for money in volume (credits that don't expire). Excellent compression, WebP and AVIF, and a unique feature: PDF optimization.
- Smush: the most installed. Its free version compresses without quantity limits (with a 5 MB file size cap) and handles lazy loading and resizing well, but WebP conversion is reserved for the Pro version.
- EWWW Image Optimizer: the only one that can compress on your own server without relying on external services or fees. Free in its local mode, with WebP included. Ideal if you upload many images and want zero cost.
Which one to choose? For most: Imagify or ShortPixel if you want the best automatic result with WebP/AVIF included, EWWW if you prefer not to depend on credits, Smush if compressing is enough for you and you already use its ecosystem. And remember the layers rule: an image plugin coexists without problem with your cache plugin, because they do different jobs; in fact WP Rocket and Imagify expressly complement each other. These and more free utilities are gathered on our web page tools.
The complete method, step by step
Let's recap the entire workflow for optimizing images in WordPress, both new and legacy:
- Measure the starting point. Run your homepage through PageSpeed Insights and note the page weight and LCP.
- Install and configure an optimization plugin. Activate automatic compression on upload, WebP conversion, and maximum resizing (2560 px or less).
- Optimize the existing media library in bulk. Do it after a backup and during off-peak hours: these are thousands of operations.
- Adopt the habit for new content: resize, convert to WebP with the converter, rename with hyphens, and fill in the alternative text when inserting.
- Check lazy loading: active in general, excluding the main image of each template.
- Measure again. On websites with many photos, it's common to cut the total page weight in half or less.
If you also serve images from a CDN (many optimization and caching plugins include it), the visitor will download them from a nearby server, adding another boost in speed, especially for international audiences.
Frequently Asked Questions
Does compression not spoil the quality of my photos?
Well-adjusted "lossy" compression removes information that the eye doesn't perceive: at Imagify or ShortPixel's medium levels, the difference is indistinguishable on screen and the saving is around 60-80%. For artistic photography where every nuance matters, use "glossy" or lossless modes, which preserve more data in exchange for less saving. In any case, good plugins save the original and allow it to be restored.
What about browsers that don't support WebP?
In 2026, practically none in real use: Chrome, Firefox, Safari, and Edge have supported it for years. Even so, plugins that serve WebP do so with fallback mechanisms (the tag <picture> or server rules) that deliver the original JPG/PNG to any old client. There is no risk of a visitor seeing gaps instead of images.
Should I delete the original JPGs after converting to WebP?
If the plugin serves WebP dynamically, the originals remain the backup and the source for regeneration: keep them unless disk space is critical. If you convert manually before uploading (with the converter, for example), then upload only the WebP and you won't accumulate duplicates. Both are valid strategies; the key is not to mix them without criteria.
How much does optimizing images really improve speed?
It depends on the starting point, but it's the optimization with the greatest impact on visual websites: going from 2-4 MB photos to 80-150 KB WebP versions reduces page weight by 50-80% and directly advances LCP. In terms of effort-benefit, only page caching competes with it.
Conclusion
Optimizing images in WordPress is not a one-time task but a system with two fronts: cleaning up what you already have (bulk optimization of the media library with a plugin) and establishing a correct workflow for new images (resizing, converting to WebP, renaming, and describing each image before publishing it). The pieces are few and all accessible: WebP as the default format, an online converter for daily use, a plugin like Imagify, ShortPixel, or EWWW to automate, well-configured lazy loading, and before-and-after measurements to check progress. The result is visible to the naked eye: pages that load in a fraction of the time, Core Web Vitals metrics in green, and a more relaxed hosting. Start today with the simplest thing: convert the images of your next article to WebP and compare the weight. That first saving will give you the impetus to apply the complete system.
