40 sec in total
368 ms
29.8 sec
9.8 sec
Welcome to spotify.com homepage info - get ready to check Spotify best content for United States right away, or after learning these important things about spotify.com
Spotify is a digital music service that gives you access to millions of songs.
Visit spotify.comWe analyzed Spotify.com page load time and found that the first response time was 368 ms and then it took 39.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
spotify.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.0 s
2/100
25%
Value10.7 s
7/100
10%
Value5,830 ms
0/100
30%
Value0.033
100/100
15%
Value19.8 s
2/100
10%
368 ms
576 ms
166 ms
2350 ms
3130 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Spotify.com, 27% (17 requests) were made to Scdn.co and 9% (6 requests) were made to Sp-bootstrap.global.ssl.fastly.net. The less responsive or slowest element that took the longest time to load (10.7 sec) relates to the external source D2oh4tlt9mrke9.cloudfront.net.
Page size can be reduced by 1.4 MB (48%)
2.8 MB
1.5 MB
In fact, the total size of Spotify.com main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 959.2 kB which makes up the majority of the site volume.
Potential reduce by 45.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.8 kB or 71% of the original size.
Potential reduce by 611 B
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Spotify images are well optimized though.
Potential reduce by 560.8 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 560.8 kB or 61% of the original size.
Potential reduce by 751.6 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Spotify.com needs all CSS files to be minified and compressed as it can save up to 751.6 kB or 84% of the original size.
Number of requests can be reduced by 39 (71%)
55
16
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spotify. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
spotify.com
368 ms
www.spotify.com
576 ms
166 ms
jquery-2-55dbf677db.1.3.min.js
2350 ms
spotify-ab3546c370.css
3130 ms
index-212b50cb38.css
2348 ms
modernizr-bc8113e41c.js
2348 ms
tracking-83d1c649be.download.js
2347 ms
spweb-site-d48e84584e.min.js
3091 ms
tour-7b483d8e67.js
3091 ms
bon-32c3a6a7e1.js
3091 ms
vt-150.js
4383 ms
analytics.js
3239 ms
gtm.js
3189 ms
sp-analytics-a3e2493d01.js
1580 ms
us.svg
2591 ms
hero-burst.svg
2768 ms
carousel-chevron.svg
3206 ms
hero-burst-easy.svg
3207 ms
your_daily_mix.jpg
3210 ms
your_release_radar.jpg
3318 ms
all-devicesAB.svg
3207 ms
plan-checklist.svg
3318 ms
plan-checklist-free.svg
3319 ms
js
546 ms
circular-book.woff
2508 ms
circular-medium.woff
3907 ms
circular-light.woff
7186 ms
circular-bold.woff
7270 ms
circular-black.woff
8560 ms
linkid.js
2938 ms
fbevents.js
8833 ms
uwt.js
10268 ms
sessioncam.recorder.js
10714 ms
ytc.js
8936 ms
beacon.js
10433 ms
activityi;src=4721227;type=uidfq0;cat=spoti0;u2=f3b00f9a33b9b002bf3e0223d5da3663;ord=6041093213577;~oref=https%3A%2F%2Fwww.spotify.com%2Fus%2F
10050 ms
e23adf2ed8c7c2c1003735642ef5779adb2e21c6
7986 ms
d83a086148afe6539dae524607cbe4b6ccdd0360
6618 ms
d30f10db04a3303623d70d7d930da769f5590019
7727 ms
8d63ab6a74d9a77d723e79f95faa3be5615c85ae
7734 ms
1483047915331997
1575 ms
tr
4097 ms
oct.js
1447 ms
adsct
4564 ms
adsct
4564 ms
sync
1842 ms
4120 ms
config.aspx
3903 ms
conversion.js
3236 ms
3618 ms
adsct
3539 ms
ga-audiences
1235 ms
420356.gif
890 ms
1x1.jpg
1633 ms
tpid=7f010c7d-0fe8-4e46-8bb3-54102b2359e9
564 ms
21398
1404 ms
1611 ms
sync
210 ms
bat.js
989 ms
38 ms
adsct
477 ms
adsct
476 ms
adsct
457 ms
spotify.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
spotify.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
spotify.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spotify.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Spotify.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
spotify.com
Open Graph data is detected on the main page of Spotify. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: