Tools & Wizards About Us
368tea.com screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

368tea.com

雅茗居-雅茗居茶文化网-云萱说茶-茶道知识-茶文化论坛

Page Load Speed

14.9 sec in total

First Response

2.7 sec

Resources Loaded

11.7 sec

Page Rendered

490 ms

368tea.com screenshot

About Website

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.com

Key Findings

We analyzed 368tea.com page load time and found that the first response time was 2.7 sec and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

368tea.com performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

368tea.com

2747 ms

168tea.css

649 ms

menus.css

435 ms

common.js

439 ms

shareto.js

1327 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 96% of them (77 requests) were addressed to the original 368tea.com, 3% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to Js.users.51.la. The less responsive or slowest element that took the longest time to load (8.6 sec) belongs to the original domain 368tea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.5 kB (10%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 368tea.com main page is 2.8 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. 40% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 104.2 kB

  • Original 121.2 kB
  • After minification 98.6 kB
  • After compression 17.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 22.6 kB, which is 19% 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 104.2 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 177.4 kB

  • Original 2.6 MB
  • After minification 2.5 MB

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.

JavaScript Optimization

-35%

Potential reduce by 865 B

  • Original 2.4 kB
  • After minification 2.4 kB
  • After compression 1.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 865 B or 35% of the original size.

CSS Optimization

-33%

Potential reduce by 3.0 kB

  • Original 9.1 kB
  • After minification 9.1 kB
  • After compression 6.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. 368tea.com needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (19%)

Requests Now

79

After Optimization

64

  • Images
  • JavaScript
  • CSS

The browser has sent 79 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 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

368tea.com

368tea.com

2747 ms

168tea.css

168tea.css

649 ms

menus.css

menus.css

435 ms

common.js

common.js

439 ms

shareto.js

shareto.js

1327 ms

hm.js

hm.js

1261 ms

top.png

top.png

884 ms

2407150001ab22b6ab67820b6e.jpeg

2407150001ab22b6ab67820b6e.jpeg

1328 ms

2406270247d552a4ac17ac2931.jpg

2406270247d552a4ac17ac2931.jpg

3327 ms

2402040742a5233cd44ba02a94.jpg

2402040742a5233cd44ba02a94.jpg

3702 ms

23121310132674a496bef0281f.jpg

23121310132674a496bef0281f.jpg

3730 ms

2312131010cc2dcfcbebc6f164.jpg

2312131010cc2dcfcbebc6f164.jpg

4748 ms

22042610463c9316a08db8194c.jpg

22042610463c9316a08db8194c.jpg

1527 ms

head_top_2.gif

head_top_2.gif

861 ms

head_top_1.gif

head_top_1.gif

215 ms

logo.gif

logo.gif

225 ms

logo_map.gif

logo_map.gif

800 ms

t1.jpg

t1.jpg

1326 ms

1_202406262356555SXvV.jpg

1_202406262356555SXvV.jpg

6683 ms

1_202211260954122dZ0U.png

1_202211260954122dZ0U.png

7939 ms

1_202201080953351K6e5.png

1_202201080953351K6e5.png

8621 ms

1_202112210953281hyZn.jpg

1_202112210953281hyZn.jpg

8607 ms

1_202112060953251bEb4.jpg

1_202112060953251bEb4.jpg

7316 ms

1_202109300954081uinQ.jpg

1_202109300954081uinQ.jpg

4847 ms

new1.gif

new1.gif

5065 ms

Mr.fzp.jpg

Mr.fzp.jpg

5281 ms

s1.jpg

s1.jpg

5498 ms

s2.jpg

s2.jpg

5715 ms

r1.jpg

r1.jpg

5932 ms

l1.jpg

l1.jpg

6150 ms

s3.jpg

s3.jpg

6367 ms

s4.jpg

s4.jpg

6585 ms

r2.jpg

r2.jpg

6802 ms

r3.jpg

r3.jpg

6904 ms

r4.jpg

r4.jpg

7019 ms

l2.jpg

l2.jpg

7350 ms

s5.jpg

s5.jpg

7235 ms

s6.jpg

s6.jpg

7466 ms

r5.jpg

r5.jpg

7557 ms

r6.jpg

r6.jpg

7573 ms

r7.jpg

r7.jpg

7683 ms

s9.jpg

s9.jpg

8447 ms

s10.jpg

s10.jpg

7795 ms

s11.jpg

s11.jpg

7902 ms

s12.jpg

s12.jpg

8019 ms

s13.jpg

s13.jpg

8118 ms

s14.jpg

s14.jpg

8245 ms

l3.jpg

l3.jpg

8247 ms

s7.jpg

s7.jpg

8124 ms

s8.jpg

s8.jpg

8239 ms

share_sina.gif

share_sina.gif

851 ms

share_douban.gif

share_douban.gif

1049 ms

share_renren.gif

share_renren.gif

1068 ms

share_qqwb.gif

share_qqwb.gif

1261 ms

r8.jpg

r8.jpg

7674 ms

2972306.js

2972306.js

667 ms

r9.jpg

r9.jpg

7762 ms

r10.jpg

r10.jpg

8429 ms

hm.gif

hm.gif

311 ms

1_200906131358561FAnR.thumb.jpg

1_200906131358561FAnR.thumb.jpg

7563 ms

1_2009061213592411pV7.thumb.jpg

1_2009061213592411pV7.thumb.jpg

4043 ms

1_200906121359042SGta.thumb.jpg

1_200906121359042SGta.thumb.jpg

3825 ms

1_200906121359001A1Y8.thumb.jpg

1_200906121359001A1Y8.thumb.jpg

3609 ms

1_200906121358581ZLAR.thumb.jpg

1_200906121358581ZLAR.thumb.jpg

3392 ms

1_200906111753171hFfi.thumb.jpg

1_200906111753171hFfi.thumb.jpg

3405 ms

head_top_3.gif

head_top_3.gif

3172 ms

cate_nav_bg.gif

cate_nav_bg.gif

3446 ms

cate_nav_bg_3.gif

cate_nav_bg_3.gif

2739 ms

titlepos.gif

titlepos.gif

2532 ms

dot.gif

dot.gif

2644 ms

numbg.gif

numbg.gif

2525 ms

frame1.gif

frame1.gif

2431 ms

icon_li.gif

icon_li.gif

2316 ms

cathead.gif

cathead.gif

2281 ms

fbg.gif

fbg.gif

2228 ms

subt.gif

subt.gif

2194 ms

subb.gif

subb.gif

2086 ms

bottom_bg3.gif

bottom_bg3.gif

1991 ms

000.gif

000.gif

2177 ms

110.gif

110.gif

2076 ms

Accessibility Review

368tea.com accessibility score

58

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

368tea.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

368tea.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: