2.8 sec in total
38 ms
2.1 sec
676 ms
Click here to check amazing Shazam content for United States. Otherwise, check out these important facts you probably never knew about shazam.com
Identify the music playing around you. Explore the music you love. Discover songs, lyrics, and artists on Shazam.
Visit shazam.comWe analyzed Shazam.com page load time and found that the first response time was 38 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
shazam.com performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value8.9 s
1/100
25%
Value5.9 s
48/100
10%
Value330 ms
76/100
30%
Value0
100/100
15%
Value8.9 s
35/100
10%
38 ms
560 ms
226 ms
36 ms
30 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 13% of them (18 requests) were addressed to the original Shazam.com, 35% (50 requests) were made to Images.shazam.com and 8% (11 requests) were made to S0.2mdn.net. The less responsive or slowest element that took the longest time to load (799 ms) belongs to the original domain Shazam.com.
Page size can be reduced by 1.0 MB (29%)
3.5 MB
2.5 MB
In fact, the total size of Shazam.com main page is 3.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 261.2 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 261.2 kB or 76% of the original size.
Potential reduce by 1.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. Shazam images are well optimized though.
Potential reduce by 566.1 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 566.1 kB or 66% of the original size.
Potential reduce by 192.3 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. Shazam.com needs all CSS files to be minified and compressed as it can save up to 192.3 kB or 71% of the original size.
Number of requests can be reduced by 62 (45%)
138
76
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shazam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
shazam.com
38 ms
www.shazam.com
560 ms
webfont.js
226 ms
base-85e0b8e5.css
36 ms
home-90fbde05.css
30 ms
almondbundle-c718fec0.js
84 ms
home-339c32d2.js
100 ms
640x360
170 ms
640x360
156 ms
a115_s400.jpg
153 ms
t283701800-i1051437168_s100b6.jpg
150 ms
t258710574-i974485474_s400.jpg
154 ms
t297103602-i1058093278_s400.jpg
155 ms
t266238057-i1081573445_s400.jpg
158 ms
a40561460_s400.jpg
155 ms
t312798409-i1087165451_s100b6.jpg
156 ms
640x360
160 ms
a5759203_s400.jpg
156 ms
t52679003-i385560939_s100b6.jpg
157 ms
640x360
162 ms
a42187177_s400.jpg
159 ms
t311980378_s100b6.jpg
157 ms
a42140149_s400.jpg
158 ms
t276325693-i941079447_s100b6.jpg
159 ms
640x360
160 ms
logo-faf60b67.png
31 ms
logo-alt-f0c88532.png
30 ms
shazam-com-masthead.jpg
162 ms
stars-a70dd4cf.png
30 ms
mobile_ios_and_android-72a04dcf.png
148 ms
itunes_en-b558b923.png
143 ms
apple_en-40ae1615.png
139 ms
GooglePlay-0d4c5617.png
144 ms
amazon_short-4f397896.png
145 ms
juno-e93581b6.png
145 ms
logo-footer-11c35103.png
145 ms
dc.js
121 ms
all.js
272 ms
feed
799 ms
gpt.js
40 ms
t283701800-i1051437168_s400.jpg
56 ms
t312798409-i1087165451_s400.jpg
57 ms
t52679003-i385560939_s400.jpg
57 ms
movie_anthems_background_w192.jpg
58 ms
future_hits_of_tomorrow_background_w192.jpg
57 ms
how_many_top_shazamed_tracks_can_you_name_background_w192.jpg
57 ms
t311980378_s400.jpg
58 ms
t276325693-i941079447_s400.jpg
58 ms
__utm.gif
36 ms
pubads_impl_81.js
8 ms
ads
268 ms
container.html
20 ms
57 ms
xd_arbiter.php
215 ms
xd_arbiter.php
422 ms
13928.js
29 ms
osd.js
10 ms
sync
18 ms
320074-15.js
168 ms
0RMLDJXEOi_1158432801.html
14 ms
emily.html
16 ms
cl
48 ms
creative_add_on.js
81 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
31 ms
lidar.js
30 ms
analytics.js
73 ms
controltag
72 ms
smart_tag.js
297 ms
rs.js
79 ms
g-3147.xgi
79 ms
index.html
48 ms
loaded.js
147 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
145 ms
DcmEnabler_01_90.js
114 ms
a40222110_s400.jpg
120 ms
a40632370_s400.jpg
32 ms
a40663162_s400.jpg
28 ms
640x360
85 ms
a41670029_s400.jpg
31 ms
640x360
31 ms
a42790090_s400.jpg
30 ms
640x360
85 ms
a40045045_s400.jpg
82 ms
a33281_s400.jpg
82 ms
t312612832-i1083965398_s400.jpg
80 ms
t311412999-i1083054695_s400.jpg
83 ms
t311926946-i1083723617_s400.jpg
85 ms
t278340546-i1054369840_s400.jpg
85 ms
t311381691-i1082866701_s400.jpg
87 ms
t49543317-i655136801_s400.jpg
86 ms
t300945736-i1053934844_s400.jpg
89 ms
t312612832-i1083965398_s100b6.jpg
88 ms
t311412999-i1083054695_s100b6.jpg
89 ms
t311926946-i1083723617_s100b6.jpg
93 ms
t278340546-i1054369840_s100b6.jpg
90 ms
t311381691-i1082866701_s100b6.jpg
90 ms
t49543317-i655136801_s100b6.jpg
91 ms
t300945736-i1053934844_s100b6.jpg
92 ms
fabric_swatch.png
65 ms
postback
72 ms
rpc.flow
53 ms
vce_st.js
17 ms
surly.js
30 ms
a.gif
45 ms
btn-replay-24.png
6 ms
cta-txt-24.png
38 ms
logo-24.png
45 ms
violator_1.png
47 ms
txt2-8.png
49 ms
txt1-8.png
47 ms
bg_0.jpg
48 ms
p2
38 ms
p
25 ms
p
29 ms
ba.html
23 ms
cms-2c.html
51 ms
postback
20 ms
4.gif
15 ms
2532.js
6 ms
2964
27 ms
Pug
26 ms
rum
24 ms
sync
10 ms
pixel
39 ms
pixel.gif
22 ms
demconf.jpg
19 ms
rum
12 ms
tap.php
10 ms
385636.gif
12 ms
m.gif
8 ms
rs
11 ms
match-result
44 ms
sd
34 ms
postback
25 ms
m_yahoo.gif
7 ms
get
65 ms
optout_check
31 ms
box_19_top-right.png
27 ms
__utm.gif
22 ms
ci.png
7 ms
xd_arbiter.php
136 ms
activeview
28 ms
shazam.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
shazam.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
shazam.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shazam.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Shazam.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
shazam.com
Open Graph data is detected on the main page of Shazam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: