New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| This setting aims to prevent things from breaking by serving "fallback" CSS or JS. The fallback-files are copies of the first Autoptimized CSS & JS files created after the cache was emptied and as such will based on the homepage. This means that the CSS/ JS migth not apply 100% on other pages, but at least the impact of missing CSS/ JS will be lessened (often significantly). | You have to log in to add a translation. | Details | |
Original untranslated This setting aims to prevent things from breaking by serving "fallback" CSS or JS. The fallback-files are copies of the first Autoptimized CSS & JS files created after the cache was emptied and as such will based on the homepage. This means that the CSS/ JS migth not apply 100% on other pages, but at least the impact of missing CSS/ JS will be lessened (often significantly). You have to log in to edit this translation. | |||
| Autoptimize caches aggregated & optimized CSS/ JS and links to those cached files are stored in the HTML, which will be stored in a page cache (which can be a plugin, can be at host level, can be at 3rd party, in the Google cache, in a browser). If there is HTML in a page cache that links to Autoptimized CSS/ JS that has been removed in the mean time (when the cache was cleared) then the page from cache will not look/ work as expected as the CSS or JS were not found (a 404 error). | Optimización automática de cachés agregados & amp; CSS / JS optimizados y los enlaces a esos archivos en caché se almacenan en el HTML, que se almacenará en la caché de una página (que puede ser un complemento, puede estar a nivel de servidor, puede estar en un tercero, en la caché de Google, en un navegador). Si hay HTML en la caché de una página que se vincula a CSS / JS optimizado automáticamente que se ha eliminado mientras tanto (cuando se borró la caché), la página de la caché no se verá / funcionará como se esperaba ya que no se encontraron CSS o JS (un error 404). | Details | |
Original current Autoptimize caches aggregated & optimized CSS/ JS and links to those cached files are stored in the HTML, which will be stored in a page cache (which can be a plugin, can be at host level, can be at 3rd party, in the Google cache, in a browser). If there is HTML in a page cache that links to Autoptimized CSS/ JS that has been removed in the mean time (when the cache was cleared) then the page from cache will not look/ work as expected as the CSS or JS were not found (a 404 error). CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Check <a href="https://wordpress.org/plugins/autoptimize-criticalcss/#faq">the FAQ on the (legacy) "power-up" here</a>, this info will be integrated in this FAQ at a later date. | You have to log in to add a translation. | Details | |
Original untranslated Check <a href="https://wordpress.org/plugins/autoptimize-criticalcss/#faq">the FAQ on the (legacy) "power-up" here</a>, this info will be integrated in this FAQ at a later date. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| The short answer: probably not. Although inlining all CSS will make the CSS non-render blocking, it will result in your base HTML-page getting significantly bigger thus requiring more "roundtrip times". Moreover when considering multiple pages being requested in a browsing session the inline CSS is sent over each time, whereas when not inlined it would be served from cache. Finally the inlined CSS will push the meta-tags in the HTML down to a position where Facebook or Whatsapp might not look for it any more, breaking e.g. thumbnails when sharing on these platforms. | You have to log in to add a translation. | Details | |
Original untranslated The short answer: probably not. Although inlining all CSS will make the CSS non-render blocking, it will result in your base HTML-page getting significantly bigger thus requiring more "roundtrip times". Moreover when considering multiple pages being requested in a browsing session the inline CSS is sent over each time, whereas when not inlined it would be served from cache. Finally the inlined CSS will push the meta-tags in the HTML down to a position where Facebook or Whatsapp might not look for it any more, breaking e.g. thumbnails when sharing on these platforms. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| What does "enable 404 fallbacks" do? Why would I need this? | ¿Qué hace "habilitar 404 fallbacks"? ¿Por qué necesitaría esto? | Details | |
Original current What does "enable 404 fallbacks" do? Why would I need this? CommentFound in faq header. You have to log in to edit this translation. | |||
| Do I still need the Critical CSS power-up when I have Autoptimize 2.7 or higher? | ¿Todavía necesito el encendido de CSS crítico cuando tengo Autoptimize 2.7? | Details | |
Original fuzzy Do I still need the Critical CSS power-up when I have Autoptimize 2.7 or higher? CommentFound in faq header. You have to log in to edit this translation. | |||
| I can't get Critical CSS working | No puedo conseguir que Critical CSS funcione | Details | |
Original current I can't get Critical CSS working CommentFound in faq header. You have to log in to edit this translation. | |||
| No; Image optimization depends on the ability of the external image optimization service to fetch the original image from your site, optimize it and save it on the CDN. If you images cannot be downloaded by anonymous visitors (due to firewall/ proxy/ password protection/ hotlinking-protection), image optimization will not work. | No, la optimización de la imagen depende de la capacidad del servicio externo de optimización de imágenes para obtener la imagen original de tu sitio, optimizarla y guardarla en el CDN. Si tus imágenes no pueden ser descargadas por visitantes anónimos (debido a un cortafuegos/proxy/protección por contraseña/protección de enlazado), la optimización de las imágenes no funcionará. | Details | |
Original current No; Image optimization depends on the ability of the external image optimization service to fetch the original image from your site, optimize it and save it on the CDN. If you images cannot be downloaded by anonymous visitors (due to firewall/ proxy/ password protection/ hotlinking-protection), image optimization will not work. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| When image optimization is on, Autoptimize will look for png, gif, jpeg (.jpg) files in image tags and in your CSS files that are loaded from your own domain and change the src (source) to the ShortPixel CDN for those. Important: this can only work for publicly available images, otherwise the image optimization proxy will not be able to get the image to optimize it, so firewalls or proxies or password protection or even hotlinking-prevention might break image optimization. | Cuando la optimización de imágenes está activada, Autoptimize buscará archivos png, gif, jpeg (.jpg) en las etiquetas de las imágenes y en los archivos CSS que se cargan desde tu propio dominio y cambiará el «src» (origen) al ShortPixel CDN para ellas. Importante: esto solo puede funcionar para imágenes disponibles públicamente, de lo contrario, el proxy de optimización de imágenes no podrá obtener la imagen para optimizarla, por lo que, los corta fuegos, proxies, la protección por contraseña o, incluso, la prevención de enlazado, podrían romper la optimización de las imágenes. | Details | |
Original current When image optimization is on, Autoptimize will look for png, gif, jpeg (.jpg) files in image tags and in your CSS files that are loaded from your own domain and change the src (source) to the ShortPixel CDN for those. Important: this can only work for publicly available images, otherwise the image optimization proxy will not be able to get the image to optimize it, so firewalls or proxies or password protection or even hotlinking-prevention might break image optimization. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Can I use image optimization for my intranet/ protected site? | ¿Puedo usar la optimización de imágenes para mi intranet/sitio protegido? | Details | |
Original current Can I use image optimization for my intranet/ protected site? CommentFound in faq header. You have to log in to edit this translation. | |||
| Domain mapped multisites require Autoptimize to be initialized at a different WordPress action, add this line of code to your wp-config.php to make it so to hook into <code>setup_theme</code> for example: | Los dominios mapeados en WordPress multisitios requieren que Autoptimize se inicialice en una acción diferente de WordPress, agregue esta línea de código a su wp-config.php para que se conecte a <code>setup_theme</code>, por ejemplo: | Details | |
Original current Domain mapped multisites require Autoptimize to be initialized at a different WordPress action, add this line of code to your wp-config.php to make it so to hook into <code>setup_theme</code> for example: CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| AO minifies excluded JS/ CSS if the filename indicates the file is not minified yet. As of AO 2.5 you can disable this on the "JS, CSS & HTML"-tab under misc. options by unticking "minify excluded files". | You have to log in to add a translation. | Details | |
Original untranslated AO minifies excluded JS/ CSS if the filename indicates the file is not minified yet. As of AO 2.5 you can disable this on the "JS, CSS & HTML"-tab under misc. options by unticking "minify excluded files". CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| When clearing AO's cache, no page cache should contain pages (HTML) that refers to the removed optimized CSS/ JS. Although for that purpose there is integration between Autoptimize and some page caches, this integration does not cover 100% of setups so you might need to purge your page cache manually. | You have to log in to add a translation. | Details | |
Original untranslated When clearing AO's cache, no page cache should contain pages (HTML) that refers to the removed optimized CSS/ JS. Although for that purpose there is integration between Autoptimize and some page caches, this integration does not cover 100% of setups so you might need to purge your page cache manually. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Can't log in on domain mapped multisites | No se puede iniciar sesión en multisitios con dominio asignados | Details | |
Original current Can't log in on domain mapped multisites CommentFound in faq header. You have to log in to edit this translation. | |||
| I excluded files but they are still being autoptimized? | ¿He excluido los archivos, pero aun están siendo optimizados? | Details | |
Original current I excluded files but they are still being autoptimized? CommentFound in faq header. You have to log in to edit this translation. | |||
Export as
Comment
Found in faq paragraph.