52.6 sec in total
4.8 sec
47.5 sec
306 ms
Welcome to elodestar.com homepage info - get ready to check Elodestar best content right away, or after learning these important things about elodestar.com
Visit elodestar.comWe analyzed Elodestar.com page load time and found that the first response time was 4.8 sec and then it took 47.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 41 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
elodestar.com performance score
4787 ms
1203 ms
991 ms
991 ms
4980 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 92% of them (69 requests) were addressed to the original Elodestar.com, 1% (1 request) were made to S20.cnzz.com and 1% (1 request) were made to Oz.cnzz.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Elodestar.com.
Page size can be reduced by 78.5 kB (22%)
349.0 kB
270.5 kB
In fact, the total size of Elodestar.com main page is 349.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. Only 10% of websites need less resources to load. Images take 295.4 kB which makes up the majority of the site volume.
Potential reduce by 22.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. This page needs HTML code to be minified as it can gain 7.4 kB, which is 28% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.0 kB or 83% of the original size.
Potential reduce by 37.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. Obviously, Elodestar needs image optimization as it can save up to 37.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 14.0 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 14.0 kB or 69% of the original size.
Potential reduce by 5.2 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. Elodestar.com needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 76% of the original size.
Number of requests can be reduced by 4 (13%)
32
28
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elodestar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
elodestar.com
4787 ms
All.css
1203 ms
font.css
991 ms
scroll.js
991 ms
jqqonline.js
4980 ms
index.js
1480 ms
stat.php
2358 ms
kefu.gif
2927 ms
china.gif
3130 ms
english.gif
3234 ms
20111226115614738.jpg
19625 ms
20111226114944395.JPG
5599 ms
20111226114950676.JPG
4282 ms
20111226114957535.JPG
19624 ms
20111226115626957.JPG
19625 ms
sbtn.gif
6850 ms
about_ld.jpg
7039 ms
product_center.jpg
19114 ms
media_center.jpg
12680 ms
customer_service.jpg
7426 ms
cargo_center.jpg
7817 ms
contact_us.jpg
8223 ms
left_bottom.jpg
9781 ms
list_bottom_right.jpg
10172 ms
copyright_logo.jpg
12792 ms
copyright_right.jpg
19625 ms
default.jsp
17949 ms
header.gif
19582 ms
current.png
19582 ms
line.gif
19584 ms
top.gif
19584 ms
search.gif
19585 ms
big_bg.jpg
19586 ms
left_bg.jpg
19587 ms
list_bottom.jpg
19587 ms
copyright_bg.jpg
19588 ms
stat.htm
184 ms
core.php
797 ms
9.gif
991 ms
app.gif
1814 ms
list_bg.jpg
9909 ms
index_bar_bg.jpg
7242 ms
new_pro.jpg
16089 ms
2011-11-14-104253_LD3801A.jpg
20285 ms
2012-01-03-140653_L214225.jpg
20286 ms
2011-12-06-170357_207190~1.JPG
20250 ms
2013-04-05-161654_L407022.jpg
19907 ms
2011-12-28-103357_G%20_l40801d.jpg
16069 ms
2011-12-05-152001_L40800B.jpg
19906 ms
2011-11-21-154950_LPS305DM.jpg
19908 ms
2013-12-26-120302_01.jpg
19913 ms
2013-07-03-113838_L215326.jpg
19733 ms
2013-02-25-101310_L502851.jpg
19734 ms
2013-02-23-165113_L502852.jpg
19734 ms
2012-04-20-084145_L107808~1.jpg
19734 ms
2012-01-03-150258_15.jpg
19736 ms
arrow.jpg
19736 ms
news.gif
19719 ms
bottom.gif
20354 ms
hot.gif
20354 ms
button_old_171.gif
491 ms
brand.jpg
19576 ms
20111024222335_pinpai01.gif
19653 ms
20111024222416_pinpai02.gif
19506 ms
20111024235541_pinpai03.gif
20003 ms
20111024235615_pinpai04.gif
19827 ms
20111024235647_pinpai05.gif
20000 ms
20111024235711_pinpai06.gif
20000 ms
20111024235753_pinpai07.gif
19999 ms
20111024235851_pinpai08.gif
19996 ms
20111024235933_pinpai09.gif
19997 ms
20111025000004_pinpai10.gif
19999 ms
20111025000029_pinpai11.gif
19998 ms
20111025000050_pinpai12.gif
19998 ms
hot_pro.gif
19997 ms
elodestar.com SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elodestar.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Elodestar.com main page’s claimed encoding is gb2312. 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.
elodestar.com
Open Graph description is not detected on the main page of Elodestar. 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: