Title: Preload specific requests
Last modified: May 5, 2021

---

# Preload specific requests

 *  Resolved [boybawang](https://wordpress.org/support/users/boybawang/)
 * (@boybawang)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/)
 * Hi Frank –
 * Google PageSpeed Insights is recommending I preload key requests. So, I added
   one of the URLs to the field ‘Preload specific requests’, cleared cache, and 
   ran Pagespeed Insights again. It gave me the same recommendation on that URL.
   I’m using a CDN. When I check the font being loaded through Chrome Dev Tools,
   it shows the URL for the CDN’s CSS file instead of the one hosted on their server.
 * Do you have any recommendations?

Viewing 10 replies - 1 through 10 (of 10 total)

 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14403892)
 * so that font-file, is it loaded over the CDN or from your own site?
 * and did you put the CDN URL or the non-CDN URL in the preload field?
 *  Thread Starter [boybawang](https://wordpress.org/support/users/boybawang/)
 * (@boybawang)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14404303)
 * The font file is loaded over the CDN. I tried adding the CDN URL and the non-
   CDN URL in the “**Preload specific requests**” field. For both, Google PageSpeed
   Insights pointed to the non-CDN URL as a field that could be preloaded. And in
   both cases it was the CSS from the CDN URL that was being loaded.
 * This WordPress site is using a child theme, and is loading the fonts from the
   parent theme. Should that make any difference?
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14404334)
 * And did you add the entire URL, including querystring (?xyz=123) if any?
 *  Thread Starter [boybawang](https://wordpress.org/support/users/boybawang/)
 * (@boybawang)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14404440)
 * Yes, I entered the entire URL. There was no querystring.
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14404529)
 * Can you share your site’s URL so I can have a look at HTML source?
 *  Thread Starter [boybawang](https://wordpress.org/support/users/boybawang/)
 * (@boybawang)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14405277)
 * Sure, it’s [https://stubbsalderton.com/](https://stubbsalderton.com/)
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14405497)
 * OK, I see [https://12oitz47a3bo3l66vw1v6293-wpengine.netdna-ssl.com/wp-content/themes/salient/font/372D2F_3_0.woff2](https://12oitz47a3bo3l66vw1v6293-wpengine.netdna-ssl.com/wp-content/themes/salient/font/372D2F_3_0.woff2)
   being preloaded. Now is that what you put there, or did you put the non-CDN URL
   there?
 *  Thread Starter [boybawang](https://wordpress.org/support/users/boybawang/)
 * (@boybawang)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14407119)
 * I put the non-CDN URL there – [https://stubbsalderton.com/wp-content/themes/salient/font/372D2F_3_0.woff2](https://stubbsalderton.com/wp-content/themes/salient/font/372D2F_3_0.woff2)
 * The non-CDN URL is what Google PageSpeed Insights is recommending that I preload.
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14407151)
 * in that case the problem is that the CDN logic (from WP Engine) simply is too
   eager, it should not replace that field. Maybe ask WP Engine support how you 
   can prevent this from happening?
 *  Thread Starter [boybawang](https://wordpress.org/support/users/boybawang/)
 * (@boybawang)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14407790)
 * Will do, [@optimizingmatters](https://wordpress.org/support/users/optimizingmatters/).
   Thanks for looking into this. Closing thread.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Preload specific requests’ is closed to new replies.

 * ![](https://ps.w.org/autoptimize/assets/icon-256X256.png?rev=2211608)
 * [Autoptimize](https://wordpress.org/plugins/autoptimize/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autoptimize/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autoptimize/)
 * [Active Topics](https://wordpress.org/support/plugin/autoptimize/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autoptimize/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autoptimize/reviews/)

## Tags

 * [cdn](https://wordpress.org/support/topic-tag/cdn/)
 * [preload](https://wordpress.org/support/topic-tag/preload/)
 * [requests](https://wordpress.org/support/topic-tag/requests/)
 * [specific](https://wordpress.org/support/topic-tag/specific/)

 * 10 replies
 * 2 participants
 * Last reply from: [boybawang](https://wordpress.org/support/users/boybawang/)
 * Last activity: [4 years, 11 months ago](https://wordpress.org/support/topic/preload-specific-requests-2/#post-14407790)
 * Status: resolved