38.6 sec in total
4.7 sec
33.6 sec
226 ms
Visit lzeweb.com now to see the best up-to-date Lzeweb content and also check out these interesting facts you probably never knew about lzeweb.com
雷州人最大的综合门户,网站设为:论坛交友、博客家园、相册、图读新闻、志愿义工、同城游戏、雷州升级、雷州歌曲等地方特色频道。
Visit lzeweb.comWe analyzed Lzeweb.com page load time and found that the first response time was 4.7 sec and then it took 33.9 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lzeweb.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value5.6 s
18/100
25%
Value9.2 s
13/100
10%
Value1,100 ms
23/100
30%
Value0.012
100/100
15%
Value12.1 s
16/100
10%
4693 ms
4317 ms
10341 ms
4578 ms
28 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 26% of them (25 requests) were addressed to the original Lzeweb.com, 13% (12 requests) were made to Asearch.alicdn.com and 8% (8 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (19.5 sec) belongs to the original domain Lzeweb.com.
Page size can be reduced by 266.5 kB (29%)
912.3 kB
645.8 kB
In fact, the total size of Lzeweb.com main page is 912.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. 50% of websites need less resources to load. Images take 468.2 kB which makes up the majority of the site volume.
Potential reduce by 29.0 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 29.0 kB or 72% of the original size.
Potential reduce by 29.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. Lzeweb images are well optimized though.
Potential reduce by 194.2 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 194.2 kB or 50% of the original size.
Potential reduce by 14.0 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. Lzeweb.com needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 75% of the original size.
Number of requests can be reduced by 41 (45%)
92
51
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lzeweb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
lzeweb.com
4693 ms
web.css
4317 ms
jquery-1.7.2.min.js
10341 ms
slider.js
4578 ms
wb.js
28 ms
adsbygoogle.js
7 ms
show_ads.js
10 ms
ex
4072 ms
logo.gif
3066 ms
op2012.png
8040 ms
4-1212312013060-L.jpg
464 ms
4-160303101SEW.jpg
19525 ms
4-150326150JU44.jpg
4847 ms
4-1403121IG31E.jpg
5093 ms
4-150Q619561a52.jpg
9396 ms
4-14101R04HIO.jpg
7346 ms
4-130622105316210.jpg
14816 ms
4-130325204432K2.jpg
6873 ms
4-13032G01634616.jpg
7712 ms
4-1212312136310-L.jpg
8810 ms
4-121231210940345.jpg
8136 ms
beian.png
10183 ms
weixin.jpg
3528 ms
rep.png
8546 ms
dot.png
8985 ms
001.gif
9308 ms
tags.png
10786 ms
dots.gif
9848 ms
icon.png
10277 ms
ca-pub-7146102682134205.js
48 ms
zrt_lookup.html
36 ms
show_ads_impl.js
51 ms
ads
305 ms
ads
248 ms
osd.js
42 ms
ads
207 ms
tanxssp.js
369 ms
12120228428982399843
40 ms
abg.js
42 ms
m_js_controller.js
54 ms
googlelogo_color_112x36dp.png
35 ms
css
109 ms
s
31 ms
x_button_blue2.png
30 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
11 ms
mobile_unified_button_icon_white.png
70 ms
ex
927 ms
PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf
127 ms
acbeacon2.html
328 ms
spf
1012 ms
TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png
265 ms
creation-164857uaSd33GHMrk-437386.html
330 ms
TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png
263 ms
TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png
265 ms
TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png
264 ms
h.js
1619 ms
activeview
19 ms
activeview
30 ms
t.gif
3931 ms
tanxclick.js
51 ms
tns.simba.taobao.com
3783 ms
loading1.gif
16 ms
bundle.js
1982 ms
hm.gif
309 ms
client.js
4 ms
iframeWidget.js
8 ms
aj_relationship.php
2595 ms
TB2lQyokVXXXXcMXXXXXXXXXXXX_!!0-saturn_solar.jpg_sum.jpg
108 ms
feature_v1.htm
1144 ms
TB2lQyokVXXXXcMXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
123 ms
TB29DtWjFXXXXbnXpXXXXXXXXXX_!!113853639-0-saturn_solar.jpg_250x250.jpg
116 ms
TB2xpmTdXXXXXcXXXXXXXXXXXXX_!!26431609-0-saturn_solar.jpg_250x250.jpg
123 ms
TB22EJOipXXXXcZXXXXXXXXXXXX_!!33274654-0-saturn_solar.jpg_250x250.jpg
117 ms
TB2d5ALgVXXXXXHXpXXXXXXXXXX_!!43695494-0-saturn_solar.jpg_250x250.jpg
122 ms
TB2MRDtmpXXXXblXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
128 ms
TB2YqdwlVXXXXb1XpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
133 ms
TB2YHEdgpXXXXc.XXXXXXXXXXXX_!!16953757-0-saturn_solar.jpg_250x250.jpg
145 ms
TB29QTsmpXXXXXeXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
133 ms
TB2iUjQmpXXXXXeXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
130 ms
TB2dEAHkFXXXXXRXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
148 ms
TB11KimHpXXXXXJXXXXQKC3FVXX-27-59.png
266 ms
TB1Mng.HpXXXXb4XFXX1qpgFpXX-20-14.gif
275 ms
TB1LKo.HpXXXXbiXFXX91dEGXXX-29-16.png
110 ms
app.gif
1935 ms
followbutton.php
670 ms
um.js
367 ms
img
1192 ms
um.json
2163 ms
getDeviceInfo
1171 ms
followButton.css
2048 ms
sso.js
6 ms
followButton.js
4 ms
suda.js
5 ms
getDeviceInfo
2110 ms
bg_flbtn.png
23 ms
b.gif
1092 ms
lzeweb.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Links do not have a discernible name
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
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.
lzeweb.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
General
Impact
Issue
Detected JavaScript libraries
lzeweb.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lzeweb.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 Lzeweb.com 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.
lzeweb.com
Open Graph description is not detected on the main page of Lzeweb. 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: