Title: Optimazz – Website Optimization and Speedup
Author: Shipon Karmakar
Published: <strong>21 de julio de 2026</strong>
Last modified: 1 de octubre de 2026

---

Buscar plugins

![](https://ps.w.org/optimazz/assets/banner-772x250.png?rev=3617647)

![](https://ps.w.org/optimazz/assets/icon-256x256.png?rev=3617647)

# Optimazz – Website Optimization and Speedup

 Por [Shipon Karmakar](https://profiles.wordpress.org/shiponkarmakar/)

[Descargar](https://downloads.wordpress.org/plugin/optimazz.1.0.24.zip)

 * [Detalles](https://es.wordpress.org/plugins/optimazz/#description)
 * [Valoraciones](https://es.wordpress.org/plugins/optimazz/#reviews)
 *  [Instalación](https://es.wordpress.org/plugins/optimazz/#installation)
 * [Desarrollo](https://es.wordpress.org/plugins/optimazz/#developers)

 [Soporte](https://wordpress.org/support/plugin/optimazz/)

## Descripción

Optimazz is an all-in-one performance suite that applies the optimizations with 
the biggest impact on Core Web Vitals — automatically and safely. Every module is
opt-in and reversible, and Optimazz never overwrites another caching plugin’s files.

**Modules included:**

 * **Page Cache** — serve static HTML instead of running PHP on every request, with
   smart exclusions (logged-in users, carts, query strings), automatic purging on
   content changes, and a cron-based cache preloader so visitors never hit a cold
   page.
 * **JavaScript** — defer scripts and delay them until the first user interaction
   to cut Total Blocking Time, with an exclusion list.
 * **CSS** — minify, combine, and load CSS asynchronously to remove render-blocking
   stylesheets.
 * **Image Optimization** — lazy-load images and iframes, add missing dimensions
   to prevent layout shift, generate and serve WebP/AVIF, bulk-compress your existing
   library, convert opaque PNGs to JPEG, and replace YouTube embeds with a click-
   to-load preview.
 * **Fonts** — add `font-display: swap`, preconnect to font hosts, and preload font
   files.
 * **Database** — clean revisions, auto-drafts, trashed posts, spam/trashed comments
   and expired transients, optimize tables, and schedule automatic cleanups.
 * **Heartbeat** — reduce or disable the WordPress Heartbeat API per context to 
   lower server load.
 * **Tweaks** — disable emojis, embeds, dashicons, query strings, XML-RPC and pingbacks,
   and add DNS-prefetch / preconnect hints.
 * **CDN** — rewrite static asset URLs to your CDN hostname.

A live performance score on the dashboard shows which optimizations are active and
your biggest remaining win.

### Build process and source code

The admin interface is a React application. The human-readable source lives in the`
src/` directory shipped inside the plugin (`src/index.js` and `src/index.scss`),
and the compiled, minified output lives in `build/`.

To regenerate the compiled files from source:

 1. Install dependencies: `npm install`
 2. Build: `npm run build`

This uses the official `@wordpress/scripts` (webpack) toolchain — no custom or hidden
build configuration. All source and build tooling are included in the plugin; nothing
is obfuscated.

### External services

Optimazz does not require any external service to function, and it works entirely
on your own server by default. Two optional, admin-controlled features can reference
third-party hosts:

 1. **Google Fonts optimization (Fonts module).** If — and only if — your theme or 
    another plugin already loads Google Fonts, and you enable the Fonts module, Optimazz
    adds `preconnect` resource hints to `fonts.googleapis.com` and `fonts.gstatic.com`
    and can add `display=swap` to the existing font URL. Optimazz does not add Google
    Fonts to a site that isn’t already using them, and it does not send any personal
    or site data — a `preconnect` is only a browser hint to open a connection earlier.
    The fonts themselves are requested by the visitor’s browser from Google, exactly
    as they were before the plugin, under Google’s terms: https://policies.google.com/
    terms and privacy policy: https://policies.google.com/privacy
 2. **CDN rewriting (CDN module).** If you enable the CDN module and enter a CDN hostname,
    Optimazz rewrites the URLs of your own static assets (CSS, JS, images) to that 
    hostname so visitors’ browsers load them from your CDN. The CDN is a service you
    choose and configure; Optimazz sends no data to it itself and is not affiliated
    with any CDN provider. Consult your chosen CDN’s own terms and privacy policy.

Both features are off by default and take effect only after you explicitly enable
them.

## Capturas

[⌊Dashboard — live performance score, cache statistics, quick actions, and per-module
on/off switches.⌉⌊Dashboard — live performance score, cache statistics, quick actions,
and per-module on/off switches.⌉[

Dashboard — live performance score, cache statistics, quick actions, and per-module
on/off switches.

[⌊Page Cache — serve static HTML instead of running PHP, with separate mobile caching.⌉⌊
Page Cache — serve static HTML instead of running PHP, with separate mobile caching
.⌉[

Page Cache — serve static HTML instead of running PHP, with separate mobile caching.

[⌊File Optimization — defer and delay JavaScript, and minify, combine and async-
load CSS.⌉⌊File Optimization — defer and delay JavaScript, and minify, combine and
async-load CSS.⌉[

File Optimization — defer and delay JavaScript, and minify, combine and async-load
CSS.

[⌊Media — lazy-load images and iframes, add missing dimensions, and convert to WebP/
AVIF.⌉⌊Media — lazy-load images and iframes, add missing dimensions, and convert
to WebP/AVIF.⌉[

Media — lazy-load images and iframes, add missing dimensions, and convert to WebP/
AVIF.

[⌊Fonts — font-display swap, preconnect to font hosts, and preload font files.⌉⌊
Fonts — font-display swap, preconnect to font hosts, and preload font files.⌉[

Fonts — font-display swap, preconnect to font hosts, and preload font files.

[⌊Preload — warm the cache automatically so visitors never hit a cold page.⌉⌊Preload—
warm the cache automatically so visitors never hit a cold page.⌉[

Preload — warm the cache automatically so visitors never hit a cold page.

[⌊Advanced Rules — fine-tune caching with URL, cookie, and user-agent exclusions.⌉⌊
Advanced Rules — fine-tune caching with URL, cookie, and user-agent exclusions.⌉[

Advanced Rules — fine-tune caching with URL, cookie, and user-agent exclusions.

[⌊Database — clean revisions, drafts, spam, and transients, and optimize tables.⌉⌊
Database — clean revisions, drafts, spam, and transients, and optimize tables.⌉[

Database — clean revisions, drafts, spam, and transients, and optimize tables.

[⌊Heartbeat — reduce or disable the WordPress Heartbeat API to lower server load.⌉⌊
Heartbeat — reduce or disable the WordPress Heartbeat API to lower server load.⌉[

Heartbeat — reduce or disable the WordPress Heartbeat API to lower server load.

[⌊Tweaks — disable emojis, embeds, query strings, XML-RPC, and other front-end bloat.⌉⌊
Tweaks — disable emojis, embeds, query strings, XML-RPC, and other front-end bloat
.⌉[

Tweaks — disable emojis, embeds, query strings, XML-RPC, and other front-end bloat.

[⌊CDN — rewrite static asset URLs to your CDN hostname.⌉⌊CDN — rewrite static asset
URLs to your CDN hostname.⌉[

CDN — rewrite static asset URLs to your CDN hostname.

[⌊Tools — import, export, and reset your configuration.⌉⌊Tools — import, export,
and reset your configuration.⌉[

Tools — import, export, and reset your configuration.

## Instalación

 1. Upload the `optimazz` folder to `/wp-content/plugins/`, or install it from the 
    Plugins screen.
 2. Activate the plugin through the **Plugins** menu in WordPress.
 3. Open **Optimazz** in the admin menu and enable the modules you want.

## FAQ

### Does Optimazz work alongside another caching plugin?

Optimazz will not overwrite another caching plugin’s `advanced-cache.php` drop-in.
To use Optimazz page caching, deactivate any other page-caching plugin first. The
other (non-caching) modules work alongside most plugins.

### Will page caching work on my host?

Page caching needs `WP_CACHE` to be defined, which Optimazz adds to `wp-config.php`
automatically. If `wp-config.php` is not writable, Optimazz shows a notice with 
the line to add manually.

### Is it safe to delay JavaScript?

Delay-until-interaction is the biggest speed win but can affect scripts that must
run before interaction. Start with «Delay» on and «Delay all» off, then add any 
problematic script keywords to the exclusion list.

### Does converting PNG to JPEG lose my originals?

Only opaque PNGs are converted, the original is optionally backed up to `uploads/
optimazz-backup`, and the conversion is rolled back if anything fails.

### Does the plugin phone home or collect data?

No. Optimazz does not track users, register accounts, or send any of your site’s
or visitors’ data to Optimazz servers. See the «External services» section for the
only optional third-party hints the plugin can add.

### Why does the plugin add inline <script> and <style> tags to my pages?

Those small inline fragments (the delay-JavaScript loader, critical/async CSS, the
lazy-load helper and LCP preload hints) are the actual optimization output that 
Optimazz writes into your front-end HTML. They are the product of the plugin’s work,
not the plugin’s own asset loading — a delay-until-interaction loader cannot be 
enqueued as an external file. The admin interface and all of the plugin’s own assets
are loaded normally through the WordPress enqueue functions.

## Reseñas

![](https://secure.gravatar.com/avatar/6c784bbfe8dd1a612003efed692188c94d6443743d6f1b87cf55a0af56045260?
s=60&d=retro&r=g)

### 󠀁[Great WordPress Performance Plugin](https://wordpress.org/support/topic/great-wordpress-performance-plugin-2/)󠁿

 [Jahid Hasan](https://profiles.wordpress.org/jahidzendforce/) 4 de septiembre de
2026

Optimazz is a solid all-in-one optimization plugin. The caching, CSS/JS optimization,
image optimization, and database cleanup features are easy to use. A promising plugin
that keeps getting better with regular updates.

![](https://secure.gravatar.com/avatar/3b228d2629f1b95acd18329986f40db27d3fb7af367e91e55bf994edfe9d07fc?
s=60&d=retro&r=g)

### 󠀁[Optimazz – Everything in one](https://wordpress.org/support/topic/optimazz-everything-in-box/)󠁿

 [solhere](https://profiles.wordpress.org/solhere/) 1 de septiembre de 2026

When I searched a reliable plugin for my site optimization I found Optimazz and 
installed and explored. I will say it was a best optimization plugin for wordpress.

![](https://secure.gravatar.com/avatar/083451e4c528f742db16bda00e15b302d6be11ff082187ac4e22abf2a2f7cc98?
s=60&d=retro&r=g)

### 󠀁[Excellent Performance Plugin – Optimazz is Amazing!](https://wordpress.org/support/topic/excellent-performance-plugin-optimazz-is-amazing/)󠁿

 [farhadsoft](https://profiles.wordpress.org/farhad123/) 25 de julio de 2026

Optimazz is amazing! I’ve used WP Rocket and FlyingPress for many of my client projects,
but recently I tried Optimazz on one of my latest projects, and I’m really impressed.
I also tested the same project with both WP Rocket and Optimazz. Surprisingly, Optimazz
delivered around 5% better performance in my tests, which exceeded my expectations.
The plugin is lightweight, easy to configure, and delivers excellent performance
improvements without unnecessary complexity. Everything worked smoothly, and the
website feels noticeably faster. Optimazz has definitely become one of my go-to 
performance plugins, and I’ll be using it for future projects as well.

![](https://secure.gravatar.com/avatar/3626d9316f5e9ddb3f01388e8212dc9e7f602fb911940da95ab7f36a4ed29060?
s=60&d=retro&r=g)

### 󠀁[Excellent Website Optimization Plugin](https://wordpress.org/support/topic/excellent-website-optimization-plugin/)󠁿

 [JoypurHost](https://profiles.wordpress.org/joypurhost/) 25 de julio de 2026

I've been using Optimazz on several WordPress websites, and the results have been
impressive. The plugin is easy to configure, improves website performance, and helps
reduce page load times without unnecessary complexity. I especially appreciate how
lightweight it is and how smoothly it works alongside other plugins. The optimization
features are practical, and the overall user experience is excellent. Thank you 
to the developer for creating such a useful plugin. Looking forward to future updates
and new features. Highly recommended!

 [ Leer todas las 4 reseñas ](https://wordpress.org/support/plugin/optimazz/reviews/)

## Colaboradores y desarrolladores

«Optimazz – Website Optimization and Speedup» es un software de código abierto. 
Las siguientes personas han colaborado con este plugin.

Colaboradores

 *   [ Shipon Karmakar ](https://profiles.wordpress.org/shiponkarmakar/)

«Optimazz – Website Optimization and Speedup» está traducido en 1 idioma. Gracias
a [los traductores](https://translate.wordpress.org/projects/wp-plugins/optimazz/contributors)
por sus contribuciones.

[Traduce «Optimazz – Website Optimization and Speedup» a tu idioma.](https://translate.wordpress.org/projects/wp-plugins/optimazz)

### ¿Interesado en el desarrollo?

[Revisa el código](https://plugins.trac.wordpress.org/browser/optimazz/) , echa 
un vistazo al [repositorio SVN](https://plugins.svn.wordpress.org/optimazz/) o suscríbete
al [registro de desarrollo](https://plugins.trac.wordpress.org/log/optimazz/) por
[RSS](https://plugins.trac.wordpress.org/log/optimazz/?limit=100&mode=stop_on_copy&format=rss).

## Registro de cambios

#### 1.0.24

 * Fixed: the automatic preload (after saving settings, and the scheduled one) only
   warmed the first 50 addresses, so on bigger sites it covered far fewer pages 
   than a manual preload. It now warms the whole site in short background chunks—
   each continues where the last stopped, and only one runs at a time — so it never
   overloads the server or hits the PHP time limit.
 * Improved: preloading is much faster — desktop and mobile copies are warmed at
   the same time, a manual preload warms several pages per step, and the page list
   is built once per run instead of on every step.
 * Improved: the preload explains what it is warming, e.g. «Found 74 pages to warm:
   10 pages, 11 posts, 18 products, 12 category and tag pages» — the total includes
   posts, products and archive pages, not only Pages. Page-builder template libraries(
   Elementor, Beaver Builder, Divi, Bricks …), WooCommerce cart / checkout / account
   pages and anything in «Never cache these URLs» are no longer in the list, since
   visitors never get them from the cache.
 * Fixed: the preloader reported pages as «warmed» even when none were saved to 
   the cache (e.g. «Warmed 114 / 121» while Cached pages stayed at 0), with no hint
   why. It now counts only pages that really reached the cache («· 98 cached · 16
   not cached») — counted per page (desktop and mobile copies of one page count 
   once), so it matches the «Cached pages» card, and when pages are not being cached
   it stops after a few and explains the exact reason and fix: another caching plugin
   owns advanced-cache.php, the drop-in or WP_CACHE is missing, a server or CDN 
   cache (LiteSpeed, Cloudflare, Varnish …) answers before WordPress, a plugin sets
   DONOTCACHEPAGE, pages return an error status, the cache folder is not writable,
   or your exclusion rules match.
 * Fixed: on sites behind a proxy, load balancer or Cloudflare (HTTPS ends at the
   proxy), cached pages were saved under an http address and never found again for
   https visitors. The real scheme is now read from X-Forwarded-Proto / CF-Visitor.
 * New: if another caching plugin (WP Rocket, Seraphinite Accelerator, LiteSpeed
   Cache …) controls the cache drop-in while Optimazz page cache is on, a notice
   now appears on every admin screen — naming the plugin, with one-click «Deactivate
   it and use Optimazz» and «Use Optimazz for caching» buttons, or «Keep the other
   plugin» to hide it. Before, the Optimazz page cache silently stayed inactive 
   unless you opened its Cache health panel.
 * Improved: conflict detection now also recognises Seraphinite Accelerator, FlyingPress,
   WP-Optimize and NitroPack, and cache plugins installed under a renamed folder(
   e.g. a GitHub download).
 * Improved: «Cache lifespan» and «Auto-preload» can now be changed right from the
   Dashboard (a dropdown on each row), and the preload row shows when the next run
   is due.
 * Fixed: scheduled auto-preload often never ran on well-cached sites. WordPress
   only runs scheduled tasks when it loads, but cached pages are served without 
   loading WordPress, so the preload quietly went overdue. When a preload is due,
   a cached page view now wakes WordPress’s scheduler in the background (after the
   page has been sent, at most once a minute).
 * Fixed: the dashboard showed an overdue preload as «in 3 hours»; it now says «
   due now», and a new «Last auto-preload» line shows when it last ran and how many
   pages it warmed (or that a firewall blocked it).
 * New: choose how often the automatic preload runs — every hour, twice a day or
   once a day (Preload settings). Turning page caching off now also clears the preload
   schedule, and a notice explains when WP-Cron is disabled on the site.
 * Fixed: switching a module on or off (or using Undo, Reset, or the post-update
   refresh) cleared the whole page cache and then left it empty, so the site ran
   uncached — and slow — until each page happened to get a visitor or the twice-
   daily preload ran. The cache is now rebuilt automatically straight after (when
   page cache and preloading are on).
 * Fixed: switching Optimazz page caching off, or deactivating Optimazz, turned 
   off WP_CACHE even when another caching plugin (e.g. WP Rocket) owned the cache
   drop-in, which silently disabled that plugin’s page cache. WP_CACHE is now only
   turned off when the drop-in was Optimazz’s own.
 * Fixed: cache preloading stopped with a 403 error when a firewall such as the 
   6G/7G rules in All-In-One Security was enabled. The preloader identified itself
   as «Optimazz-Preloader», and these firewalls block any visitor whose user-agent
   contains the word «loader». It now identifies as «Optimazz-CacheWarmer» in the
   standard crawler format, which those rules allow. The user-agent can be changed
   with the new `optimazz_preload_user_agent` filter.

#### 1.0.23

 * Fixed: with WebP/AVIF serving on, some images (often the site logo) showed as
   broken on HTTPS sites whose content still used old http:// image addresses. Browsers
   upgrade a plain http:// image to https:// automatically, but block an http://
   image inside a source — and never fall back. Next-gen image sources now always
   use https:// on HTTPS pages.
 * Fixed: in responsive images, a size without a WebP/AVIF copy could be offered
   to the browser and show as broken; only sizes whose next-gen file exists are 
   now listed.
 * Fixed: tidier image markup — no attributes added after a self-closing slash, 
   and no duplicate decoding/fetchpriority attributes.
 * New: Google Fonts optimization (Fonts module). Page builders such as Elementor
   load every Google Font family as a separate request, each with every weight from
   100 to 900 plus italics. Optimazz now merges them into a single request and loads
   only the weights and styles your pages actually use (weights 400 and 700 are 
   always kept). On a typical Elementor site this turns three render-blocking requests
   into one and cuts the font CSS by more than half (measured: 170 KB down to 64
   KB). Both options are on by default and can be switched off in the Fonts settings;
   requests that subset by text are never changed.
 * Improved: the build tooling (`package.json`) ships with the plugin again, so 
   the admin interface can be rebuilt from the included source as described under«
   Build process and source code».
 * Fixed: with the CDN module on, CSS minify/combine, WebP delivery and missing-
   image-dimension fixes were silently skipped, because the CDN rewrite ran before
   the other optimizations and they could no longer recognise your own files. The
   CDN rewrite now runs last, on the finished page.
 * Improved: when the update safety check switches Safe Mode on to protect a site,
   it now keeps re-checking and switches Safe Mode back off by itself as soon as
   pages load correctly again, restoring full optimization (CSS combine, async CSS
   and JavaScript delay). Previously Safe Mode stayed on until someone turned it
   off manually, so a site could quietly run slower for a long time after a temporary
   problem. If pages break again within a day of being restored, Safe Mode stays
   on and the admin decides. Safe Mode that you switch on yourself is never changed
   automatically.
 * Fixed: the update safety check now also recognises stylesheets served from your
   CDN hostname (when the CDN module is on), so a page that loads unstyled through
   the CDN is detected instead of being reported as healthy.
 * Fixed: the «Optimazz Safe Mode is on» notice no longer lingers after Safe Mode
   was switched off via Undo last change, Reset or Import.
 * Fixed: uninstalling Optimazz now removes all of its data, including the version
   marker, the safety-check state and its scheduled check, and the cached font-weight
   data.

#### 1.0.22

 * Fixed: on some hosts (certain LiteSpeed/WAF setups and managed hosts) pages loaded
   unstyled because the server does not serve — or routinely deletes — files under`
   wp-content/cache/`, which is where Optimazz kept its generated CSS. Since the
   page HTML references those files by name, a page that could not load them rendered
   without styling. Optimazz now stores generated CSS under `wp-content/uploads/
   optimazz/` instead — the standard, always-served, persistent location page builders
   also use — so the stylesheets load reliably and are never wiped out from under
   a cached page. On update the page cache is refreshed automatically so pages pick
   up the new location with no manual step.
 * New: update safety guard. Shortly after the plugin updates, Optimazz quietly 
   checks its own front page to confirm the optimized CSS actually loads. If it 
   finds pages rendering unstyled — their generated stylesheets returning 404, usually
   because an external server or CDN cache is still serving old pages — it automatically
   switches on Safe Mode to keep the site working (pausing the risky CSS/JS transforms
   without changing your saved settings, so pages fall back to their original stylesheets)
   and shows an admin notice explaining what happened. After you clear your server/
   CDN cache and switch Safe Mode off from Tools, Optimazz re-checks and re-protects
   the site if anything is still broken — so an update can no longer leave a site
   visibly broken.

#### 1.0.21

 * Fixed: after updating, a site whose page cache was already populated could keep
   serving pages that loaded unstyled, until the cache was purged by hand. A plugin
   update never clears the page cache, so any HTML cached by an earlier version —
   still pointing at combined CSS/JS files that an older purge had removed — stayed
   in place and rendered without styling. Optimazz now clears the page cache automatically
   once, the first time it runs after an update, and re-aligns its caching drop-
   in; the generated CSS/JS assets are kept, so pages come back fully styled on 
   the next visit with no manual purge needed. This completes the 1.0.20 fix for
   existing installs.

#### 1.0.20

 * Fixed: pages could intermittently load completely unstyled when CSS minify/combine
   was on together with page caching (or a server-level cache such as LiteSpeed).
   Optimazz names each generated CSS/JS file by a content hash and embeds those 
   filenames in the cached HTML — but purging the page cache also deleted those 
   generated files, so any HTML still held in a cache (Optimazz’s own, a CDN’s, 
   or the server’s) pointed at stylesheets that had been removed, returning 404 
   and rendering the page without styling until they regenerated. Purging the page
   cache now preserves the hashed CSS/JS assets (they are self-invalidating — a 
   source change produces a new filename), keeping the HTML and its stylesheets 
   consistent.

#### 1.0.19

 * Fixed: page caching could silently stop working after a plugin update or a manual
   re-upload, making the whole site slow (every request fell back to full PHP). 
   The advanced-cache.php drop-in embeds the path to the cache engine, and if the
   plugin folder was moved or recreated by the update, that path went stale — but
   Optimazz still recognised the drop-in as its own and never repaired it. Optimazz
   now detects a stale drop-in and rewrites it with the correct path automatically,
   and the drop-in itself falls back to the standard plugin location so caching 
   keeps working immediately. If you were affected, the cache heals itself on the
   first page view after updating.
 * Improved: the per-request cache readiness check no longer spins up the WordPress
   filesystem API just to read its own drop-in, removing needless overhead on every
   uncached request.

#### 1.0.18

 * New: **Safe Mode** (Tools screen). If a theme or page builder looks broken after
   you enable optimization, one toggle pauses just the riskiest transforms — combine
   CSS, async CSS, remove-block-CSS and JavaScript delay — while keeping page cache,
   minify, defer and lazy-load running. It changes nothing in your saved settings;
   those optimizations simply pause until you switch Safe Mode off, so recovery 
   is instant and reversible. Filterable via `optimazz_safe_mode` so a host can 
   force it on during an incident.
 * New: **Undo last change** (Tools screen). Optimazz now keeps a one-step backup
   of your settings taken before every save, reset or Safe Mode toggle, so a single
   click restores the previous state — and undo is itself reversible (press it again
   to redo).

#### Older versions

The complete history (1.0.0 onward) is in [changelog.txt](https://plugins.svn.wordpress.org/optimazz/trunk/changelog.txt),
included with the plugin.

## Meta

 *  Versión **1.0.24**
 *  Última actualización **hace 6 días**
 *  Instalaciones activas **50+**
 *  Versión de WordPress ** 6.0 o superior **
 *  Probado hasta **7.1.3**
 *  Versión de PHP ** 7.4 o superior **
 *  Idiomas
 * [English (US)](https://wordpress.org/plugins/optimazz/) y [Korean](https://ko.wordpress.org/plugins/optimazz/).
 *  [Traducir a tu idioma](https://translate.wordpress.org/projects/wp-plugins/optimazz)
 * Etiquetas:
 * [cache](https://es.wordpress.org/plugins/tags/cache/)[lazy load](https://es.wordpress.org/plugins/tags/lazy-load/)
   [optimization](https://es.wordpress.org/plugins/tags/optimization/)[performance](https://es.wordpress.org/plugins/tags/performance/)
   [webp](https://es.wordpress.org/plugins/tags/webp/)
 *  [Vista avanzada](https://es.wordpress.org/plugins/optimazz/advanced/)

## Valoraciones

 5 de 5 estrellas.

 *  [  4 valoraciones de 5 estrellas     ](https://wordpress.org/support/plugin/optimazz/reviews/?filter=5)
 *  [  0 valoraciones de 4 estrellas     ](https://wordpress.org/support/plugin/optimazz/reviews/?filter=4)
 *  [  0 valoraciones de 3 estrellas     ](https://wordpress.org/support/plugin/optimazz/reviews/?filter=3)
 *  [  0 valoraciones de 2 estrellas     ](https://wordpress.org/support/plugin/optimazz/reviews/?filter=2)
 *  [  0 valoraciones de 1 estrellas     ](https://wordpress.org/support/plugin/optimazz/reviews/?filter=1)

[Tu valoración](https://wordpress.org/support/plugin/optimazz/reviews/#new-post)

[Ver todas las reseñas](https://wordpress.org/support/plugin/optimazz/reviews/)

## Colaboradores

 *   [ Shipon Karmakar ](https://profiles.wordpress.org/shiponkarmakar/)

## Soporte

¿Tienes algo que decir? ¿Necesitas ayuda?

 [Ver el foro de soporte](https://wordpress.org/support/plugin/optimazz/)