Analyze

lanshe.cc: 请稍等,正在进入...

兰舍效果图专业收集硅藻泥效果图、兰舍硅藻泥效果图、硅藻泥效果图片、硅藻泥图片的综合性硅藻泥图片网站【www.lanshe.cc】

Page load speed analysis

  • 46/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    2.7 sec

  • Resources loaded

    26.3 sec

  • Page rendered

    947 ms

  • Total page load time

    29.9 sec

Welcome to lanshe.cc homepage info - get ready to check Lanshe best content right away, or after learning these important things about lanshe.cc

We analyzed Lanshe.cc page load time and found that the first response time was 2.7 sec and then it took 27.2 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Page optimization

  • HTML 46.5 kB
    Images 2.5 MB
    Javascripts 35.4 kB
    CSS 12.5 kB

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

    • Original 46.5 kB
    • After minification 45.4 kB
    • After compression 6.8 kB

    HTML optimization

    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 39.7 kB or 85% of the original size.

    • Original 2.5 MB
    • After optimization 2.4 MB

    Image optimization

    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. Lanshe images are well optimized though.

    • Original 35.4 kB
    • After minification 34.6 kB
    • After compression 12.9 kB

    JavaScript optimization

    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 22.4 kB or 63% of the original size.

    • Original 12.5 kB
    • After minification 9.5 kB
    • After compression 2.6 kB

    CSS optimization

    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. Lanshe.cc needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 79% of the original size.

Network requests diagram

  • lanshe.cc
  • css.css
  • logo.jpg
  • hottags.js
  • fav.js
  • thea1.js
  • thea3.js
  • thea7.js
  • lib.js
  • common.js
  • thea4.js
  • ecmst.js
  • 6b63dcee010920ae20bc9b3ff89bac99.jpg
  • 681b093c9a3c6d47ee5b4ea25cb060c3.jpg
  • 2d887ee0e883cda7694c013149d3f45d.jpg
  • 169a76daf7637fd00606ecf5bad8e9ab.jpg
  • 20576a17d95ebcde1d4dfdc518c2bc84.jpg
  • 00b1f9a309e3d31878eea2b297c8a2e7.jpg
  • f28c3c9c6446723f76a650226869aa7f.jpg
  • 2cffedfd3a69d7afdba8e4983cc8b61e.jpg
  • 1a204ad4c30d1ef333f54fba704c5d8f.jpg
  • 44869c922bf482c550a692fa34215397.jpg
  • 985effb44204839ee937a04493d6511f.jpg
  • 2076fbd478bd37edba54413c37bbc57a.jpg
  • 7aa88f6cf134f221150863e26a15438b.jpg
  • 081098aedc9e0aa9385638acb18060ab.jpg
  • ddabd88e5fbdd13aab819cb4e3eb03cd.jpg
  • dd34f2751018720f6a91421c0c55d9a9.jpg
  • b0a26e8135167fe4ba974f8d6dfea7df.jpg
  • a6a0612b39602f929762566b3607a499.jpg
  • fc34ed314a7073391a6fe45d3d8739eb.jpg
  • ffc3d0bab1aceee091f3f02c3e29020c.jpg
  • 70b0ffb645046a75ac036d990d51fc91.jpg
  • 269a7bd4a7f6d61c3c14b172d1d4e46d.jpg
  • 68860006d1de5bb2a5101cfd7cff89e2.jpg
  • b178d7b91151db93f505c147c46d5f14.jpg
  • 3b9f4ed46260b570f5d38f1cbd4d57bf.jpg
  • 411715f4e64e40c5cf994efaaa77f25f.jpg
  • 09d86a37d41909e922d4f73f984fe631.jpg
  • b2c2fe62a12c14859fed083391f5b0ca.jpg
  • b197449ee803936d45c365523c90ea05.jpg
  • a43a2e11130bafd94d9e70e8bd8d4efa.jpg
  • 4993c77912d2f6bcba2e30a9c36214da.jpg
  • 78c573c28702fb5c0d0d297b4b469f46.jpg
  • 3c2d8f603892bf31856169fd325a60ee.jpg
  • 7376ef8b024d5af9e6c3c3755a781829.jpg
  • 26bb3567b9311e725383630f423aa3bd.jpg
  • search.png
  • navR.png
  • navLi.png
  • navCur.png
  • hot.gif
  • B3taocan.jpg
  • focus.png
  • thR.png
  • titCur.png
  • tit.png
  • recom.png
  • next.png
  • prev.png
  • yygzn.jpg
  • lay1.png
  • lay2.png
  • lay3.png
  • lay4.png
  • lay9.png
  • lay5.png
  • hm.js
  • h.js
  • tongji.js
  • focusCur.png
  • hm.gif
  • hm.gif
  • 031fdc3dff0d5e91e384c2a6cc458873.jpg
  • 9fba774019bd0ad1e6a16e3f656a4474.jpg
  • 4f13a6509848421706607b625b252a65.jpg
  • e87bdfedb4c70a64f8b08211de1c0444.jpg
  • cbdca8b7498a39e8a86b4f57be71cce9.jpg
  • c0e01b1a8d3e22da75edc985bc2dbf3a.jpg
  • f5e10e162ac8d82af2f540034fa58115.jpg
  • 692feb33b27c894b09005cababb1ad1c.jpg
  • 40ff3ac6aaef07a81dc393f2751ad91a.jpg
  • 6b140f8e245d6dd1a7dcdbb6485da73e.jpg
  • 7ed5ba056d53ada818847ad815e42e0a.jpg
  • 9ddf4ec222ada467981ac47fa2bc3ba5.jpg
  • 90575f13a0b12fd69ec53893ef89b155.jpg
  • 5d5540929242ec1b5810fead6cb5f64d.jpg
  • e63b692fc7e2e878c421907e972faf3e.jpg
  • 865c10675ec87775b0af967a63b37536.jpg
  • b27714b8641e72954f942e295601fe8c.jpg
  • 87ca02a0b2ccc7e85996634445ecf106.jpg
  • 977db1a14bb7a4bb94e708a6517d3614.jpg
  • aa79bf1b268101ef631f950d876c3658.jpg
  • e5e67da1b367a5b3ff999a605df5c4d9.jpg
  • ddb1bcad88db528c9c48b625cfb66575.jpg
  • 52c2ccad62371c4600dca59609aa27c6.jpg

Our browser made a total of 96 requests to load all elements on the main page. We found that 93% of them (89 requests) were addressed to the original Lanshe.cc, 4% (4 requests) were made to Hm.baidu.com and 2% (2 requests) were made to Gznpic.b0.upaiyun.com. The less responsive or slowest element that took the longest time to load (19.6 sec) belongs to the original domain Lanshe.cc.

Additional info on lanshe.cc

Requests

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

12

Javascripts

81

Images

1

CSS

94

All

Possible request optimization

1

Javascripts

71

Images

1

CSS

21

Optimized

73

All

Normal result

IP address

This IP address is dedicated to Lanshe.cc. This is the best domain hosting practice .

Normal result

IP Trace

lanshe.cc

156.224.178.160

DNS records

Type Host Target/ip TTL Other
A

www.lanshe.cc.w.kunlungr.com

122.228.95.135 179
NS

lanshe.cc

v1s1.xundns.com 7199
NS

lanshe.cc

v1s2.xundns.com 7199
CNAME

lanshe.cc

www.lanshe.cc.w.kunlungr.com 599
SOA

lanshe.cc

7199 Mname: v1s1.xundns.com
Rname: nsadmin.xundns.com
Serial: 286270
Refresh: 3600
Retry: 600
Expire: 604800
Minimum-ttl: 600

Language and encoding

Normal result

Language

N/A  language flag

Detected

N/A  language flag

Claimed

Encoding

GB2312

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lanshe.cc can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lanshe.cc main page’s claimed encoding is gb2312. 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.

HTTPS certificate

SSL Certificate

Lanshe.cc has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of Lanshe.cc is located in South Africa, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Poor result

Social Sharing Optimization

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

lanshe.cc

Share this report in social media

Analyze another website

Analyze