18.5 sec in total
2.1 sec
16.1 sec
407 ms
Visit lzgd.net now to see the best up-to-date Lzgd content and also check out these interesting facts you probably never knew about lzgd.net
咱山东人自己的招聘信息网。找工作、招人才,上鲁中直聘。淄博亿舟传媒旗下人才招聘信息网。
Visit lzgd.netWe analyzed Lzgd.net page load time and found that the first response time was 2.1 sec and then it took 16.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lzgd.net performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value6.4 s
9/100
25%
Value9.3 s
13/100
10%
Value120 ms
97/100
30%
Value0.005
100/100
15%
Value6.1 s
64/100
10%
2059 ms
831 ms
835 ms
838 ms
839 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 74% of them (86 requests) were addressed to the original Lzgd.net, 3% (4 requests) were made to Static.css.weather.com.cn and 3% (3 requests) were made to Ext.weather.com.cn. The less responsive or slowest element that took the longest time to load (5.9 sec) relates to the external source Static.js.weather.com.cn.
Page size can be reduced by 479.7 kB (18%)
2.7 MB
2.2 MB
In fact, the total size of Lzgd.net main page is 2.7 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. 40% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 68.8 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 12.4 kB, which is 15% 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 68.8 kB or 81% of the original size.
Potential reduce by 180.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. Lzgd images are well optimized though.
Potential reduce by 177.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 177.2 kB or 60% of the original size.
Potential reduce by 53.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. Lzgd.net needs all CSS files to be minified and compressed as it can save up to 53.5 kB or 85% of the original size.
Number of requests can be reduced by 37 (33%)
113
76
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lzgd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lzgd.net
2059 ms
honey.newhunantv.js
831 ms
pswencode.js
835 ms
shifty.js
838 ms
slide.nojquery.js
839 ms
page-global.css
1257 ms
page-index.css
1260 ms
uaredirect.js
741 ms
m.js
3016 ms
74536.js
2554 ms
jquery-1.4.2.min.js
2089 ms
jcarousellite_1.0.1.min.js
1251 ms
23.js
875 ms
22.js
878 ms
24.js
877 ms
tongji.js
698 ms
topbg.png
409 ms
top-ico1.png
410 ms
top-ico2.png
410 ms
logo.png
819 ms
ico1.png
412 ms
ico2.png
809 ms
ad2.gif
1237 ms
20160317093511118.jpg
2060 ms
ad2.jpg
1653 ms
20150212092529164.jpg
1654 ms
20150812083219629.jpg
2050 ms
20151110013220193.jpg
2474 ms
20160317024426300.jpg
2902 ms
20160317024734622.jpg
2903 ms
20160319073353992.jpg
2487 ms
20160318092019542.jpg
2468 ms
20160317055735664.jpg
2900 ms
20160314075634396.jpg
3303 ms
20160316064509862.jpg
3306 ms
20160315064226121.jpg
3322 ms
20160311072624686.jpg
3313 ms
20160317055610113.jpg
3318 ms
20160318093019434.jpg
3734 ms
20160317042614678.jpg
4130 ms
20160317034113858.jpg
4138 ms
20160317023557239.jpg
4147 ms
20160307023230901.jpg
3733 ms
20160307023408330.jpg
3737 ms
20160307023535686.jpg
4147 ms
20160316024413272.jpg
4573 ms
20160215110443383.jpg
4573 ms
20160215110529237.jpg
4953 ms
20160202110405775.jpg
4558 ms
20160318082641837.gif
4968 ms
20160317084730185.jpg
4568 ms
20160317084604509.jpg
4965 ms
74536.html
568 ms
20151110013312788.jpg
1234 ms
20151110013451175.jpg
822 ms
20140714024133922.jpg
823 ms
tongji.do
1176 ms
CA162361108411119040001.js
3040 ms
sh1.gif
4587 ms
20140504104351480.jpg
4579 ms
20140504104503294.jpg
4581 ms
113000756.jpg
4966 ms
hao123.css
2544 ms
jquery.js
3994 ms
b.js
5912 ms
hao123.js
4277 ms
112934920.jpg
4577 ms
0950412482.jpg
4572 ms
1501277967.jpg
4164 ms
line-bg.png
3748 ms
line1.png
3748 ms
dot555.png
3732 ms
index-line.png
3732 ms
bf.png
3325 ms
btn-down.png
3335 ms
play-ico.png
3320 ms
btn-l.png
2907 ms
btn-r.png
3281 ms
ico7.png
3289 ms
gs.gif
1154 ms
gs.gif
3077 ms
blue.png
616 ms
ecom
990 ms
b.css
278 ms
shifty.js
2896 ms
slide.nojquery.js
2904 ms
ico10.png
2899 ms
t1.png
2896 ms
ico13.png
3263 ms
ico131.png
2861 ms
interview.png
2868 ms
ico9.png
2876 ms
list-num-2.png
2484 ms
line-dot.png
2476 ms
ico-l.png
2840 ms
ico-r.png
2848 ms
dui-lian.js
486 ms
ico-top.png
2444 ms
ico16.png
2444 ms
ico21.png
2442 ms
ico22.png
2442 ms
0f000rzcPes8_BovTxfuA6.jpg
2042 ms
close.gif
1484 ms
0f000KHjSt5c1jrkU8I3t6.jpg
2039 ms
ico23.png
2432 ms
ico24.png
2428 ms
h.js
980 ms
101120308.json
573 ms
hm.gif
377 ms
index_icon.gif
282 ms
small.png
1671 ms
pluginlog.aspx
911 ms
o.htm
363 ms
wh.js
673 ms
ac.js
462 ms
hm.gif
371 ms
fp.htm
516 ms
lzgd.net accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
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.
lzgd.net 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
lzgd.net SEO score
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
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lzgd.net 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 Lzgd.net 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.
lzgd.net
Open Graph description is not detected on the main page of Lzgd. 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: