68.2 sec in total
13.3 sec
54 sec
885 ms
Visit lirenxie.com now to see the best up-to-date Lirenxie content and also check out these interesting facts you probably never knew about lirenxie.com
Visit lirenxie.comWe analyzed Lirenxie.com page load time and found that the first response time was 13.3 sec and then it took 54.9 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 24 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lirenxie.com performance score
13284 ms
9689 ms
2210 ms
3110 ms
913 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 92% of them (72 requests) were addressed to the original Lirenxie.com, 5% (4 requests) were made to Pub.idqqimg.com and 1% (1 request) were made to Wpa.qq.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Lirenxie.com.
Page size can be reduced by 120.1 kB (24%)
497.3 kB
377.1 kB
In fact, the total size of Lirenxie.com main page is 497.3 kB. 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 389.2 kB which makes up the majority of the site volume.
Potential reduce by 47.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. This page needs HTML code to be minified as it can gain 7.8 kB, which is 13% 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 47.7 kB or 82% of the original size.
Potential reduce by 33.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. Lirenxie images are well optimized though.
Potential reduce by 27.8 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 27.8 kB or 78% of the original size.
Potential reduce by 11.5 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. Lirenxie.com needs all CSS files to be minified and compressed as it can save up to 11.5 kB or 82% of the original size.
Number of requests can be reduced by 5 (9%)
53
48
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lirenxie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
lirenxie.com
13284 ms
base.css
9689 ms
index.css
2210 ms
common.js
3110 ms
index.js
913 ms
transport.js
5400 ms
utils.js
1364 ms
cycle_image.js
1820 ms
logo.gif
517 ms
nav_cat.gif
461 ms
%E6%9C%AC_01_conew1.jpg
7098 ms
%E6%9C%AC_03_conew1.jpg
2728 ms
%E6%9C%AC_05_conew1.jpg
3444 ms
%E6%9C%AC_07_conew1.jpg
5951 ms
8933_thumb_G_1453580244687.jpg
4445 ms
8905_thumb_G_1453576473491.jpg
6380 ms
8916_thumb_G_1453577891420.jpg
8204 ms
1773_thumb_G_1273806393491.jpg
9204 ms
4626_thumb_G_1320484276770.jpg
7849 ms
1895_thumb_G_1273212604705.jpg
7368 ms
8926_thumb_G_1453579172262.jpg
9699 ms
9038_thumb_G_1455615146571.jpg
18754 ms
8953_thumb_G_1453967952040.jpg
14210 ms
8944_thumb_G_1453964866473.jpg
16983 ms
3587_thumb_G_1298851928129.jpg
16198 ms
8910_thumb_G_1453577133987.jpg
16441 ms
8938_thumb_G_1453923405222.jpg
16315 ms
9057_thumb_G_1457765297321.jpg
18915 ms
9003_thumb_G_1455570551802.jpg
19855 ms
8866_thumb_G_1446357470269.jpg
20345 ms
8799_thumb_G_1444021380959.jpg
20345 ms
8556_thumb_G_1437202161093.jpg
20347 ms
7888_thumb_G_1411622169467.jpg
20350 ms
8196_thumb_G_1426574733930.jpg
20352 ms
8185_thumb_G_1426576497452.jpg
20354 ms
8128_thumb_G_1424754733706.jpg
20356 ms
7992_thumb_G_1418883429817.jpg
20358 ms
7799_thumb_G_1409102059142.jpg
20358 ms
7835_thumb_G_1410070770427.jpg
20360 ms
9155_thumb_G_1459834720498.jpg
20360 ms
8741_thumb_G_1441347185658.jpg
20361 ms
8762_thumb_G_1442216350777.jpg
20363 ms
8917_thumb_G_1453578020593.jpg
20362 ms
8876_thumb_G_1446415620134.jpg
19921 ms
8843_thumb_G_1443858502776.jpg
19868 ms
qq.css
19771 ms
ServiceQQ.js
19069 ms
8798_thumb_G_1444023025413.jpg
19909 ms
8804_thumb_G_1444018470768.jpg
19908 ms
8726_thumb_G_1440306008831.jpg
18135 ms
8668_thumb_G_1438928296015.jpg
19969 ms
8084_thumb_G_1422933299347.jpg
20255 ms
8088_thumb_G_1422931334899.jpg
19980 ms
8085_thumb_G_1422933063290.jpg
18224 ms
8078_thumb_G_1422935493542.jpg
19262 ms
8079_thumb_G_1422934349221.jpg
20144 ms
8080_thumb_G_1422934133125.jpg
17792 ms
8081_thumb_G_1422933997869.jpg
17925 ms
8083_thumb_G_1422933479459.jpg
17727 ms
8086_thumb_G_1422931539973.jpg
14257 ms
8089_thumb_G_1422931183566.jpg
16564 ms
so.gif
11317 ms
icon-common.png
11060 ms
loading.gif
11397 ms
icon-saleoff.png
11519 ms
%E4%B8%80%E7%9B%B4%E7%94%A8%E5%BF%83%E5%9C%A8%E5%81%9A.gif
11325 ms
f1.gif
13114 ms
f2.gif
13538 ms
f3.gif
14737 ms
dibubj.jpg
14550 ms
popup-close-bg.png
13570 ms
pa
19552 ms
qq_1.png
16747 ms
T1uUG.XjtkXXcb2gzo-77-19.gif
340 ms
button_71.gif
472 ms
button_71.gif
471 ms
button_71.gif
469 ms
button_71.gif
546 ms
lirenxie.com SEO score
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lirenxie.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 Lirenxie.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.
lirenxie.com
Open Graph description is not detected on the main page of Lirenxie. 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: