28.7 sec in total
284 ms
27.2 sec
1.2 sec
Click here to check amazing Musicdb content. Otherwise, check out these important facts you probably never knew about musicdb.co
musicdb, the world's most comprehensive and authoritative source for music, information and content
Visit musicdb.coWe analyzed Musicdb.co page load time and found that the first response time was 284 ms and then it took 28.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
musicdb.co performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value2.9 s
82/100
25%
Value2.5 s
98/100
10%
Value60 ms
100/100
30%
Value0.029
100/100
15%
Value2.9 s
96/100
10%
284 ms
444 ms
270 ms
3087 ms
5728 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 17% of them (22 requests) were addressed to the original Musicdb.co, 29% (36 requests) were made to Static.xx.fbcdn.net and 12% (15 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Musicdb.co.
Page size can be reduced by 457.3 kB (48%)
953.0 kB
495.7 kB
In fact, the total size of Musicdb.co main page is 953.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 310.9 kB which makes up the majority of the site volume.
Potential reduce by 124.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 124.8 kB or 81% of the original size.
Potential reduce by 4.5 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. Musicdb images are well optimized though.
Potential reduce by 129.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 129.1 kB or 53% of the original size.
Potential reduce by 198.8 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. Musicdb.co needs all CSS files to be minified and compressed as it can save up to 198.8 kB or 81% of the original size.
Number of requests can be reduced by 62 (58%)
106
44
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Musicdb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.musicdb.co
284 ms
css
444 ms
ga.js
270 ms
musicdb.min.css
3087 ms
musicdb_bootstrap.min.css
5728 ms
styles.less
5658 ms
icons.css
717 ms
star-rating.min.css
1167 ms
pinit.js
208 ms
jquery-2.1.4.min.js
453 ms
jquery.tempgauge.min.js
1155 ms
jquery.min.js
737 ms
typeahead.bundle.min.js
361 ms
application-3009048f3bf0a64af3f8c42af237bb94.js
5841 ms
bootstrap.min.js
403 ms
modernizr.js
19759 ms
chart.min.js
1264 ms
studio.js
348 ms
icon
517 ms
font-awesome.min.css
400 ms
q
199 ms
analytics.js
78 ms
584968
517 ms
logo_red_2.png
967 ms
6784584
481 ms
435348
327 ms
4859427
768 ms
226816
478 ms
1295533
299 ms
5998905
921 ms
6314279
547 ms
sdk.js
385 ms
pinit_main.js
153 ms
collect
70 ms
collect
1749 ms
279 ms
xd_arbiter.php
277 ms
xd_arbiter.php
1022 ms
ga-audiences
281 ms
font-awesome.min.css
174 ms
proximanova-semibold-webfont.woff
49 ms
dropdown-arrow-down-007c07dc276dae4f5d7420af265d40a3d887b10add9e2e972f21a0ccd76213af.png
251 ms
dropdown-arrow-down-007c07dc276dae4f5d7420af265d40a3d887b10add9e2e972f21a0ccd76213af.png
250 ms
widgets.js
248 ms
fontawesome-webfont.woff
473 ms
fontawesome-webfont.woff
245 ms
youtube_proxy_source
515 ms
youtube_proxy_source
4849 ms
youtube_proxy_source
4845 ms
youtube_proxy_source
2777 ms
youtube_proxy_source
4845 ms
youtube_proxy_source
2777 ms
youtube_proxy_source
4847 ms
youtube_proxy_source
4706 ms
youtube_proxy_source
4818 ms
comments.php
607 ms
comments.php
573 ms
comments.php
3236 ms
comments.php
330 ms
comments.php
5073 ms
comments.php
338 ms
comments.php
485 ms
comments.php
480 ms
comments.php
607 ms
comments.php
655 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
223 ms
xd_arbiter.php
182 ms
page.php
1205 ms
4zvF1Y0eZKv.css
364 ms
FrSU6IlfEX1.css
456 ms
1YCjbvlQvop.css
970 ms
K4OnSbts6xo.css
1002 ms
SRSW8M763HA.js
1096 ms
ullQFyhrQFI.js
1290 ms
y97Ig99UVTs.js
938 ms
rR4Qw0p7TFQ.js
1731 ms
ULtnh-HfQSw.js
1088 ms
Cw6QosZRsiU.js
1287 ms
FOagnU9QnXq.js
1287 ms
O3W7iparFI2.js
1485 ms
dt0QadAXRnm.js
1408 ms
KanoMJZ9xtG.js
1403 ms
ye4Amg-qrtc.js
2098 ms
d_-F4IIjJo3.js
1405 ms
3poIqqWXpbT.js
1407 ms
KHAtULXOQuz.js
1408 ms
syndication
327 ms
670667033109991424
523 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
60 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
141 ms
8SkTmSEa_normal.png
726 ms
CYvrBTVWcAEvSlO.png
2782 ms
5IbuNoOZgHx.css
709 ms
GZeiuqs6M9H.css
458 ms
6IFzBT9uHU-.js
2139 ms
Gqzx6edLp88.js
531 ms
HQR5HcLW5FK.js
614 ms
XlY_wsDnClE.js
1767 ms
i8XO-4kv8i7.js
1123 ms
z5eMxBRE-Ji.js
1124 ms
7YklgZdHLYS.js
1125 ms
jot
96 ms
fav.png
175 ms
odA9sNLrE86.jpg
176 ms
wL6VQj7Ab77.png
177 ms
gm-8CYVMZ_l.png
176 ms
VXcANLwwL5J.js
230 ms
12522964_660594780748357_6036901139274254748_n.png
3011 ms
946799_659852837489218_1247543030460092242_n.png
1256 ms
1JLnMyDN79z.png
171 ms
336 ms
560 ms
FASTu8Ostla.png
155 ms
b53Ajb4ihCP.gif
196 ms
css;base64,
2 ms
gxZYrzUnHwF.css
77 ms
W4NL_XloU4d.js
80 ms
12226939_10153471094122771_7487464602355677698_n.jpg
398 ms
11796386_680817316103_3803967913282577006_n.jpg
398 ms
1800282_10152361743112261_7972863925166694908_n.jpg
441 ms
10590643_10152522019760067_4841036336793796593_n.jpg
534 ms
12552856_10208808619833391_4500549058269891427_n.jpg
497 ms
10444721_10154238352255188_2005840489235511334_n.jpg
559 ms
11138066_10153228546610240_439069050926511634_n.jpg
534 ms
988379_10153561213880341_1049611695_n.jpg
580 ms
collect
138 ms
musicdb.co 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.
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
<frame> or <iframe> elements do not have a title
musicdb.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
musicdb.co 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Musicdb.co 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 Musicdb.co 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.
musicdb.co
Open Graph data is detected on the main page of Musicdb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: