Tools & Wizards About Us
lincha.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lincha.com

林茶网 - 武夷山茶叶网|武夷岩茶大红袍|正山小种红茶金骏眉

Page Load Speed

50.2 sec in total

First Response

1.1 sec

Resources Loaded

48.5 sec

Page Rendered

622 ms

lincha.com screenshot

About Website

Visit lincha.com now to see the best up-to-date Lincha content for China and also check out these interesting facts you probably never knew about lincha.com

武夷山茶叶网(林茶网:www.Lincha.com)关注武夷山茶叶市场,以大红袍茶、 肉桂、水仙为代表的武夷山岩茶和武夷红茶(正山小种、金骏眉红茶),关注大红袍价格、金骏眉价格和介绍大红袍是什么茶、金骏眉桐木关正山小种红茶、大红袍 功效、金骏眉功效等茶叶的功效与作用和武夷山大红袍专卖店的信息.

Visit lincha.com

Key Findings

We analyzed Lincha.com page load time and found that the first response time was 1.1 sec and then it took 49.1 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 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

lincha.com performance score

0

Network Requests Diagram

lincha.com

1078 ms

bootstrap.css

3383 ms

style.css

2189 ms

font-awesome.min.css

1893 ms

animate.css

2830 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 14% of them (15 requests) were addressed to the original Lincha.com, 11% (12 requests) were made to T10.baidu.com and 9% (10 requests) were made to T12.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source T10.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.9 kB (48%)

Content Size

1.2 MB

After Optimization

642.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lincha.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. 55% of websites need less resources to load. Javascripts take 429.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 52.9 kB

  • Original 67.1 kB
  • After minification 61.7 kB
  • After compression 14.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. 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 52.9 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 11.0 kB

  • Original 389.2 kB
  • After minification 378.2 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. Lincha images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 237.5 kB

  • Original 429.0 kB
  • After minification 428.5 kB
  • After compression 191.5 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 237.5 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 299.5 kB

  • Original 357.7 kB
  • After minification 324.2 kB
  • After compression 58.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. Lincha.com needs all CSS files to be minified and compressed as it can save up to 299.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (43%)

Requests Now

98

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lincha. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lincha.com

lincha.com

1078 ms

bootstrap.css

bootstrap.css

3383 ms

style.css

style.css

2189 ms

font-awesome.min.css

font-awesome.min.css

1893 ms

animate.css

animate.css

2830 ms

B00C00.css

B00C00.css

2873 ms

jquery.js

jquery.js

19524 ms

plugins.js

plugins.js

19525 ms

c.js

c.js

1063 ms

adsbygoogle.js

adsbygoogle.js

18 ms

functions.js

functions.js

7095 ms

wp-embed.min.js

wp-embed.min.js

1999 ms

qrcode_for_lincha.gif

qrcode_for_lincha.gif

2230 ms

timthumb.php

timthumb.php

2708 ms

lincha-com-qrcode.jpg

lincha-com-qrcode.jpg

1445 ms

timthumb.php

timthumb.php

2716 ms

timthumb.php

timthumb.php

5086 ms

timthumb.php

timthumb.php

7163 ms

timthumb.php

timthumb.php

6303 ms

timthumb.php

timthumb.php

3918 ms

loading.gif

loading.gif

2993 ms

logo.png

logo.png

2218 ms

logo-mobi.png

logo-mobi.png

1558 ms

hclm

hclm

736 ms

push.js

push.js

829 ms

dotted.png

dotted.png

2945 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

4222 ms

hclm

hclm

869 ms

hclm

hclm

773 ms

zrt_lookup.html

zrt_lookup.html

241 ms

show_ads_impl.js

show_ads_impl.js

163 ms

like

like

581 ms

am_cst_line.png

am_cst_line.png

1172 ms

cst_bg.png

cst_bg.png

1146 ms

am_bg.png

am_bg.png

1099 ms

hclm

hclm

1021 ms

footer-bg.jpg

footer-bg.jpg

8939 ms

widget-link.png

widget-link.png

3112 ms

widget-comment.png

widget-comment.png

3439 ms

stat.php

stat.php

1036 ms

ads

ads

277 ms

osd.js

osd.js

133 ms

ads

ads

273 ms

m_js_controller.js

m_js_controller.js

15 ms

abg.js

abg.js

50 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

59 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

57 ms

s

s

59 ms

x_button_blue2.png

x_button_blue2.png

44 ms

like_this.css

like_this.css

997 ms

j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js

j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js

12 ms

hclm

hclm

1896 ms

hclm

hclm

2480 ms

hclm

hclm

674 ms

hclm

hclm

2900 ms

stat.htm

stat.htm

272 ms

core.php

core.php

1439 ms

adx.php

adx.php

865 ms

u=2460184570,3230684567&fm=76

u=2460184570,3230684567&fm=76

1158 ms

u=724819251,3929121627&fm=76

u=724819251,3929121627&fm=76

2443 ms

u=269419931,689842886&fm=76

u=269419931,689842886&fm=76

7168 ms

bg.png

bg.png

576 ms

reduce_bd-logo1_oper.png

reduce_bd-logo1_oper.png

585 ms

u=1972141059,2588352677&fm=76

u=1972141059,2588352677&fm=76

20335 ms

u=815707873,3811565151&fm=76

u=815707873,3811565151&fm=76

4655 ms

u=851094431,1223671679&fm=76

u=851094431,1223671679&fm=76

20334 ms

u=1926554417,2847412231&fm=76

u=1926554417,2847412231&fm=76

4965 ms

u=733284413,847267242&fm=76

u=733284413,847267242&fm=76

4565 ms

u=3167490845,3632332229&fm=76

u=3167490845,3632332229&fm=76

2361 ms

u=1786237361,2270303794&fm=76

u=1786237361,2270303794&fm=76

5832 ms

qzfl_for_qzone.js

qzfl_for_qzone.js

730 ms

interface.js

interface.js

480 ms

tc.js

tc.js

480 ms

adx.php

adx.php

990 ms

like_bg.png

like_bg.png

248 ms

u=1919217789,2877167260&fm=76

u=1919217789,2877167260&fm=76

7712 ms

u=1056302295,128669961&fm=76

u=1056302295,128669961&fm=76

11309 ms

u=569575824,3717552257&fm=76

u=569575824,3717552257&fm=76

9630 ms

u=736789695,3763724407&fm=76

u=736789695,3763724407&fm=76

3030 ms

u=1333138468,2004568021&fm=76

u=1333138468,2004568021&fm=76

2711 ms

u=828686131,1143236679&fm=76

u=828686131,1143236679&fm=76

6635 ms

u=2045264153,2865505133&fm=76

u=2045264153,2865505133&fm=76

5090 ms

u=1046372606,1085172425&fm=76

u=1046372606,1085172425&fm=76

20280 ms

u=2449366487,1524057768&fm=76

u=2449366487,1524057768&fm=76

20281 ms

9.gif

9.gif

5088 ms

hm.js

hm.js

732 ms

adx.php

adx.php

450 ms

u=854973360,14275615&fm=76

u=854973360,14275615&fm=76

5977 ms

u=355574367,746139835&fm=76

u=355574367,746139835&fm=76

15790 ms

u=179453436,4294806091&fm=76

u=179453436,4294806091&fm=76

15038 ms

u=570752001,3683915222&fm=76

u=570752001,3683915222&fm=76

15203 ms

u=633016047,3555197488&fm=76

u=633016047,3555197488&fm=76

16868 ms

u=380705655,813403767&fm=76

u=380705655,813403767&fm=76

19605 ms

u=184021655,126458770&fm=76

u=184021655,126458770&fm=76

10600 ms

hm.gif

hm.gif

366 ms

s.js

s.js

1252 ms

besmap

besmap

4952 ms

adx.php

adx.php

420 ms

cube_1.jpg

cube_1.jpg

508 ms

app.gif

app.gif

1942 ms

closefeedback.min.js

closefeedback.min.js

491 ms

reduce_promotion_oper.png

reduce_promotion_oper.png

487 ms

bd_logo.png

bd_logo.png

485 ms

bg_rb.png

bg_rb.png

556 ms

o.htm

o.htm

4106 ms

ui

ui

157 ms

hm.gif

hm.gif

718 ms

ac.js

ac.js

513 ms

wh.js

wh.js

790 ms

SEO Factors

lincha.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lincha.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 Lincha.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.

Social Sharing Optimization

lincha.com

Open Graph description is not detected on the main page of Lincha. 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: