29.9 sec in total
2.7 sec
26.3 sec
947 ms
Welcome to lanshe.cc homepage info - get ready to check Lanshe best content right away, or after learning these important things about lanshe.cc
兰舍效果图专业收集硅藻泥效果图、兰舍硅藻泥效果图、硅藻泥效果图片、硅藻泥图片的综合性硅藻泥图片网站【www.lanshe.cc】
Visit lanshe.ccWe 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.
lanshe.cc performance score
2679 ms
4330 ms
6520 ms
1277 ms
768 ms
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.
Page size can be reduced by 185.9 kB (7%)
2.6 MB
2.4 MB
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. 20% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 39.7 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 39.7 kB or 85% of the original size.
Potential reduce by 113.9 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. Lanshe images are well optimized though.
Potential reduce by 22.4 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 22.4 kB or 63% of the original size.
Potential reduce by 9.9 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. 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.
Number of requests can be reduced by 21 (22%)
94
73
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.
lanshe.cc
2679 ms
css.css
4330 ms
logo.jpg
6520 ms
hottags.js
1277 ms
fav.js
768 ms
thea1.js
1037 ms
thea3.js
784 ms
thea7.js
753 ms
lib.js
1185 ms
common.js
748 ms
thea4.js
558 ms
ecmst.js
577 ms
6b63dcee010920ae20bc9b3ff89bac99.jpg
2529 ms
681b093c9a3c6d47ee5b4ea25cb060c3.jpg
6714 ms
2d887ee0e883cda7694c013149d3f45d.jpg
6719 ms
169a76daf7637fd00606ecf5bad8e9ab.jpg
2612 ms
20576a17d95ebcde1d4dfdc518c2bc84.jpg
5510 ms
00b1f9a309e3d31878eea2b297c8a2e7.jpg
3354 ms
f28c3c9c6446723f76a650226869aa7f.jpg
3694 ms
2cffedfd3a69d7afdba8e4983cc8b61e.jpg
3625 ms
1a204ad4c30d1ef333f54fba704c5d8f.jpg
5627 ms
44869c922bf482c550a692fa34215397.jpg
4879 ms
985effb44204839ee937a04493d6511f.jpg
5516 ms
2076fbd478bd37edba54413c37bbc57a.jpg
6550 ms
7aa88f6cf134f221150863e26a15438b.jpg
7659 ms
081098aedc9e0aa9385638acb18060ab.jpg
6623 ms
ddabd88e5fbdd13aab819cb4e3eb03cd.jpg
7190 ms
dd34f2751018720f6a91421c0c55d9a9.jpg
8758 ms
b0a26e8135167fe4ba974f8d6dfea7df.jpg
9088 ms
a6a0612b39602f929762566b3607a499.jpg
19630 ms
fc34ed314a7073391a6fe45d3d8739eb.jpg
8873 ms
ffc3d0bab1aceee091f3f02c3e29020c.jpg
8982 ms
70b0ffb645046a75ac036d990d51fc91.jpg
9245 ms
269a7bd4a7f6d61c3c14b172d1d4e46d.jpg
12678 ms
68860006d1de5bb2a5101cfd7cff89e2.jpg
12434 ms
b178d7b91151db93f505c147c46d5f14.jpg
10371 ms
3b9f4ed46260b570f5d38f1cbd4d57bf.jpg
10147 ms
411715f4e64e40c5cf994efaaa77f25f.jpg
10587 ms
09d86a37d41909e922d4f73f984fe631.jpg
13328 ms
b2c2fe62a12c14859fed083391f5b0ca.jpg
11335 ms
b197449ee803936d45c365523c90ea05.jpg
13658 ms
a43a2e11130bafd94d9e70e8bd8d4efa.jpg
13144 ms
4993c77912d2f6bcba2e30a9c36214da.jpg
13471 ms
78c573c28702fb5c0d0d297b4b469f46.jpg
14805 ms
3c2d8f603892bf31856169fd325a60ee.jpg
14418 ms
7376ef8b024d5af9e6c3c3755a781829.jpg
14330 ms
26bb3567b9311e725383630f423aa3bd.jpg
14291 ms
search.png
255 ms
navR.png
274 ms
navLi.png
271 ms
navCur.png
269 ms
hot.gif
283 ms
B3taocan.jpg
1683 ms
focus.png
246 ms
thR.png
548 ms
titCur.png
588 ms
tit.png
582 ms
recom.png
1005 ms
next.png
3292 ms
prev.png
1011 ms
yygzn.jpg
1901 ms
lay1.png
812 ms
lay2.png
1068 ms
lay3.png
934 ms
lay4.png
1089 ms
lay9.png
1281 ms
lay5.png
1279 ms
hm.js
1461 ms
h.js
1061 ms
tongji.js
1345 ms
focusCur.png
1325 ms
hm.gif
383 ms
hm.gif
1229 ms
031fdc3dff0d5e91e384c2a6cc458873.jpg
13023 ms
9fba774019bd0ad1e6a16e3f656a4474.jpg
13561 ms
4f13a6509848421706607b625b252a65.jpg
13908 ms
e87bdfedb4c70a64f8b08211de1c0444.jpg
12430 ms
cbdca8b7498a39e8a86b4f57be71cce9.jpg
12257 ms
c0e01b1a8d3e22da75edc985bc2dbf3a.jpg
12501 ms
f5e10e162ac8d82af2f540034fa58115.jpg
11938 ms
692feb33b27c894b09005cababb1ad1c.jpg
11475 ms
40ff3ac6aaef07a81dc393f2751ad91a.jpg
12375 ms
6b140f8e245d6dd1a7dcdbb6485da73e.jpg
12610 ms
7ed5ba056d53ada818847ad815e42e0a.jpg
10823 ms
9ddf4ec222ada467981ac47fa2bc3ba5.jpg
11190 ms
90575f13a0b12fd69ec53893ef89b155.jpg
11099 ms
5d5540929242ec1b5810fead6cb5f64d.jpg
11756 ms
e63b692fc7e2e878c421907e972faf3e.jpg
11736 ms
865c10675ec87775b0af967a63b37536.jpg
11014 ms
b27714b8641e72954f942e295601fe8c.jpg
11007 ms
87ca02a0b2ccc7e85996634445ecf106.jpg
10468 ms
977db1a14bb7a4bb94e708a6517d3614.jpg
11183 ms
aa79bf1b268101ef631f950d876c3658.jpg
11579 ms
e5e67da1b367a5b3ff999a605df5c4d9.jpg
11008 ms
ddb1bcad88db528c9c48b625cfb66575.jpg
10501 ms
52c2ccad62371c4600dca59609aa27c6.jpg
10424 ms
lanshe.cc SEO score
N/A
N/A
GB2312
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.
lanshe.cc
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: