Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

spotifycharts.com

Spotify Charts - Spotify Charts are made by fans

Page Load Speed

3.3 sec in total

First Response

141 ms

Resources Loaded

1.8 sec

Page Rendered

1.4 sec

spotifycharts.com screenshot

About Website

Welcome to spotifycharts.com homepage info - get ready to check Spotify Charts best content for Australia right away, or after learning these important things about spotifycharts.com

The new home for Spotify Charts. Dive into artist, genre, city and local pulse charts to see what music is moving fans around the world.

Visit spotifycharts.com

Key Findings

We analyzed Spotifycharts.com page load time and found that the first response time was 141 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

spotifycharts.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value39.1 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

spotifycharts.com

141 ms

analytics.js

6 ms

main.js

211 ms

78 ms

112 ms

Our browser made a total of 176 requests to load all elements on the main page. We found that 6% of them (10 requests) were addressed to the original Spotifycharts.com, 93% (164 requests) were made to I.scdn.co and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (386 ms) belongs to the original domain Spotifycharts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 620.6 kB (51%)

Content Size

1.2 MB

After Optimization

590.2 kB

In fact, the total size of Spotifycharts.com main page is 1.2 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. 40% of websites need less resources to load. Javascripts take 439.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 324.0 kB

  • Original 373.0 kB
  • After minification 372.9 kB
  • After compression 49.0 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 324.0 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 398.3 kB
  • After minification 398.3 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 Charts images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 296.6 kB

  • Original 439.5 kB
  • After minification 439.5 kB
  • After compression 142.9 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 296.6 kB or 67% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

171

After Optimization

171

The browser has sent 171 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spotify Charts. According to our analytics all requests are already optimized.

Accessibility Review

spotifycharts.com accessibility score

77

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

spotifycharts.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

spotifycharts.com SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spotifycharts.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Spotifycharts.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 Charts. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: