I installed ShortPixel Adaptive Images but it doesn't seem to work
Known conflicts, issues and workarounds
Please take a look at this article to know more about this.
- Your domain is not associated to your account: How can I associate a domain to my account?
- You don't have enough available optimization credits. If this is the case, please purchase a new plan, or in case you have a monthly quota, upgrade your plan.
- The API URL is not correct. It is located on Settings > ShortPixel AI > Behaviour and by default it should be "https://cdn.shortpixel.ai/spai" (see image below); only change it if you know what you're doing.
- You use a caching plugin or your hosting provider uses a caching mechanism, and the cache has not been flushed after installing and configuring SPAI. The solution is to flush your cache to get rid of old image URLs being displayed. To do a proper cache clearing, please read this article: How to clear WordPress cache
- There is another plugin or theme that has a lazy loading feature activated and this conflicts with SPAI. The solution is to deactivate this functionality on the plugin or theme that use it. Please notice that you don't need to disable lazy loading on videos or other resources; only image lazy loading must be disabled.
- Your images are already being delivered as WebP. Please deactivate any other WebP delivering method that is not provided by ShortPixel Adaptive Images.
- jQuery has been disabled either manually or by another plugin. In this case, SPAI will not work properly. Please make sure jQuery is enabled.
- Your hosting provider is SiteGround and you are working on a staging site. The way SiteGround creates staging sites is a little bit different: they are using a filter to replace the domain names in the URLs. Please ignore any malfunction in this case, as the live site will probably work correctly.
- There is a conflict with another plugin or theme.
Only some images are not optimized
Sometimes SPAI is actually working correctly, but not all the images are being served from our CDN. This can happen because:
- The images are background images ("background-image" CSS property) declared in .css files. Please activate the "Replace in CSS files" option.