765 ms in total
9 ms
518 ms
238 ms
Visit setlist.fm now to see the best up-to-date Setlist content for United States and also check out these interesting facts you probably never knew about setlist.fm
Over 7,850,000 concert setlists of more than 353,600 artists including tour and song statistics, personal statistics, videos and much more.
Visit setlist.fmWe analyzed Setlist.fm page load time and found that the first response time was 9 ms and then it took 756 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
setlist.fm performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value7.2 s
5/100
25%
Value7.3 s
29/100
10%
Value1,130 ms
22/100
30%
Value0.018
100/100
15%
Value14.7 s
8/100
10%
9 ms
125 ms
85 ms
45 ms
38 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 8% of them (4 requests) were addressed to the original Setlist.fm, 37% (19 requests) were made to I1.cdn.setlistfm.com and 25% (13 requests) were made to S1.cdn.setlistfm.com. The less responsive or slowest element that took the longest time to load (160 ms) relates to the external source Cdn.krxd.net.
Page size can be reduced by 1.2 MB (53%)
2.2 MB
1.0 MB
In fact, the total size of Setlist.fm main page is 2.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. 65% of websites need less resources to load. Javascripts take 884.4 kB which makes up the majority of the site volume.
Potential reduce by 178.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 178.7 kB or 74% of the original size.
Potential reduce by 31.4 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. Setlist images are well optimized though.
Potential reduce by 619.4 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 619.4 kB or 70% of the original size.
Potential reduce by 342.7 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. Setlist.fm needs all CSS files to be minified and compressed as it can save up to 342.7 kB or 84% of the original size.
Number of requests can be reduced by 13 (28%)
47
34
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Setlist. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
setlist.fm
9 ms
www.setlist.fm
125 ms
css
85 ms
setlist-2.0.378-dirty.css
45 ms
wicket-1.4.23-molindo1.js
38 ms
jquery.min.js
61 ms
jquery-migrate-1.1.1.min.js
4 ms
setlist-jquery-2.0.378-dirty.js
37 ms
jquery-ui.min.js
72 ms
jquery-ui.css
76 ms
jquery-plugins-2.0.378-dirty.js
41 ms
setlist-2.0.378-dirty.js
36 ms
3082580109.js
128 ms
react.js
27 ms
controltag
160 ms
gpt.js
159 ms
ga.js
157 ms
sfm-logo.png
157 ms
samsung-footer.png
157 ms
2bd6dcce.jpg
130 ms
beacon.js
119 ms
logo-samsung-horiz.png
16 ms
sfm-start.jpg
44 ms
sfm-search-icon-white.svg
17 ms
close-dark.svg
20 ms
sfm-stats.png
18 ms
sfm-badge.png
21 ms
3bd6803c.jpg
19 ms
bd6ad22.jpg
21 ms
23d6807b.jpg
21 ms
53d6ebd5.jpg
41 ms
7bd3caf0.jpg
19 ms
bd6bdbe.jpg
40 ms
1bd6a5b4.jpg
40 ms
2bd6b8d2.jpg
41 ms
3bd680c8.jpg
39 ms
2bd6d836.jpg
41 ms
33d6bc71.jpg
44 ms
bd6bd2a.jpg
43 ms
4bd6bfea.jpg
43 ms
6bdc6e66.jpg
43 ms
7bd6be40.jpg
43 ms
13d69909.jpg
43 ms
7bd4e228.jpg
47 ms
23d6b80b.jpg
45 ms
Xyjz-jNkfiYuJf8UC3Lizw.woff
54 ms
oOeFwZNlrTefzLYmlVV1UD8E0i7KZn-EPnyo3HZu7kw.woff
55 ms
fontawesome-webfont-4.4.0.woff
47 ms
__utm.gif
73 ms
pubads_impl_81.js
21 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
69 ms
container.html
31 ms
setlist.fm accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
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
setlist.fm 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
Page has valid source maps
setlist.fm SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Setlist.fm 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 Setlist.fm 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.
setlist.fm
Open Graph description is not detected on the main page of Setlist. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: