12.4 sec in total
516 ms
10.4 sec
1.5 sec
Click here to check amazing Tom content for China. Otherwise, check out these important facts you probably never knew about tom.com
Visit tom.comWe analyzed Tom.com page load time and found that the first response time was 516 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tom.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value16.8 s
0/100
25%
Value7.5 s
27/100
10%
Value7,680 ms
0/100
30%
Value0.514
15/100
15%
Value15.6 s
6/100
10%
516 ms
1815 ms
275 ms
549 ms
821 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 49% of them (35 requests) were addressed to the original Tom.com, 32% (23 requests) were made to Imgs.tom.com and 7% (5 requests) were made to Qq.weatherol.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Webapi.amap.com.
Page size can be reduced by 265.9 kB (23%)
1.2 MB
913.1 kB
In fact, the total size of Tom.com main page is 1.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. 60% of websites need less resources to load. Images take 777.8 kB which makes up the majority of the site volume.
Potential reduce by 217.5 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 217.5 kB or 83% of the original size.
Potential reduce by 34.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. Tom images are well optimized though.
Potential reduce by 12.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 12.4 kB or 11% of the original size.
Potential reduce by 1.5 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. Tom.com has all CSS files already compressed.
Number of requests can be reduced by 18 (27%)
66
48
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tom.com
516 ms
www.tom.com
1815 ms
2021bootstrap.min.css
275 ms
2021shouye.min.css
549 ms
jquery-3.2.1.min.js
821 ms
bootstrap.min.js
838 ms
jquery.lazyload.js
1082 ms
jquery.cookie.min.js
1116 ms
headroom.min.js
1117 ms
jQuery.headroom.min.js
1115 ms
masonry.pkgd.min.js
1089 ms
imagesloaded.pkgd.min.js
1109 ms
readjson-pc20180903.js
1355 ms
get_track.min.js
1340 ms
maps
4537 ms
jquery.cookie.min.js
1293 ms
2475 ms
tomcss_sprites.png
1884 ms
logotom.png
1885 ms
line_1.png
1886 ms
white_lazy.png
1885 ms
g-a.png
1898 ms
pic02.jpg
1898 ms
1232l-j.png
1897 ms
pic03.gif
1897 ms
content_bottom_box_line.png
1897 ms
modules
887 ms
init
1006 ms
weatherWidget.css
686 ms
base.css
687 ms
d00.png
727 ms
getPlugIns
727 ms
d00.png
921 ms
THUMBNAILb5aa916d4b79343f.jpg
1394 ms
qcgs.jpg
274 ms
init
933 ms
modules
324 ms
nfylw.png
286 ms
zgwhcmw.jpg
268 ms
ylzg.png
282 ms
syqzw.jpg
284 ms
39jkw.png
289 ms
qdzg.png
532 ms
93913.png
520 ms
xcsx.png
555 ms
xzj.png
602 ms
rdkj.png
592 ms
ydd.png
597 ms
THUMBNAIL71E3AF0AF8534737.jpg
1442 ms
THUMBNAIL9be6e4beaade1cc7.jpg
1441 ms
CONTENTE0209379E68A4A34.jpg
1477 ms
THUMBNAILbc6bca6e91622f6f.jpg
1488 ms
THUMBNAIL0ed4a0721fdc8c9c.jpg
1455 ms
CONTENTCCBAF2863FDE4AFF.jpg
1636 ms
THUMBNAILF1C3268926C348EF.jpg
1737 ms
THUMBNAILA37D6847363B4190.jpg
1731 ms
THUMBNAILf951cd3e8e0003f1.jpg
1760 ms
THUMBNAIL8e2e009865b63f01.jpg
1778 ms
THUMBNAILaa6f941ab2a46fd6.jpg
1794 ms
THUMBNAIL7ee8c5b84135142f.jpg
1901 ms
THUMBNAIL21a21b1de0d0d5c4.jpg
2243 ms
THUMBNAILb6036f8508b3dd08.jpg
2087 ms
THUMBNAILF712D7AF71FE4BC8.jpg
2053 ms
THUMBNAILf11884705a5046c4.jpg
2168 ms
THUMBNAILed6daac1d2e10e1a.jpg
2094 ms
THUMBNAILC1A90A39549A45A7.jpg
2252 ms
THUMBNAIL538782aa71000e35.jpg
2411 ms
THUMBNAIL7428a814951f2125.jpg
2410 ms
THUMBNAILAC6D1E4A1C334BD4.jpg
2434 ms
THUMBNAIL9da7356ded00a947.jpg
2508 ms
ipLocation
332 ms
searchCity
958 ms
tom.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
Links do not have a discernible name
tom.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
tom.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 Tom.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.
tom.com
Open Graph data is detected on the main page of Tom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: