6.3 sec in total
616 ms
5.4 sec
265 ms
Visit eclassical.com now to see the best up-to-date EClassical content for China and also check out these interesting facts you probably never knew about eclassical.com
Download Classical Music in lossless High Resolution FLAC & MP3 formats, and learn about Classical Music. Refund Policy, No DRM protection and pricing is per second.
Visit eclassical.comWe analyzed Eclassical.com page load time and found that the first response time was 616 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eclassical.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.8 s
7/100
25%
Value8.3 s
20/100
10%
Value730 ms
40/100
30%
Value0.003
100/100
15%
Value7.2 s
51/100
10%
616 ms
302 ms
212 ms
642 ms
352 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 57% of them (45 requests) were addressed to the original Eclassical.com, 13% (10 requests) were made to Static.xx.fbcdn.net and 11% (9 requests) were made to Ecstatic.textalk.se. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Eclassical.textalk.se.
Page size can be reduced by 486.4 kB (32%)
1.5 MB
1.1 MB
In fact, the total size of Eclassical.com main page is 1.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. 40% of websites need less resources to load. Images take 905.1 kB which makes up the majority of the site volume.
Potential reduce by 42.9 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 42.9 kB or 79% of the original size.
Potential reduce by 20.8 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. EClassical images are well optimized though.
Potential reduce by 355.8 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 355.8 kB or 72% of the original size.
Potential reduce by 67.0 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. Eclassical.com needs all CSS files to be minified and compressed as it can save up to 67.0 kB or 84% of the original size.
Number of requests can be reduced by 25 (32%)
77
52
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EClassical. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.eclassical.com
616 ms
webshop.css.php
302 ms
dtree.css
212 ms
Shop.min.js
642 ms
template.js.php
352 ms
cookie.js
274 ms
url.js
364 ms
jquery.expander.js
311 ms
jquery.scrollTo.js
386 ms
jquery.url.packed.js
408 ms
jquery.nivo.slider.pack.js
415 ms
17115-fieldbgupper-048445.png
130 ms
17116-log-e4882e.png
123 ms
17115-2728994-shopw-9066a2.png
121 ms
17115-2728994-shopw-5c7e30.png
123 ms
17115-2728994-shopw-cd2c02.png
121 ms
17116-fieldbgtop-e1ce17.png
123 ms
ec-button_ok.png
210 ms
all.js
83 ms
17115-fieldbgleft-2270bb.png
210 ms
17115-2728994-shopw-4e6451.png
217 ms
17115-2728994-shopw-94e19a.png
217 ms
17115-2728994-shopw-1a480e.png
214 ms
17116-2747761-shopw-c280be.jpg
2210 ms
4971450-origpic-cac586.jpg_0_0_100_100_250_250_0.jpg
974 ms
17116-2746983-shopw-53b82e.png
434 ms
p.gif
294 ms
4969410-origpic-484c79.jpg_0_0_100_100_143_143_0.jpg
305 ms
4975672-origpic-7bdf6e.jpg_0_0_100_100_143_141_0.jpg
339 ms
4975601-origpic-c1b528.jpg_0_0_100_100_143_143_0.jpg
338 ms
4975591-origpic-76c5d8.jpg_0_0_100_100_143_143_0.jpg
340 ms
4975472-origpic-b97a68.jpg_0_0_100_100_143_143_0.jpg
399 ms
4975470-origpic-4e8792.jpg_0_0_100_100_143_141_0.jpg
411 ms
4975055-origpic-56a1f3.jpg_0_0_100_100_143_143_0.jpg
970 ms
4975019-origpic-094a63.jpg_0_0_100_100_143_143_0.jpg
970 ms
17115-fieldbgright-a547b3.png
974 ms
4971489-origpic-93cce9.jpg_0_0_100_100_250_250_0.jpg
968 ms
4973696-origpic-a90eb7.png_0_0_100_100_250_250_0.png
1410 ms
4971459-origpic-2ae520.jpg_0_0_100_100_250_250_0.jpg
1088 ms
4972960-origpic-602a8a.png_0_0_100_100_250_250_0.png
1626 ms
4972956-origpic-364684.png_0_0_100_100_250_247_0.png
2091 ms
4972885-origpic-f694b7.png_0_0_100_100_250_250_0.png
1455 ms
4972880-origpic-9b0224.png_0_0_100_100_250_247_0.png
1384 ms
54167-ban-181c0e.jpg
1309 ms
17116-2747761-shopw-b6c50a.jpg
2380 ms
17116-2746983-shopw-22b506.png
1969 ms
4930827-origpic-78fcc6.jpg_0_0_100_100_50_50_0.jpg
958 ms
4935096-origpic-a24807.png_0_0_100_100_50_50_0.png
1056 ms
4951435-origpic-83f7cb.png_0_0_100_100_50_50_0.png
961 ms
statisticsLink.png
1067 ms
4961751-origpic-80014a.jpg_0_0_100_100_50_50_0.jpg
1963 ms
4967798-origpic-cf77af.png_0_0_100_100_50_50_0.png
1955 ms
4965572-origpic-64fc89.jpg_0_0_100_100_50_50_0.jpg
1966 ms
17116-fieldbglower-e1b5fd.png
1965 ms
ga.js
29 ms
17115-2728994-shopw-f68a08.png
1941 ms
ui-bg_flat_75_ffffff_40x100.png
1157 ms
__utm.gif
33 ms
174 ms
xd_arbiter.php
79 ms
xd_arbiter.php
137 ms
arrows.png
115 ms
bullets.png
111 ms
like_box.php
148 ms
jTuqQ-OPDr6.css
79 ms
n370yiaI2G6.css
97 ms
mqajJoRXkq3.js
134 ms
x5F9OMjKyLw.js
164 ms
ICDbTSzjQEg.js
157 ms
TTCre3391I0.js
132 ms
20784_797883283613023_3993273375119959800_n.jpg
90 ms
318567_197182117016479_930248368_n.jpg
78 ms
1477377_10152501273432846_1637762670_n.jpg
79 ms
1922225_600609030010953_380820144_n.jpg
89 ms
559860_10200817874747272_709122688_n.jpg
90 ms
wL6VQj7Ab77.png
22 ms
s7jcwEQH7Sx.png
22 ms
I6-MnjEovm5.js
21 ms
vlXaquuXMrr.js
44 ms
eclassical.com 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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
eclassical.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eclassical.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eclassical.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 Eclassical.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.
eclassical.com
Open Graph description is not detected on the main page of EClassical. 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: