New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| My site looks broken when I purge Autoptimize's cache! | You have to log in to add a translation. | Details | |
Original untranslated | |||
| Starting with version 1.6.6 Autoptimize excludes everything inside noptimize tags, e.g.:↵ <!--noptimize--><script>alert('this will not get autoptimized');</script><!--/noptimize--> | You have to log in to add a translation. | Details | |
Original untranslated Starting with version 1.6.6 Autoptimize excludes everything inside noptimize tags, e.g.:↵ <!--noptimize--><script>alert('this will not get autoptimized');</script><!--/noptimize--> CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| By default AO uses non multibyte-safe string methods, but if your PHP has the mbstring extension you can enable multibyte-safe string functions with this filter; | You have to log in to add a translation. | Details | |
Original untranslated By default AO uses non multibyte-safe string methods, but if your PHP has the mbstring extension you can enable multibyte-safe string functions with this filter; CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Some of the non-ASCII characters get lost after optimization | You have to log in to add a translation. | Details | |
Original untranslated Some of the non-ASCII characters get lost after optimization CommentFound in faq header. You have to log in to edit this translation. | |||
| As from AO 2.4 AO "listens" to page cache purges to clear its own cache. You can disable this behavior with this filter; | You have to log in to add a translation. | Details | |
Original untranslated As from AO 2.4 AO "listens" to page cache purges to clear its own cache. You can disable this behavior with this filter; CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Can I disable AO listening to page cache purges? | You have to log in to add a translation. | Details | |
Original untranslated Can I disable AO listening to page cache purges? CommentFound in faq header. You have to log in to edit this translation. | |||
| Have a look at <a href="https://shortpixel.helpscoutdocs.com/category/60-shortpixel-ai-cdn">Shortpixel's FAQ</a>. | You have to log in to add a translation. | Details | |
Original untranslated Have a look at <a href="https://shortpixel.helpscoutdocs.com/category/60-shortpixel-ai-cdn">Shortpixel's FAQ</a>. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Where can I get more info on image optimization? | You have to log in to add a translation. | Details | |
Original untranslated Where can I get more info on image optimization? CommentFound in faq header. You have to log in to edit this translation. | |||
| How does image optimization work? | You have to log in to add a translation. | Details | |
Original untranslated How does image optimization work? CommentFound in faq header. You have to log in to edit this translation. | |||
| Make sure you're not running other HTML, CSS or JS minification plugins (BWP minify, WP minify, ...) simultaneously with Autoptimize or disable that functionality your page caching plugin (W3 Total Cache, WP Fastest Cache, ...). Try enabling only CSS or only JS optimization to see which one causes the server error and follow the generic troubleshooting steps to find a workaround. | You have to log in to add a translation. | Details | |
Original untranslated Make sure you're not running other HTML, CSS or JS minification plugins (BWP minify, WP minify, ...) simultaneously with Autoptimize or disable that functionality your page caching plugin (W3 Total Cache, WP Fastest Cache, ...). Try enabling only CSS or only JS optimization to see which one causes the server error and follow the generic troubleshooting steps to find a workaround. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| JavaScript files that are not autoptimized (because they were excluded or because they are hosted elsewhere) are typically render-blocking. By adding them in the comma-separated "async JS" field, Autoptimize will add the async flag causing the browser to load those files asynchronously (i.e. non-render blocking). This can however break your site (page), e.g. if you async "js/jquery/jquery.min.js" you will very likely get "jQuery is not defined"-errors. Use with care. | You have to log in to add a translation. | Details | |
Original untranslated JavaScript files that are not autoptimized (because they were excluded or because they are hosted elsewhere) are typically render-blocking. By adding them in the comma-separated "async JS" field, Autoptimize will add the async flag causing the browser to load those files asynchronously (i.e. non-render blocking). This can however break your site (page), e.g. if you async "js/jquery/jquery.min.js" you will very likely get "jQuery is not defined"-errors. Use with care. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Preconnect is a somewhat advanced feature to instruct browsers (<a href="https://caniuse.com/#feat=link-rel-preconnect">if they support it</a>) to make a connection to specific domains even if the connection is not immediately needed. This can be used e.g. to lessen the impact of 3rd party resources on HTTPS (as DNS-request, TCP-connection and SSL/TLS negotiation are executed early). Use with care, as preconnecting to too many domains can be counter-productive. | You have to log in to add a translation. | Details | |
Original untranslated Preconnect is a somewhat advanced feature to instruct browsers (<a href="https://caniuse.com/#feat=link-rel-preconnect">if they support it</a>) to make a connection to specific domains even if the connection is not immediately needed. This can be used e.g. to lessen the impact of 3rd party resources on HTTPS (as DNS-request, TCP-connection and SSL/TLS negotiation are executed early). Use with care, as preconnecting to too many domains can be counter-productive. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Google Fonts are typically loaded by a "render blocking" linked CSS-file. If you have a theme and plugins that use Google Fonts, you might end up with multiple such CSS-files. Autoptimize (since version 2.3) now let's you lessen the impact of Google Fonts by either removing them alltogether or by optimizing the way they are loaded. There are two optimization-flavors; the first one is "combine and link", which replaces all requests for Google Fonts into one request, which will still be render-blocking but will allow the fonts to be loaded immediately (meaning you won't see fonts change while the page is loading). The alternative is "combine and load async" which uses JavaScript to load the fonts in a non-render blocking manner but which might cause a "flash of unstyled text". | You have to log in to add a translation. | Details | |
Original untranslated Google Fonts are typically loaded by a "render blocking" linked CSS-file. If you have a theme and plugins that use Google Fonts, you might end up with multiple such CSS-files. Autoptimize (since version 2.3) now let's you lessen the impact of Google Fonts by either removing them alltogether or by optimizing the way they are loaded. There are two optimization-flavors; the first one is "combine and link", which replaces all requests for Google Fonts into one request, which will still be render-blocking but will allow the fonts to be loaded immediately (meaning you won't see fonts change while the page is loading). The alternative is "combine and load async" which uses JavaScript to load the fonts in a non-render blocking manner but which might cause a "flash of unstyled text". CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| Although some online performance assessment tools will single out "query strings for static files" as an issue for performance, in general the impact of these is almost non-existant. As such Autoptimize, since version 2.3, allows you to have the query string (or more precisely the "ver"-parameter) removed, but ticking "remove query strings from static resources" will have little or no impact of on your site's performance as measured in (milli-)seconds. | You have to log in to add a translation. | Details | |
Original untranslated Although some online performance assessment tools will single out "query strings for static files" as an issue for performance, in general the impact of these is almost non-existant. As such Autoptimize, since version 2.3, allows you to have the query string (or more precisely the "ver"-parameter) removed, but ticking "remove query strings from static resources" will have little or no impact of on your site's performance as measured in (milli-)seconds. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
| This new option in Autoptimize 2.3 removes the inline CSS, inline JS and linked JS-file added by WordPress core. As such is can have a small positive impact on your site's performance. | You have to log in to add a translation. | Details | |
Original untranslated This new option in Autoptimize 2.3 removes the inline CSS, inline JS and linked JS-file added by WordPress core. As such is can have a small positive impact on your site's performance. CommentFound in faq paragraph. You have to log in to edit this translation. | |||
Export as
Comment
Found in faq header.