43.1 sec in total
1.4 sec
41.2 sec
515 ms
Click here to check amazing Qz Lnest content for China. Otherwise, check out these important facts you probably never knew about qz.lnest.com
港湾有巢CMS,分销系统,拼团系统,系统开发,app需求定制,电商商城定制,平台开发
Visit qz.lnest.comWe analyzed Qz.lnest.com page load time and found that the first response time was 1.4 sec and then it took 41.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 13 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
qz.lnest.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value17.0 s
0/100
25%
Value13.6 s
2/100
10%
Value90 ms
99/100
30%
Value0.756
6/100
15%
Value14.6 s
8/100
10%
1415 ms
1540 ms
2084 ms
320 ms
564 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 89% of them (132 requests) were addressed to the original Qz.lnest.com, 3% (5 requests) were made to Dgt.zoosnet.net and 3% (4 requests) were made to Zidc.com.cn. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Qz.lnest.com.
Page size can be reduced by 1.2 MB (19%)
6.5 MB
5.3 MB
In fact, the total size of Qz.lnest.com main page is 6.5 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. 35% of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 71.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 20.6 kB, which is 25% 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 71.7 kB or 87% of the original size.
Potential reduce by 960.3 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. Obviously, Qz Lnest needs image optimization as it can save up to 960.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 140.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 140.8 kB or 61% of the original size.
Potential reduce by 32.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. Qz.lnest.com needs all CSS files to be minified and compressed as it can save up to 32.9 kB or 85% of the original size.
Number of requests can be reduced by 29 (22%)
129
100
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qz Lnest. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
qz.lnest.com
1415 ms
css.css
1540 ms
jquery.js
2084 ms
common.js
320 ms
layout.js
564 ms
LsJS.aspx
3305 ms
o.js
988 ms
tcym
937 ms
logo.png
622 ms
20140513014336641.jpg
11397 ms
qq.png
340 ms
sub_menu_img.png
367 ms
20151028032656796.jpg
7284 ms
20150608071851669.jpg
3159 ms
20150608071826312.jpg
2799 ms
20140516115533674.jpg
3900 ms
view_img.jpg
645 ms
copy_btn.jpg
904 ms
20150623101207726.png
16879 ms
20150623101722303.png
10492 ms
20140515105331492.jpg
6262 ms
20140403035959461.jpg
6564 ms
20140325040738601.jpg
11181 ms
20140515091705848.jpg
11940 ms
20140514024024112.jpg
10741 ms
20140521030116746.jpg
9970 ms
20140515042609797.jpg
12565 ms
20140521055037643.jpg
13288 ms
20140514025647707.jpg
13621 ms
20140514055827411.jpg
13903 ms
20140515053102351.jpg
14548 ms
20140326053011975.jpg
13470 ms
20140326044548856.jpg
16783 ms
20140515043451284.jpg
16313 ms
20140516031104858.jpg
16495 ms
20140325045718360.jpg
20498 ms
20140516100204665.jpg
17909 ms
20140515090240443.jpg
20498 ms
20140326032730297.jpg
19363 ms
20140326032640524.jpg
18113 ms
20140121110254335.jpg
20498 ms
20140326054532753.jpg
18703 ms
20140408093750386.jpg
18657 ms
20140325045635607.jpg
20497 ms
20140514021626500.jpg
20497 ms
20140513100934928.jpg
8560 ms
20140515021006204.jpg
20173 ms
20140515093030809.jpg
20147 ms
20140515090106555.jpg
19897 ms
20131228090738846.jpg
19868 ms
20150923034902995.png
19608 ms
JS5.aspx
2036 ms
20140515115838515.jpg
19709 ms
2.gif
2087 ms
20140326054401333.jpg
18365 ms
1.gif
2774 ms
7.gif
10804 ms
20140325041724743.jpg
19606 ms
20140515093628800.jpg
18024 ms
20140514054041753.jpg
17570 ms
20140325035752900.jpg
14343 ms
daoqi
1177 ms
713 ms
20140521051139404.jpg
15325 ms
20140516113655535.jpg
14644 ms
20140326042954349.jpg
19285 ms
20140326035126877.jpg
20323 ms
daoqi
356 ms
357 ms
20140514055352629.jpg
15110 ms
20140414040310361.png
12420 ms
20140414035431979.png
12021 ms
20140414034317910.png
12247 ms
20140414031222229.png
12089 ms
20140412045950827.png
13869 ms
20140414024645490.png
11475 ms
20140412050235510.png
9802 ms
20131227111857581.jpg
10118 ms
20140412051442650.png
9664 ms
20140412035624940.png
12070 ms
20140412035409612.png
9311 ms
20140412031532366.png
9239 ms
20140412024542871.png
10754 ms
20140414024157533.png
9443 ms
20140412040426832.png
10587 ms
20140414025853671.png
8192 ms
20140412051705484.png
10525 ms
20140414035710282.png
8726 ms
20140412052616799.png
9030 ms
20140412045725976.png
11727 ms
20140412031236543.png
9318 ms
20140414040937645.png
9910 ms
20140414035247471.png
9831 ms
20140414034151186.png
9822 ms
20140414030603377.png
10087 ms
20140412052008233.png
11085 ms
20140414040727859.png
9376 ms
20140414033611743.png
8748 ms
20140414031516143.png
7800 ms
20150107091545156.png
7144 ms
20140412045524738.png
7474 ms
20140412042619331.png
6848 ms
20140412033153148.png
6633 ms
con_01_img.jpg
7523 ms
con_02_img.jpg
6988 ms
con_03_img.jpg
6613 ms
more_btn.jpg
6436 ms
20150805042731768.jpg
6964 ms
thumb_346_269_20140821093928881.jpg
6730 ms
20140610095714894.png
6395 ms
qq_img.png
6035 ms
header_bg.png
6388 ms
phone_ico.png
5734 ms
search_input.png
5738 ms
search_btn.png
5337 ms
p_ico_off.png
4946 ms
menu_ico.png
4541 ms
banner_bg.png
4325 ms
banner_con_bg.png
4176 ms
focus_on_ico.jpg
3956 ms
focus_off_ico.jpg
3839 ms
main_box_01_bg.png
3681 ms
main_box_01_tit.png
3586 ms
bar_bg.png
3649 ms
main_box_02_tit.jpg
3335 ms
tab_title_c_02.gif
3341 ms
tab_off_02.png
3292 ms
news_box_tit.gif
3302 ms
news_01_tit.jpg
2902 ms
news_ico.gif
2891 ms
news_02_tit.jpg
2684 ms
news_03_tit.jpg
2687 ms
main_box_05.jpg
2671 ms
top_btn.jpg
2698 ms
main_box_05_list.gif
2428 ms
list_01_dt.png
2438 ms
main_box_05_dd.gif
2370 ms
list_02_dt.png
2075 ms
list_03_dt.png
2001 ms
list_04_dt.png
2162 ms
list_05_dt.png
2150 ms
tab_on_02.png
1855 ms
tab_on_bg.jpg
1830 ms
tab_list_li.jpg
1806 ms
img_box_txt.jpg
1756 ms
o.htm
1251 ms
ac.js
505 ms
wh.js
792 ms
fp.htm
465 ms
qz.lnest.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
qz.lnest.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
qz.lnest.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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qz.lnest.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 Qz.lnest.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.
qz.lnest.com
Open Graph description is not detected on the main page of Qz Lnest. 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: