HTTP/2 for Spotify Embed Widgets

Hi,

When running the PageSpeed Insights[1] for my blog which I use Spotify Embed Widgets[2] to share music I am getting performance hits due to the JavaScript files used for the Widgets being served over HTTP/1.1 instead of HTTP/2[3]. The images also i.e. the Single or Album covers are also being served over HTTP/1.1 instead of HTTP/2.

 

An example JavaScript file[4] and an example image[5].

 

It looks like Spotify use Fastly as their CDN[6] and Fastly support HTTP/2[7] so this looks like a config change that could improve performance for everyone quite easily.

 

Thanks,
Reece

[1] https://developers.google.com/speed/pagespeed/insights

[2] https://developer.spotify.com/documentation/widgets/

[3] https://web.dev/uses-http2/?utm_source=lighthouse&utm_medium=devtools

[4] https://open.scdn.co/cdn/js/retargeting-pixels.62fc87d4.js

[5] https://i.scdn.co/image/ab67616d0000b273e37f4c90e212abccc90d0fd2

[6] https://engineering.atspotify.com/2020/02/24/how-spotify-aligned-cdn-services-for-a-lightning-fast-streaming-experience/

[7] https://www.fastly.com/blog/http2-now-general-availability

 

Child Item
Child Item
Child Item

Accepted answers

All comments

Agree. @Spotify should update this... The embed widgets are very slow.

Agreed!

 

This greatly affects the performance of everything using the Spotify CDN, including the Spotify product itself

Child Item
Child Item