9.1 sec in total
1.6 sec
7.2 sec
229 ms
Visit liu16.com now to see the best up-to-date Liu 16 content for China and also check out these interesting facts you probably never knew about liu16.com
你知道的网站我能收录,你不知道的网址我也能收录,光的传人导航,一个自用实用的福利导航大全!本着实用原则,首页无需登陆可以自定义添加自己喜欢的网站,适合情侣观看的网站、男人喜欢的网址、最新免费福利网站……能收尽收!满足男人女人不同的导航需求!
Visit liu16.comWe analyzed Liu16.com page load time and found that the first response time was 1.6 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
liu16.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value3.4 s
66/100
25%
Value9.2 s
13/100
10%
Value490 ms
59/100
30%
Value0.451
20/100
15%
Value11.1 s
20/100
10%
1645 ms
748 ms
717 ms
1235 ms
751 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 57% of them (79 requests) were addressed to the original Liu16.com, 7% (10 requests) were made to Tianqi.2345.com and 2% (3 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Liu16.com.
Page size can be reduced by 111.9 kB (17%)
644.9 kB
533.0 kB
In fact, the total size of Liu16.com main page is 644.9 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. 55% of websites need less resources to load. Javascripts take 291.0 kB which makes up the majority of the site volume.
Potential reduce by 59.1 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 9.2 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 59.1 kB or 84% of the original size.
Potential reduce by 5.4 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. Liu 16 images are well optimized though.
Potential reduce by 46.0 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 46.0 kB or 16% of the original size.
Potential reduce by 1.4 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. Liu16.com has all CSS files already compressed.
Number of requests can be reduced by 24 (19%)
127
103
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liu 16. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
liu16.com
1645 ms
font-awesome.min.css
748 ms
style.css
717 ms
jquery-2.2.4.min.js
1235 ms
zblogphp.js
751 ms
c_html_js_add.php
791 ms
jquery.js
2055 ms
cm.js
1367 ms
jquery.cookie.min.js
442 ms
main.js
756 ms
swiper.js
1043 ms
favicon.png
1498 ms
favicon.ico
1404 ms
O1CN01c26iB51UyR3MKMFvk_!!6000000002586-2-tps-124-122.png
599 ms
favicon.ico
584 ms
favicon2.ico
376 ms
favicon.ico
991 ms
favicon.ico
1052 ms
favicon.ico
281 ms
favicon.ico
575 ms
favicon.ico
1964 ms
favicon.ico
1180 ms
favicon.ico
505 ms
favicon.ico
1148 ms
favicon.ico
990 ms
favicon.ico
474 ms
favicon.ico
1120 ms
favicon.ico
286 ms
favicon.ico
550 ms
favicon.ico
1022 ms
favicon.ico
296 ms
logo.png
459 ms
favicon.ico
364 ms
favicon.ico
1932 ms
favicon.ico
627 ms
favicon.ico
945 ms
favicon.ico
1380 ms
favicon.ico
2399 ms
favicon.fb0b7.ico
2012 ms
favicon.ico
1869 ms
favicon.ico
552 ms
favicon.ico
1054 ms
logo_default.png
972 ms
darklogo_default.png
517 ms
favicon_default.ico
516 ms
20220404112930_60607.ico
275 ms
20220406225420_54016.ico
276 ms
20220403172043_97000.ico
542 ms
20220402232316_60941.png
543 ms
20230519201326_75575.ico
545 ms
20220402234202_19215.ico
830 ms
20220403171812_19709.ico
828 ms
20220403171224_20192.ico
828 ms
20220402232953_54726.png
829 ms
20220403000502_65308.ico
843 ms
20220403163300_67705.ico
1082 ms
20220402235321_59357.ico
1078 ms
20220403001214_61040.ico
1079 ms
20220402232152_58576.ico
1081 ms
20220404114006_61482.ico
1085 ms
20220403171444_11335.ico
1206 ms
20220403170409_73661.ico
1316 ms
20220403234607_45444.ico
1321 ms
20220410163815_18911.ico
1327 ms
20220406111640_65241.ico
1328 ms
20220410122031_55500.ico
1324 ms
20240101232712_14519.png
1529 ms
20240101230931_46858.png
1549 ms
20220404111644_71050.ico
1557 ms
20220408193303_91938.ico
1566 ms
20220411171925_25041.ico
1566 ms
20220408193636_32383.ico
1567 ms
202204111649685996374109.ico
1766 ms
20220411215809_53027.ico
1783 ms
20220406230457_87360.ico
1794 ms
20220404112516_92892.ico
1804 ms
20220406230219_85346.ico
1800 ms
20220404112744_99512.ico
1539 ms
20220406230640_36724.ico
4297 ms
8.jpg
1979 ms
favicon.ico
488 ms
20220404110157_30963.ico
1523 ms
20220404111114_71504.png
2004 ms
20220406231345_47760.ico
1514 ms
20220404105813_19030.png
1517 ms
favicon.ico
544 ms
20220404105526_21713.png
1867 ms
favicon.ico
336 ms
favicon.ico
110 ms
index.htm
603 ms
icmm
1776 ms
favicon.ico
271 ms
20220410170415_30472.ico
2358 ms
202204061649212723749993.png
2357 ms
20220411165626_14801.ico
2353 ms
20230715232407_19636.ico
2341 ms
h.js
456 ms
202204101649566236985547.ico
2576 ms
fontawesome-webfont.woff
2447 ms
202204071649343446191612.ico
2355 ms
20220410234410_76258.ico
2355 ms
20220410120412_42074.ico
2354 ms
20220406110426_85262.ico
2574 ms
202204101649605333162857.ico
2582 ms
TB1uh..zbj1gK0jSZFuXXcrHpXa-16-16.ico
72 ms
20220411170031_97248.ico
2462 ms
h.js
1159 ms
20220410121105_40063.ico
2356 ms
20220410120739_72381.ico
2353 ms
20220410124352_95138.ico
2570 ms
20220408194215_63022.ico
2581 ms
20220406104320_43809.ico
2585 ms
wea_plugin_widget.css
242 ms
jquery-1.8.3.min.js
666 ms
common2_v20160923084755.js
477 ms
citySelectData.js
723 ms
interCitySelectData.js
958 ms
smallCityName.js
434 ms
widget.js
469 ms
tianqiplugin
579 ms
20220408112609_22367.ico
2391 ms
20220406113518_62239.ico
2371 ms
20220410120211_91285.ico
2575 ms
20220410121333_65317.ico
2586 ms
20220406113334_65783.ico
2586 ms
1.jpg
2592 ms
20220408113522_33336.ico
2395 ms
202204141649927222187400.png
2638 ms
20220408114934_69314.ico
2725 ms
20220408115813_71122.ico
2618 ms
20220512163859_26347.png
2615 ms
favicon.ico
1621 ms
detect2013_plugin.php
221 ms
21.gif
1647 ms
hm.gif
335 ms
auto_dup
356 ms
plugin-widget.png
220 ms
icmm
536 ms
liu16.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
liu16.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
liu16.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
ZH
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liu16.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 Liu16.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.
liu16.com
Open Graph description is not detected on the main page of Liu 16. 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: