10Web Booster – Website speed optimization, Cache & Page Speed optimizer

Descripción

10Web Booster es el complemento de optimización de velocidad para mejorar el rendimiento general de cualquier sitio web. 10Web Booster quiere que se concentre y prospere en los aspectos creativos de su sitio web de WordPress permitiéndonos concentrarnos en la optimización del rendimiento de WordPress.

Obtenga una puntuación de PageSpeed de más de 90 y apruebe Core Web Vitals automáticamente. Clasifique más alto en Google, aumente las conversiones y haga crecer su negocio.

Enlaces útiles:

10Web Booster

Are you looking for a WordPress page speed plugin that’ll automatically speed up your WordPress site? Then 10Web Booster is exactly website speed optimizer you’re looking for!
Our WordPress performance plugin will transform your website in no time, enhancing the visitors’ user experience, SEO, engagement, and conversion rates.

10Web Booster funciona en versiones de escritorio y móviles de páginas web de cualquier complejidad. Optimice las páginas de su sitio web, experimente con todos los niveles que ofrecemos y obtenga resultados con el mejor complemento de velocidad de WordPress del mercado.

Consulte la extensa lista de características de 10Web Booster a continuación y eche un vistazo más detallado a todo lo que ofrecemos.

Beneficios

  • PageSpeed 90+ automatizado
  • Core Web Vitals optimizados
  • Mejor posicionamiento en buscadores
  • Incremento de hasta un 7% en las conversiones
  • Impulso de hasta un 40% en el compromiso de los visitantes
  • Incremento del compromiso del tráfico móvil de hasta un 53%

What’s in it

Optimización de la página de inicio + 5 páginas , imágenes incrustadas incluidas
10Web Booster es posible gracias a docenas de optimizaciones técnicas:

Caché de página

Una caché es un espacio de almacenamiento a corto plazo de rápida recuperación donde se guardan copias de los datos y recursos a los que se ha accedido recientemente. Una caché acelera significativamente la velocidad y el rendimiento de la página descargando de la fuente estos datos a los que se accede con frecuencia, creando una copia de estos recursos y guardándolos temporalmente en un espacio de almacenamiento de más fácil acceso desde el que se puede acceder a los datos más rápidamente una vez que el visitante regresa. Este espacio a corto plazo puede ser un navegador o un servidor web o incluso el servidor web original, que también guarda copias en distintos formatos de sus recursos. Cuando usted actualiza los datos de su sitio web, las copias guardadas también se revisan y actualizan.

10Web Booster utiliza varias técnicas de caché, como la caché de páginas para HTML, la caché de archivos, la invalidación inteligente de la caché, la caché consciente de la sesión y del navegador y la caché consciente del dispositivo y de las cookies.

Page cache takes care of dynamic pages. In WordPress, dynamic pages are written in the PHP backend language, which require a great deal of time to generate, when compared to the generation time of traditional static web pages in plain HTML. Page cache creates and stores copies of dynamic pages in the format of static files, making their retrieval as quick as possible. When a visitor enters your site, this «static» copy of your page is immediately loaded from the cache instead of your hosting.

La caché de archivos, o caché de recursos, por otro lado, permite almacenar los scripts y estilos creados minimizados y comprimidos. Este proceso también acelera la velocidad y rendimiento de página.

10Web Booster Pro emplea el backend o almacenamiento en caché del servidor y, a través de NGINX FastCGI Cache, almacena en caché una gran variedad de recursos, desde páginas a feeds o redirecciones 301 en subdominios. De esta forma se obtiene una velocidad de página y recuperación lo más rápida posible.

CSS & Minificación de HTML& Compresión

La minificación y fusión de CSS y HTML es el procedimiento de reducir el tamaño del archivo en un par de bytes. La importancia de esto se deriva del hecho de que los archivos más grandes requieren más recursos, lo que puede ralentizar el tiempo de carga del sitio web.

Minificación y Comprensión JS

La compresión de largos códigos JS algorítmicos es una práctica estándar. La compresión del código JS, es decir, la eliminación de todos los espacios adicionales, comentarios y otros componentes que hacen que el código sea legible y comprensible, reduce el tiempo de descarga de JavaScript, mejorando directamente la velocidad de WordPress. Combinando scripts JS, también podemos minimizar los archivos, reduciendo aún más el tiempo de ejecución.

Optimización de imagen

Image optimization leans on minimizing file size through image compression while simultaneously preserving image quality. 10Web’s image optimization achieves that and more. Through WebP compression, container-specific image resizing, and preloading of images, images can be optimized and loaded within seconds.

Container-specific image resizing finds or generates copies of images in various sizes. It then uses these differently sized copies of images on different-sized screens. This technique reduces valuable seconds of image load time and guarantees that you do not sacrifice quality for page speed.
Preloading images also significantly reduces page load time while providing your visitors with a seamless user experience. Preloading images means recovering images prior to visitor interaction. This method does make sense for certain cases – and not for all types of image, like mouseover images or slide show images.

Diferir la ejecución de JS y CSS

Having content that’s immediately visible when a user opens your website is only possible with file load optimization through prioritization of important CSS and deferral of JavaScript. That’s how 10Web booster ensures a 90+ page speed score as the best WordPress speed plugin.

Los archivos Javascript pueden causar una grave reducción de la velocidad de carga de la página. Esto es especialmente cierto en el caso de archivos JavaScript de terceros que están mal creados. Los archivos JavaScript de terceros incluyen widgets, rastreadores, analíticas, anuncios, sociales, chats, botones multimedia, ventanas emergentes y otros archivos incrustados directamente en su sitio. Estos archivos JavaScript pueden reducir la velocidad de carga de su página, por lo que primero deben localizarse y luego dividirse en archivos JavaScript críticos y no críticos. Los que no son críticos deben retrasarse y activarse sólo cuando un visitante interactúe con la página web.

CSS crítico

Downloading complete CSS files hinder the perceived speed of your WordPress website. After the user visits the webpages, the minimum-necessary stylesheets for the proper rendering of the webpage’s visible content are loaded, while the rest is served per need. Critical CSS doesn’t block page rendering and assists in passing the Core Web Vitals. 10Web Booster’s superiority in the case of critical CSS generation is due to its algorithms which programmatically parse through your web page and collect all the CSS rules used on that page. 10Web Booster guarantees that all stylesheets for critical CSS are present and unaffected. It also ensures that rule duplicates are deleted and that styles are structured to improve performance. 10Web Booster uses the critical CSS generation technique on five different screen sizes, from mobile to desktop to deliver the most effective page speed optimize in the market.

Carga diferida de iFrame y Video

Las imágenes son uno de los mayores recursos de una página que arrastran su velocidad. Mediante la técnica de carga lenta de imágenes, puede retrasar el proceso de carga de todas las imágenes de su página, excepto las que estén a la vista de los visitantes del sitio web. Este método ahorra importantes segundos de tiempo de carga y mejora drásticamente todos los valores vitales del núcleo de la web. 10Web Booster garantiza que sus algoritmos de carga lenta funcionan perfectamente y no entran en conflicto con temas y plugins. 10Web Booster también carga lentamente las imágenes de fondo.

Cambio de fuentes

La reducción y optimización de la forma en que se cargan las fuentes web podría ayudar potencialmente a superar la evaluación Core Web Vitals y, por tanto, beneficiar su clasificación en Google.Las fuentes personalizadas requieren recursos adicionales para cargarse y sólo entonces su página muestra la fuente elegida a mano y, por supuesto, esto lleva tiempo y añade los tan temidos milisegundos a la velocidad de su página. 10Web Booster añade font-display: swap. Esta técnica muestra primero una fuente genérica, con lo que su página se carga inmediatamente, y luego intercambia la fuente predeterminada con su fuente elegida a mano una vez que su estilo de fuente original está configurado. Este método de intercambio reduce el tiempo de carga de la página y garantiza que se eviten los problemas FOUT o Flash de texto sin estilo y FOIT o Flash de texto invisible.

Conversión de formato de imagen a WebP

Images take up website resources and unfortunately cannot be avoided. There are ways to reduce their large size. Conversion to different formats is one solution. Conversion to JPEG or PNG was the traditional method. There is another, a newer player which produces better results. Google’s WebP compression can reduce file size, on average, 25-34% smaller than a comparable JPEG image and 26% smaller than a comparable PNG image. This significant reduction in size, substantially impacts and improves page speed.

iFrame and Video Lazy load

Los iframes y los videos tienen un tamaño aún mayor que las imágenes, así que imagine su impacto en la velocidad de su página. Mediante la carga lenta de iframes y videos, nos aseguramos de que el contenido que aún no está a la vista directa de su visitante no entre en conflicto con la velocidad de su página. La carga de estos elementos se retrasa hasta que su usuario se desplaza hacia abajo. Al igual que con la carga retardada de imágenes, la carga retardada de iframes y videos mejora todas las Core Web Vitals.

Redimensionamiento de imágenes específico para cada contenedor

The container-specific image resizing method involves identifying images on your page and creating different-sized duplicates of these images. The differently sized images are then used for differently sized screens. Small-screen devices receive the small-sized images, loading them at the optimal speed possible. Medium-sized screens load medium-sized images, loading images at the fastest possible speed without sacrificing image quality. Large-sized screens, likewise, load large-sized images, ensuring the best quality and the best possible speed. Therefore, with the 10Web Booster, instead of forcing your website to load an enormous image when the user is only looking for a thumbnail, you’ll have a container-specific image at your disposal.

10Web Booster Pro

Optimización de la vista pública completa de toda la web y todas las imágenes

Optimización de la administración

Modos de optimización de velocidad

Cuando comienza la optimización automatizada de su página de inicio, probamos todos y cada uno de los 4 modos. En consecuencia, comparamos los resultados y, como se presume, el modo que logró la puntuación más alta y, a la vez, impidió que su sitio web se rompiera, se establecerá como predeterminado.

Puede elegir cualquiera de los cuatro niveles siguientes y gestionar los niveles para cada página individualmente desde la pestaña Reglas personalizadas de su panel de control de 10Web para proporcionar. Proporcionamos el mejor optimizador de velocidad de página a cualquier sitio web WordPress, en función de las necesidades.

  • Modo Estándar:: utiliza diferentes técnicas de optimización de velocidad estándar.
  • Modo Equilibrado:: todas las técnicas de optimización en Modo Estándar + CSS crítico
  • Modo Fuerte: – Todas las técnicas de optimización en Modo Estándar + retardo JS.
  • Modo Extremo: – Todas las técnicas de optimización del Modo Equilibrado + JS Delay.

IMPORTANTE:

Si cree que encontró un error en 10Web Booster o tiene algún problema o pregunta sobre el complemento, por favor consulte el Foro de asistencia en nuestra página web.

Instalación

Gracias por su interés en 10Web Booster.

Installing via WordPress
Follow the steps below to install 10Web Booster Plugin to your website.
Log-in to your WordPress administrator panel.
Select Plugins page from toolbar menu, click Add New.
Search for 10Web Boosterin the right-top search bar if you want to download the Free version or click Upload Plugin button > “Choose file” (“Browse”) and select the 10Web Booster zip file

Instalación vía FTP

Accede a tu espacio de alojamiento a través de un software FTP, por ejemplo FileZilla.↵
Descomprime la carpeta descargada del plugin 10Web Booster sin realizar ningún cambio en la carpeta.↵
Sube el plugin 10Web Booster en la siguiente ubicación wp-content>wp-plugins.↵
Accede al panel de administrador de WordPress.↵
Activa 10Web Booster yendo a Plugins y pulsando el botón Activar.

Sign-up is required to connect to the 10Web booster service.

FAQ

1. ¿Funciona el 10Web Booster también en móviles?

¡Absolutamente! Con 10Web Booster puede acelerar su sitio WordPress tanto en móvil como en escritorio.

2. ¿Funciona 10Web Booster en todos los sitios web?

10Web Booster optimizes any WordPress website’s speed automatically. Our website booster will provide optimal speed for any and all WordPress websites.

3. ¿Durará el resultado conseguido por 10Web Booster?

The easy answer is yes!
As 10Web Booster is constantly being updated and syncing with Google algorithms and changes, your WordPress speed optimization results will last as long as your website is connected to the 10Web Booster!

4. ¿Cómo puedo optimizar otras páginas de mi sitio o sitios web?

After you connect your website and start the optimization for your homepage, you will be redirected to your dashboard. In the General tab, you will see a URL slot to add and optimize more pages. Add up to 5 inner pages in the free version. They will be optimized using the default mode we’ve set for your homepage, however, you can always change the optimization mode for a specific page from the Custom rules tab (Pro version).

We’ll leave you to it.

5. ¿Cómo puedo pasar a la versión Pro?

Puede completar la optimización de su sitio web cambiando a 10Web Booster Pro desde su .

6. ¿Cuál es la diferencia entre los cuatro modos de optimización?

Los cuatro modos para su plugin de optimización de la velocidad de WordPress son los siguientes:

El modo Estándar, que en sí mismo incluye las siguientes características.

  • CSS & Minificación de HTML& Compresión
  • Caché de página
  • Minificación y Comprensión JS
  • Optimización de imagen
  • Carga diferida de iFrame y Video
  • Cambio de fuentes
  • Conversión de formato de imagen a WebP
  • iFrame and Video Lazy load
  • Redimensionamiento de imágenes específico para cada contenedor

El Modo Equilibrado incluye funciones de modo estándar + generación de CSS crítico↵
El Modo Fuerte incluye funciones de modo estándar + todos los retardos de JS↵
El Modo Extremo implica funciones de modo estándar + generación de CSS crítico + todos los retardos de JS

7. ¿Cuál es el historial de 10Web Booster?

10Web Booster es conocido por automatizar el proceso de conseguir:

Automated 90+ PageSpeed
Optimized Core Web Vitals
Higher search engine rankings
Up to 7% boost in conversions
Up to 40% boost in visitor engagement
Up to 53% mobile traffic engagement boost

8. ¿Cómo afecta 10Web Booster a la tasa de rebote?

With a 90+ page speed, averaging up to a load time of 1.5 seconds, bounce rate worries are out of the question with 10Web Booster. We’re better than good, literally. Good being an average of 2 seconds for load time, which translates to an average of 4 seconds of loading to cause a bounce. There’s no need to worry about your WordPress page speed optimization with the best website speed optimizer, 10Web Booster.

9. ¿Cuánto tiempo tarda la optimización?

As a plugin that aims to speed up WordPress sites, taking too long wasn’t an option.

La optimización de la velocidad de WordPress suele llevar sólo unos minutos.

10. ¿Puedo utilizar simultáneamente varios optimizadores de velocidad para mi sitio web?

WordPress’ functionality is in its prime when there’s only one speed optimizer fix for any website at a time.
So using another speed optimizer alongside 10Web Booster is not recommended by either us or WordPress.

Un optimizador de velocidad de WordPress alternativo podría ser cualquiera de los siguientes:

W3 Total Cache
WP Super Cache
WP Rocket
WP Rocket Footer JS
Autoptimize
Perfmatters
WP Fastest Cache
WP-Optimize
Asset CleanUp
Shortpixel AI
Rocket Lazy load
Hummingbird
Smush
Flying Scripts
Async JavaScript
NitroPack
PageSpeed Ninja
Swift Performance Lite
Swift Performance
Fast Velocity Minify
LiteSpeed Cache
WP Performance Score Booster
SG Optimizer
Ezoic

11. What’s the difference between cache plugins and 10Web Booster?

To sum up caching plugins, they attempt to speed up your website by simply caching files, clearing site cache, compressing cached pages, and performing HTML minification. They don’t require third-party servers for operation and run inside WP servers.

10Web Booster is more than just a plugin, it’s a service that speeds up your website with a wider range of optimization techniques. These techniques can only be implemented using a specific service for website optimization (10Web Booster services), rather than running the solution inside of the WordPress hosting server.

12. ¿Reemplaza 10Web Booster a todos los plugins de optimización de imágenes, almacenamiento en caché y otros plugins de optimización?

Sí. 10Web Booster es una solución todo en uno para optimizar sitios web. Implementa docenas de técnicas de optimización de la velocidad, desde la simple minificación hasta el retraso de JS y la generación crítica de CSS para la optimización del frontend y el alojamiento superrápido para la optimización del backend. No hay necesidad de ejecutar otro plugin de optimización de velocidad junto con 10Web. La única característica importante que no tiene todavía es CDN que se incluye en la hoja de ruta.

13. ¿Cuáles son las características de almacenamiento en caché de 10Web Booster?

10Web uses page cache and file cache. They are used to store dynamic webpages as static files. When a repeating visitor accesses your webpage, a “static” version of your webpage is quickly loaded from the cache. This feature works for all websites optimized with 10Web Booster, including those not hosted on 10Web. For sites hosted on 10Web, even more caching options are available, including NGINX FastCGI Cache.

Reseñas

19 de abril de 2024
I had an incredible experience with 10web's customer support team. They were prompt, professional, and solved my issue instantly. I can't thank them enough for their exceptional service.
18 de abril de 2024
We have been using 10web and this plugin for about six months now and are extremely happy! Not only are all my websites running super fast now, but anytime I notice a dip in performance Mane or one of the support staff have been incredibly quick to fix it and get us back on track. I feel very lucky to have a support team like them behind me!
15 de abril de 2024
I've been trying for quite some time to get something that will really speed up my website. This did the job, great suport too.
12 de abril de 2024
Maybe the plugin is working fine but the CONSTANT spamming makes the company very despicable. Especially because I clicked on the 'Unsubscribe' option 4 times. To no avail. Big privacy issues here.
Leer todas las 345 reseñas

Colaboradores y desarrolladores

«10Web Booster – Website speed optimization, Cache & Page Speed optimizer» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

Registro de cambios

2.27.4

Improved: Finding page_id for author and archive pages
Improved: Performance when querying images from DB
Fixed: Perfomance service fixes for ERR_TOO_MANY_REDIRECTS bug
Fixed: PHP8 Warnings

2.26.6

Improved: Images Lazy Load for Woocommerce Products
Improved: Cache exclusion

2.25.14

Improved: PHP8.3 compatibility
Changed: Minimum required PHP version is now 7.4
Added: Hooks and filters for manipulating SB output
Added: Support for DONOTCACHEPAGE and DONOTOPTIMIZEPAGE

2.24.18

Improved: PHP8.2 compatibility
Fixed: Security issue

2.24.14

Fixed: Kinsta cache clearing
Fixed: IO package

2.24.12

Improved: Added compatibility checks
Improved: Critical CSS generation
Improved: Compatibility with other plugins
Fixed: Loading Google Ads
Fixed: Disabling background images lazyload from 10web Dashboard
Fixed: Texts in deactivation popup
Fixed: Iframe lazyload bug

2.23.18

Added: More WP actions

2.23.16

Improved: Compatibility with Divi theme

2.23.15

Fixed: Issues with connection

2.23.14

Fixed: Connection bugs

2.23.13

Updated: IO package

2.23.12

Fixed: Error when setting attributes for scripts
Fixed: Corrupted JSON in certain cases when «Delay All JS» option is on
Fixed: Bug with pages displaying in 10Web Dashboard
Fixed: Comment about page cache when Whitelabel is enabled
Updated: Minor Ui changes
Improved: Excluded non-html pages from optimization
Improved: Font loading improvements
Improved: Updated IO package

2.22.32

Fixed: Generating Critical CSS for hosted multisites

2.22.31

Fixed: URL scheme checking

2.22.30

Fixed: Fixed division by zero bug

2.22.29

Fixed: Do not write WebP delivery lines if the website is already serving WebP
Fixed: Elementor animation conflicts with Critical CSS
Fixed: Elementor’s lazyload is disabled when our plugin is enabled and working
Improved: Activation of the plugin is faster now because of refactored score check logic
Improved: Slideshows work with «Delay All JS» is enabled
Fixed: Bug when no fonts are being added to the homepage
Improved: Added exception handling for JS Minifier
Improved: Added new options to SB REST API
Fixed: Compatibility with Hubspot Calendar
Fixed: Deprecation warnings
Fixed: Adding display:swap to font loading
Improved: Added fm_cookie_ to the list of non-cached cookies

2.21.25

Updated: Settings REST API
Improved: folder exclusion of JS files
Fixed: UI bugs

2.21.16

Fixed: Excluding scripts from Delay ALL JS via regexp
Fixed: Firing events after Delay All JS

2.21.12

Updated: IO package

2.21.11

Fixed: Bug when admin bar content were not fully visible on small screens
Added: Reconnect button in WP admin when connection issues are detected (no token or domain_id).
Improved: Background lazyload
Fixed: Events fired after connecting delayed JS files
Fixed: Issues when «Delay All JS» was breaking schema.org JSON
Updated: SB Settings REST API

2.20.33

Fixed: Minor bug

2.20.32

Fixed: Bug with firing events

2.20.31

Refactored: Critical CSS generation
Changed: Multiselect option to disable events that are being triggered after connecting all scripts in «Delay All Js»
Fixed: Conflicts with web-stories plugin
Fixed: html validation errors
Added: REST API for editing all the SB settings to integrate it in 10Web Dashboard
Fixed: Handling complicated cases of Critical Background Images
Fixed: Excluding Owl Carousel JS scripts from «Delay All JS» option
Added: Popup to notify user that she can enable auto-update of Booster plugin
Fixed: Logic of Critical CSS generation during other plugins updates
Fixed: «Custom Events» option
Fixed: Page optimization if test mode is on
Changed: Elementor’s animations now works with enabled «Delay All JS» option
Lightened: Logic during onboarding flow, fixed many bugs
Added: Special option to fix Scroll issues created by Critical CSS
Added: Special selectbox with Plugin/Theme/JS scripts list for easily exclude them from «Delay All JS» option
Fixed: Couple of Score Check warnings in WP admin
Changed: SB is now disabled on AMP pages by default

2.19.49

Fixed: UI issues

2.19.46

Updated: IO package

2.19.45

Updated: IO package

2.19.44

Changed: Connection logic for new IO plugin
Added: «Clear cache» button in advanced settings of the plugins clears CF cache
Improved: Reliability of score check
Improved» Stability

2.18.17

Changed: Load only critical fonts by default
Added: Default options for Critical CSS
Improved: Compatibility with Divi theme
Added: An option to lazyload iframes on user interaction
Added: Browser caching rules to the .htaccess file
Improved: Critical CSS generation
Improved: Viewport images gathering
Fixed: Bugs related to «Delay All JS» option
Improved: Connection logic
Improved: Score check stability in WP Admin
Fixed: A couple of bugs on static file caching
Fixed: PHP warnings
Fixed: WP Cron functionality

2.17.23

Improved score check in the WP dashboard

2.17.21

Added: Block to easily share the referral link
Improved: Image Optimizer
Improved: Lazy Load both for background images and regular images
Updated: Parameters to ignore for page cache
Changed: Now SB’s scripts are being injected inside the tag, not before it
Added: When changing the background image in Elementor’s page edit, Critical CSS will be regenerated for that page
Fixed: Couple of bugs that resulted in fatal errors on the websites
Fixed: Loading of critical fonts
Added: New option for critical fonts that allows load only them or exclude them from Critical CSS
Fixed: Bug that prevented enabling/disabling some options from 10Web Dashboard

2.15.18

Changed: Fully refactored IO package and service
Improved: Image optimizing queue
Removed: AWS package as dependency in favor of presigned keys.
Improved: Performance of getting data from the IO service
Improved: Performance of getting optimized images statistics in 10Web Dashboard
Refactored: Autooptimize feature to work with WP Cron
Added: Option to load excluded JS files the simple way
Added:Data size limit for Cache Structure to avoid database overflow
Fixed: Injecting scripts into tag, instead of appending them to it
Changed: «Exclude Elementor Scripts» now excludes also 10Web Builder
Improved: Exclude critical fonts from Uncritical CSS, and avoid loading them twice
Fixed: Minor UI issues
Fixed: Fatal error when plugin is activated on website with no posts and pages
Fixed: Error in «Delay All JS»‘s Web Worker
Fixed: Warning about strpos() function

2.14.50

Changed: Now collecting excluded images for background works only if that option is checked in plugin settings
Fixed: The bug when sometimes sizes for critical css generation were not sent to the Performance service

2.14.49

Changed: New faster connection logic
Refactored: Constructors not to use superglobal variables
Changed: CDN page
Added: Auto-exclude images in viewport
Fixed: Disconnect popup when White Label is on
Improved: Fonts loading
Fixed: serving gzipped page caches
Improved: Cache compatibility with Litespeed servers
Fixed: Iincompatibility with Elementor’s Background lazyload function
Changed: Google Ads JS files now excluded by default from the «Delay All JS»
Fixed: PHP warning about not emtpy directory when clearing the cache
Added: Notice about missing DOMDocument extension
Fixed: PHP warning about count() function’s parameters
Fixed: breaking Unicode characters inside inline scripts while connecting them to the page
Removed: All dependencies of old minifier
Improved: Worker in «Delay All JS» option

2.13.47

Fixed: CSS Minifier bug
Changed: CSS Minifier library

2.13.45

Fixed: Security issue

2.13.44

Fixed: Errors when migrating not-optimized pages from old structure to new
Added: lazy loading for video poster
Added: fallback for default page sizes during Critical CSS generation

2.13.42

Fixes: Whitelabel bug in certain conditions
Fixed: Web worker’s bug with scripts loading scripts.
Fixed: Cache bugs for 10Web hosted websites

2.13.41

Fixed: Whitelable fatal error

2.13.40

Disabled: logging by default
Fixed: conflicts with other plugins using Composer autoloader

2.13.37

Refactored: Plugin uninstall logic
Added: Option to exclude Elementor Pro JS fles from «Delay All JS»
Added: «Perforamance Lab» to exclude list of plugins
Fixed: Multisite or low PHP version warnings in the plugin, refactored plugin’s main file
Fixed: Updating cache constants on plugin activate/deactivate
Fixed: Deleting a page from the list of not-optimizable pages in Dashboard
Changed: «Delay All JS» option now works with script tags added in Gutenberg’s text block
Added: Option to exclude «10web Photo Gallery» plugin from delay
Added: GET routes in plugin’s REST API as a workaround of Cloudflare’s POST to GET convertion fix
Moved: Hardcoded not-optimizable pages list to the option
Changed: Now adding tag for lazyloaded images is optional
Fixed: Congrats popup in advanced mode
Fixed: Minor UI fixes for RTL websites
Added: .min to all minified CSS and JS files
Added: «Clear Cache» button for clients with activated White Label
Changed: Score check functionality is moved to a separate package
Changed: Generated JS and CSS files are not cleared now during cache flush, but are being overwritten
Fixed: An issue when we always call the site state update
Added: Bluehost cache is now cleared with our cache clear
Added: An option to enable WP’s autoupdate for SB plugin
Changed: 10Web Transients logic is moved to a separate package
Fixed: Bug when we show Booster plan as paid when client purchased only AI Assistant
Removed: all .git folders from vendor/ directory

2.12.26

Added: Cache warmup after cleaning cache in the plugin
Fixed: Bug with many requests to the page to determine its page ID

2.12.23

Fixed: Security issue

2.12.22

Changed: API keys

2.12.21

Changed: Optimization flow

2.12.15

Changed: Onboarding flow
Fixed: Minor UI/UX

2.11.43

Fixed: Transients and permanent cache conflicts

2.11.42

Fixed: Minor bug

2.11.41

Added: NPS survey banner
Added: Option to load excluded JS files with worker
Added: Customer support page
Improved: Debug log
Fixed: Connection issues

2.10.68

Improved: Optimization flow

2.10.66

Improved: Cache structure

2.10.65

Added: New signup logic
Fixed: «Optimized Background Images» option
Fixed: Issue when non-cached page is served

2.10.46

Changed: Design for plugin interface
Improved: File cache
Changed: All aggregated CSS and JS files now have same naming
Added: Option to exclude popular sliders from “Delay All JS” option
Added: Smart lazyload for iframes, sliders and videos. Now if there is no such item on the page, the optimization or exclusion of it won’t work on that page.
Improved: Background lazy-loading for specific cases
Added: An option to set SB Page Cache lifetime.
Added: Now you can optimize author and 404 pages.
Improved: Third-party cache clearing
Changed: All similar Google Fonts are being merged after download and connect as one to get rid of duplicates
Fixed: Bug when lazyload broked audio tags
Fixed: A couple of bugs with Page Counter when home page is set to “Latest Posts”
Fixed: Bug when Optimized Background Images option conflicted with Background LazyLoad
Fixed: Bug when Critical CSS is not being connected to the page when “Use Critical Font” is unchecked
Fixed: Bug when home page was defined incorectly if was written with http or with www.
Fixed: Bug preventing onboarding flow to finish in NO_REST Critical CSS import
Refactored:“Delay All JS” optimization, now scripts are not moved from their places, this improves stability.

2.9.27

Fixed: Minor bug

2.9.25

Fixed: Minor bug

2.9.24

Fixed: Gutenberg block
Fixed: Elementor block

2.9.23

Fixed: Deactivation popup on the Plugins page.
Fixed: Bug when Critical CSS was being regenerated after the update.
Fixed: Bug when the cache was kept after removing, disabling, or deactivating the plugin.
Improved: Critical CSS generation.
Improved: Critical Fonts generation.
Fixed: Bug with the Optimized Background Images option.

2.8.35

Fixed: Security issue

2.8.34

Fixed: Security issue
Added: BF offer

2.8.32

Added: Endpoint to enable/disable CF integration.
Added: Hooks to clear CF cache.
Updated: IO package
Added: An option to load fonts after CSS load

2.8.19

Fixed: Compatibility issue with WordPress 6.1.

2.8.18

Changed: Many UI
Improved: Stability for Critical CSS generation
Fixed: Incompatibility issues with WPML’s Woocommerce Multilingual module
Improved: Performance improvements

2.7.47

Fixed: Critical CSS regeneration issues

2.7.44

Improved: REST API speed
Improved: Page cache.

2.7.37

Added: Wp admin dashboard UI changes.
Added: Optimization of archive and product pages.

2.6.42

Improved: Onboarding flow
Added: A dedicated page to manage Whitelable settings

2.6.40

Improved: REST API reliability and Critical CSS generation

2.6.37

Fixed: Critical CSS generation

2.6.31

Fixed: Minor bug

2.6.30

Changed: Onboarding flow
Fixed: Bug in page cache on hosted website

2.3.3

Added: Compatibility with WPML

2.3.2

Fixed: Bug in white label
Improved: Images Lazyload

2.3.1

Improved: Plugin white label
Improved: Images Lazyload (Now works with picture tags and srcsets)
Improved: Critical CSS stability

2.3.0

Added: Option to white label admin dashboard

2.2.18

Improved: Font preload
Added: New special mode for collecting images

2.2.16

Fixed: Page cache if it is not correctly set up.

2.2.15

Fixed: Warning messages about WebP and Page Caching
Fixed: Warning about advanced-cache.php
Reduced: Vendor size
Updated: Incompatible plugins list

2.2.12

Added: Test mode
Fixed: Bug in page cache

2.2.8

Improved: Critical CSS stability
Fixed: Bug in page cache
Fixed: Bug in clear cache

2.0.27

Disabled: Cleare cache trigger on ACF update
Removed: Deactivation popup for hosted websites
Changed: Notification texts

2.0.26

Added: Notice about incompatible plugins

2.0.25

Fixed: Bug in the page cache
Added: Trigger to clear page cache on page edit

2.0.22

Fixed: Conflicts with 3rd party plugins images lazy load
Improved: Optimization flow
Fixed: Bug in JS delay

2.0.21

Added: Image optimization for additional pages
Added: Deactivation pop-up

2.0.18

Improved: Optimization flow

2.0.17

Changed: Composer update for image optimizer

2.0.16

Added: Clear cache on disconnect website
Added: Compatibility for connecting from Photo Gallery plugin.

2.0.15

Changed: Get Critical CSS via Rest API instead of Ajax call

2.0.14

Fixed: Bug in homepage optimization flow

2.0.13

Fixed: Conflicts with third party plugins and hostings caches
Fixed: Bug in tag attributes

2.0.12

Fixed: Google ads display
Fixed: Uncritical CSS loading with worker

2.0.11

Changed: Welcome page design
Fixed: Bug in Critical CSS generation

2.0.10

Added: Rest route to edit optimization settings via REST API

2.0.9

  • Fixed: Minor bug

2.0.7

  • Fixed: Whitelabel bug
  • Fixed: bug with redirection after update

2.0.3

  • Initial version on wp.org