Join the community today
Become a Member

CDN WebPerf Benefits of using a common CDN based webfont, javascript, css going away soon !

Discussion in 'Web Development & Web Performance' started by eva2000, Sep 30, 2019.

  1. eva2000

    eva2000 Administrator Staff Member

    45,434
    10,311
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +15,991
    Local Time:
    12:37 PM
    Nginx 1.19.x
    MariaDB 5.5/10.x
    Just came across this Twitter conversation and reply from Patrick (from webpagetest.org and now works at Cloudflare) regarding if there's any benefits of using a common CDN base library, webfont, javascript, or css across different domains and it seems with upcoming Chrome web browser could change such benefits Patrick Meenan on Twitter

    The benefits we are talking about are if you use Google webfont which is hosted on Google CDN, you assume to receive the benefit that other web sites who use the same Google CDN hosted webfont will potentially already have warmed up the cache and browser cache for your visitors who have visited other sites using the same CDN webfont. So page load speed for visitor is faster as their web browser's cache is already got a copy of the CDN webfont.

    However, Chrome proposed change could remove such benefits by partitioning the HTTP cache Partition the HTTP Cache - Chrome Platform Status
    Sounds like in future if you want to improve page load speed and browser cache hit rates, you'd want the CDN to be served from your own same origin domain name. i.e. use Cloudflare CDN for your domain/site :)