15.6 sec in total
869 ms
14 sec
742 ms
Click here to check amazing Tz 100 content for China. Otherwise, check out these important facts you probably never knew about tz100.com
购物优惠精选 - 淘者 - 高性价比网购推荐
Visit tz100.comWe analyzed Tz100.com page load time and found that the first response time was 869 ms and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tz100.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value5.8 s
15/100
25%
Value11.3 s
5/100
10%
Value10 ms
100/100
30%
Value0.016
100/100
15%
Value10.1 s
26/100
10%
869 ms
1140 ms
812 ms
1359 ms
548 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 29% of them (23 requests) were addressed to the original Tz100.com, 14% (11 requests) were made to Img4.tz100.com and 9% (7 requests) were made to Img2.tz100.com. The less responsive or slowest element that took the longest time to load (9.8 sec) relates to the external source Widget.weibo.com.
Page size can be reduced by 323.6 kB (15%)
2.1 MB
1.8 MB
In fact, the total size of Tz100.com main page is 2.1 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 108.2 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 22.0 kB, which is 17% 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 108.2 kB or 83% of the original size.
Potential reduce by 17.3 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. Tz 100 images are well optimized though.
Potential reduce by 153.6 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 153.6 kB or 63% of the original size.
Potential reduce by 44.6 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. Tz100.com needs all CSS files to be minified and compressed as it can save up to 44.6 kB or 79% of the original size.
Number of requests can be reduced by 28 (36%)
78
50
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tz 100. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
tz100.com
869 ms
www.tz100.com
1140 ms
style.css
812 ms
jquery.min.js
1359 ms
jquery.lazyload.min.js
548 ms
show_ads.js
18 ms
stat.php
964 ms
followbutton.php
9824 ms
d9afa9cc58bc11e4a3bf002274e0634d.png!161
5790 ms
8ec9b5cedf5711e5ad0d00163e000be0.png!161
6037 ms
1d7d9e18df5111e5ad0d00163e000be0.png!161
5566 ms
d320b282df4c11e5ad0d00163e000be0.png!161
5559 ms
d4f4d690ab7311e5ad0d00163e000be0.png!161
5554 ms
logo8.png
265 ms
searchbox.png
267 ms
searchbtn.png
266 ms
xia.gif
268 ms
bg.png
524 ms
rss1.png
523 ms
bdshare19.png
525 ms
category_bg_l1.png
524 ms
category_bg1.png
525 ms
type.jpg
527 ms
category_bg_r1.png
784 ms
commend.png
783 ms
btn_add_cart2.gif
789 ms
grey.gif
789 ms
thumbup_small.gif
790 ms
thumbdown_small.gif
806 ms
hot_flag.png
1049 ms
3c5ef8c6df4d11e5ad0d00163e000be0.jpg!161
5556 ms
b1e7b6e6debc11e5ad0d00163e000be0.png!80
5540 ms
1dbec46669e711e2b346123a45dddc8a.jpg!80
5540 ms
ab194186188911e49461002274e0634d.jpg!80
5553 ms
8ec9b5cedf5711e5ad0d00163e000be0.png!650
5991 ms
b3adec72c20f11e4ad0d00163e000be0.png!161
5556 ms
743f7f92d0a611e4ad0d00163e000be0.png!161
5546 ms
0e5572186a3e11e5ad0d00163e000be0.png!161
5556 ms
fcb4e10c578111e5ad0d00163e000be0.png!161
5556 ms
e90e9e7cab7311e5ad0d00163e000be0.jpg%21650
5564 ms
2b1f14bedf4411e5ad0d00163e000be0.gif!161
5568 ms
36704d3adec511e5ad0d00163e000be0.png!80
5566 ms
e1637478dee411e5ad0d00163e000be0.png!80
5566 ms
b2ea897e665e11e4b6d2002274e0634d.png!80
5571 ms
eef1af82df5811e5ad0d00163e000be0.png!161
5995 ms
e397ab36df5411e5ad0d00163e000be0.png!161
5553 ms
e397ab36df5411e5ad0d00163e000be0.png!650
5564 ms
68096ea0dee111e5ad0d00163e000be0.jpg!80
5529 ms
ae610dde3bbb11e39603123a45dddc8a.jpg!80
5531 ms
a7c1bc3cdf4f11e5ad0d00163e000be0.png!161
5555 ms
9ca91d4caee711e5ad0d00163e000be0.png!161
5542 ms
ae94e6b6deea11e5ad0d00163e000be0.png!80
5542 ms
cb1c0806de9411e5ad0d00163e000be0.png!80
5543 ms
ca-pub-6226354653555931.js
68 ms
zrt_lookup.html
63 ms
show_ads_impl.js
66 ms
scrolltop.png
971 ms
bds_s_v2.js
2141 ms
stat.htm
170 ms
core.php
753 ms
ads
142 ms
osd.js
16 ms
ads
183 ms
9291268155534424452
29 ms
abg.js
31 ms
m_js_controller.js
40 ms
googlelogo_color_112x36dp.png
64 ms
s
25 ms
x_button_blue2.png
23 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
11 ms
pic.gif
1596 ms
d9afa9cc58bc11e4a3bf002274e0634d.png!470
5338 ms
bdsstyle.css
309 ms
is.png
612 ms
followButton.css
7 ms
sso.js
12 ms
followButton.js
10 ms
suda.js
11 ms
bg_flbtn.png
21 ms
b.gif
1046 ms
tz100.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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
tz100.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
General
Impact
Issue
Detected JavaScript libraries
tz100.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 Tz100.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 Tz100.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.
tz100.com
Open Graph description is not detected on the main page of Tz 100. 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: