47.8 sec in total
5.1 sec
42.5 sec
261 ms
Visit discovery.tom.com now to see the best up-to-date Discovery Tom content for China and also check out these interesting facts you probably never knew about discovery.tom.com
Visit discovery.tom.comWe analyzed Discovery.tom.com page load time and found that the first response time was 5.1 sec and then it took 42.8 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 were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
discovery.tom.com performance score
5051 ms
603 ms
19554 ms
794 ms
2222 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 71% of them (49 requests) were addressed to the original Discovery.tom.com, 4% (3 requests) were made to Nav2.tom.com and 4% (3 requests) were made to Tom.com. The less responsive or slowest element that took the longest time to load (19.6 sec) belongs to the original domain Discovery.tom.com.
Page size can be reduced by 119.4 kB (26%)
456.0 kB
336.5 kB
In fact, the total size of Discovery.tom.com main page is 456.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. 20% of websites need less resources to load. Images take 302.9 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.7 kB or 75% of the original size.
Potential reduce by 14.7 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. Discovery Tom images are well optimized though.
Potential reduce by 72.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 72.0 kB or 66% of the original size.
Potential reduce by 7.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. Discovery.tom.com needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 74% of the original size.
Number of requests can be reduced by 21 (50%)
42
21
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discovery Tom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
discovery.tom.com
5051 ms
css.css
603 ms
focus.js
19554 ms
ad_pl.js
794 ms
tomnav.css
2222 ms
pdnav2009.js
2224 ms
pdlogin.js
2223 ms
2013news_hp_fc1.js
4078 ms
ule_vw_ad.js
969 ms
footer.js
1918 ms
discovery_hp_fmt.js
19548 ms
k.js
3808 ms
ts1.jpg
854 ms
go.gif
292 ms
ts1.jpg
867 ms
ts1.jpg
583 ms
ts01.jpg
653 ms
ts-01.jpg
14098 ms
ts-1.jpg
1390 ms
ts-1.jpg
584 ms
ts-01.jpg
583 ms
listmore.gif
583 ms
img-1418246762594.jpg
584 ms
img-1418246402287.jpg
583 ms
img-1418160202766.jpg
583 ms
img-1418160089307.jpg
584 ms
img-1417814019771.jpg
583 ms
img-1417813917073.jpg
583 ms
img-1417226179593.jpg
583 ms
img-1417226496123.jpg
582 ms
img-1417226806965.jpg
583 ms
img-1417227261402.jpg
582 ms
img-1417227477310.jpg
582 ms
img-1417227798274.jpg
582 ms
img-1417227687853.jpg
582 ms
img-1409421998657.jpg
582 ms
img-1409421554086.jpg
581 ms
img-1409421502108.jpg
581 ms
img-1401867817890.jpg
580 ms
67.jpg
581 ms
66.jpg
581 ms
tomsubnav.gif
19 ms
ico.gif
18 ms
a.htm
1196 ms
r.js
3546 ms
tansuo.jpg
616 ms
hometop.gif
293 ms
focustop.gif
612 ms
focusbtm.gif
333 ms
arrow.gif
167 ms
t1.jpg
119 ms
b1.jpg
130 ms
b2.jpg
749 ms
b3.jpg
241 ms
b4.jpg
250 ms
t5.gif
261 ms
t6.gif
271 ms
t2.jpg
562 ms
t3.jpg
590 ms
b5.gif
560 ms
t4.jpg
857 ms
vwad.gif
2428 ms
b6.gif
855 ms
baidutj.js
777 ms
piwiktj.js
3838 ms
hm.js
450 ms
hm.gif
224 ms
piwik.js
1929 ms
piwik.php
282 ms
discovery.tom.com SEO score
ZH
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discovery.tom.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Discovery.tom.com main page’s claimed encoding is gbk. 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.
discovery.tom.com
Open Graph description is not detected on the main page of Discovery Tom. 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: