Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

spotify.com

Spotify - Web Player: Music for everyone

Page Load Speed

40 sec in total

First Response

368 ms

Resources Loaded

29.8 sec

Page Rendered

9.8 sec

spotify.com screenshot

About Website

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.com

Key Findings

We 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.

Performance Metrics

spotify.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value5,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (48%)

Content Size

2.8 MB

After Optimization

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.

HTML Optimization

-71%

Potential reduce by 45.8 kB

  • Original 64.5 kB
  • After minification 58.0 kB
  • After compression 18.7 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.

Image Optimization

-0%

Potential reduce by 611 B

  • Original 959.2 kB
  • After minification 958.6 kB

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.

JavaScript Optimization

-61%

Potential reduce by 560.8 kB

  • Original 916.3 kB
  • After minification 915.6 kB
  • After compression 355.5 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.

CSS Optimization

-84%

Potential reduce by 751.6 kB

  • Original 895.1 kB
  • After minification 894.8 kB
  • After compression 143.5 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.

Requests Breakdown

Number of requests can be reduced by 39 (71%)

Requests Now

55

After Optimization

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.

Accessibility Review

spotify.com accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

spotify.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

spotify.com SEO score

99

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: