79.5 sec in total
8.1 sec
70.7 sec
688 ms
Click here to check amazing 368 Tea content for China. Otherwise, check out these important facts you probably never knew about 368tea.com
雅茗居茶文化网致力于打造最专业的茶文化知识网、手机茶叶网、云萱茶叶知识网。这里有茶叶知识、茶道知识、茶叶论坛、茶具知识、茶叶知识问答、宜兴紫砂壶知识、茶具知识、茶网大全、十大名茶知识、茶叶科研科技知识、以及黑茶知识网、黄茶知识网、红茶知识网、岩茶知识网、绿茶知识网、白茶知识网、花草茶知识网、乌龙茶知识网、普洱茶知识网、武夷大红袍茶艺表演视频、茶道表演视频、名窑瓷嚣等专业的茶叶网站。
Visit 368tea.comWe analyzed 368tea.com page load time and found that the first response time was 8.1 sec and then it took 71.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
368tea.com performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value2.0 s
97/100
25%
Value6.9 s
34/100
10%
Value0 ms
100/100
30%
Value0.045
99/100
15%
Value1.9 s
100/100
10%
8107 ms
3854 ms
3635 ms
695 ms
955 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 39% of them (52 requests) were addressed to the original 368tea.com, 15% (20 requests) were made to Pos.baidu.com and 8% (11 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain 368tea.com.
Page size can be reduced by 598.6 kB (46%)
1.3 MB
689.8 kB
In fact, the total size of 368tea.com main page is 1.3 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. 45% of websites need less resources to load. Javascripts take 640.8 kB which makes up the majority of the site volume.
Potential reduce by 126.6 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 23.1 kB, which is 16% 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 126.6 kB or 86% of the original size.
Potential reduce by 15.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. 368 Tea images are well optimized though.
Potential reduce by 432.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 432.6 kB or 68% of the original size.
Potential reduce by 24.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. 368tea.com needs all CSS files to be minified and compressed as it can save up to 24.0 kB or 80% of the original size.
Number of requests can be reduced by 47 (36%)
132
85
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 368 Tea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
368tea.com
8107 ms
168tea.css
3854 ms
menus.css
3635 ms
common.js
695 ms
shareto.js
955 ms
c.js
1594 ms
c.js
9126 ms
2972306.js
1110 ms
f.js
1313 ms
f.js
1019 ms
top.png
9526 ms
20160315_bb6543587a8a539a6bdaa73lWDmU13Lg.jpg
15120 ms
20160308_1c6d7fd693a1ea051b820MpjBbVmWV1S.jpg
19513 ms
20160305_6da161f877eed8a33e9amU3APgO6RQEq.jpg
19514 ms
20160305_607e6f14cb2f9dd19a41ZxhAfmePJxIP.jpg
19514 ms
20160302_d794f564e0c30aa96941Xo53VD6xG9yz.jpg
19513 ms
20160225_3a44a12f6a6e6281eec4gUlf7fSMWWbo.jpg
19513 ms
head_top_2.gif
347 ms
head_top_1.gif
346 ms
logo.gif
6695 ms
logo_map.gif
1039 ms
t1.jpg
19513 ms
1_201512040945451P27p.jpg
19506 ms
1_201511170945261pdfr.jpg
19505 ms
1_201511110945411Uz56.jpg
19506 ms
1_201509260947541I546.jpg
19506 ms
1_201509130948111qr00.jpg
19506 ms
l1.jpg
20500 ms
s3.jpg
20501 ms
s4.jpg
20499 ms
r2.jpg
20499 ms
share_sina.gif
15414 ms
share_renren.gif
20154 ms
share_qqwb.gif
20156 ms
r9.jpg
20473 ms
kcim
1686 ms
kcim
1110 ms
adx.php
1270 ms
u=1032677624,4283857634&fm=76
19532 ms
u=4220042409,215967527&fm=76
19531 ms
u=1904241940,1028360115&fm=76
3929 ms
bg.png
435 ms
u=1743791029,2758388625&fm=76
19525 ms
u=1547871558,2144661730&fm=76
7855 ms
u=553958940,998531244&fm=76
19524 ms
u=532347953,843705257&fm=76
17702 ms
reduce_bd-logo1_oper.png
436 ms
r10.jpg
18520 ms
kcim
354 ms
kcim
683 ms
kcim
941 ms
kcim
942 ms
kcim
1312 ms
kcim
997 ms
kcim
1286 ms
kcim
1279 ms
icon_12.gif
469 ms
kcim
2301 ms
ls.js
264 ms
kcim
2155 ms
ls_flowbar.js
265 ms
home
2864 ms
kcim
3039 ms
kcim
2572 ms
kcim
1411 ms
kcim
943 ms
kcim
3018 ms
kcim
16198 ms
kcim
2200 ms
adx.php
1789 ms
u=381608122,654455319&fm=76
18014 ms
u=229394781,3869966010&fm=76
19806 ms
u=273188660,600816362&fm=76
19806 ms
u=446284679,477678630&fm=76
19806 ms
u=872235593,3739827254&fm=76
8066 ms
u=1467652022,2171702146&fm=76
19805 ms
adx.php
1046 ms
lu_hot_word.png
434 ms
adx.php
1308 ms
adx.php
1036 ms
cpro.js
656 ms
adx.php
1831 ms
closefeedback.min.js
445 ms
icon_14px.png
454 ms
adx.php
6657 ms
jquery_a4373ccd.js
525 ms
cm
643 ms
adx.php
1026 ms
tpl_flowbarimgtext.js
523 ms
u=639822778,3930173820&fm=76
20256 ms
u=420914965,918734605&fm=76
20255 ms
u=436594962,759961637&fm=76
20255 ms
u=1498564476,1971018852&fm=76
7053 ms
u=3761954114,3257532577&fm=76
8940 ms
u=1116139691,1549905397&fm=76
19932 ms
reduce_promotion_oper.png
442 ms
bd_logo.png
442 ms
bg_rb.png
450 ms
u=401277584,3836194238&fm=96
19889 ms
u=1217394418,3099274421&fm=96
3066 ms
arrow_left_60_e700a3bb.png
264 ms
nextprev_0d964fdd.png
263 ms
b_613fef8e.png
518 ms
u=2568940497,3963180835&fm=96
5115 ms
u=1466177841,4232761777&fm=96
19871 ms
u=3177198820,3242205509&fm=96
1199 ms
u=631427633,3530015036&fm=96
1682 ms
u=838759026,2844843528&fm=96
19871 ms
emar
603 ms
1_2009051917080110a78.thumb.jpg
3883 ms
1_2009051917065311UgQ.thumb.jpg
19998 ms
1_2009051917063813sJf.thumb.jpg
8700 ms
1_200905191701371YDx0.gif
19997 ms
1_2014070913580214Qn4.thumb.jpg
17262 ms
1_200905191506151O2jK.gif
6066 ms
000.gif
8752 ms
110.gif
11630 ms
head_top_3.gif
9097 ms
cate_nav_bg.gif
9441 ms
cate_nav_bg_3.gif
11468 ms
titlepos.gif
10062 ms
dot.gif
9411 ms
numbg.gif
12328 ms
frame1.gif
10815 ms
icon_li.gif
10983 ms
cathead.gif
18136 ms
fbg.gif
11338 ms
subt.gif
11690 ms
subb.gif
12041 ms
bottom_bg3.gif
12393 ms
adx.php
518 ms
o.htm
744 ms
wh.js
1551 ms
ac.js
1335 ms
368tea.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
368tea.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
368tea.com SEO score
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
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
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 368tea.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 368tea.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.
368tea.com
Open Graph description is not detected on the main page of 368 Tea. 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: