In some cases, you will notice that even after configuring the BunnyCDN plugin in WordPress, some or even all of the URLs for the static resources are not coming from BunnyCDN. In this guide, we will look into the most common reasons why this happens and how to solve them.
Your server might be configured to automatically push the resources to the browser, even without the browser requesting those. In this case, you will need to configure your server to disable HTTP/2 Push for requests that are already served from the CDN.
If your WordPress is configured with a static page caching plugin, it might be holding an older version of the pages in cache, before the CDN plugin has been activated. After activating the plugin for the first time, we suggest purging the cache of any caching plugins just in case to ensure that the new URLs are set.
This can also apply to various static caching configured by the web hosting itself. If you are aware your web hosting is actively caching pages, make sure to purge that as well.
Incorrect URL Detection
Our plugin works by detecting the URL of your WordPress page based on the settings inside of WordPress itself. In case no URLs are getting detected, we suggest checking that the URL in the Advanced Settings of the plugin matches with the actual URL of your website where the files are served from.
Dynamically Generated Scripts or Lazy Loading