Tools & Wizards About Us
zglb.org screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

zglb.org

中国老兵网★老兵自己的门户网站!

Page Load Speed

12.4 sec in total

First Response

700 ms

Resources Loaded

11.3 sec

Page Rendered

373 ms

zglb.org screenshot

About Website

Welcome to zglb.org homepage info - get ready to check Zglb best content right away, or after learning these important things about zglb.org

中国老兵网(www.zglb.org)创办于2008年8月,致力于为所有老兵量身打造的大型综合性门户网站。

Visit zglb.org

Key Findings

We analyzed Zglb.org page load time and found that the first response time was 700 ms and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

zglb.org performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

zglb.org

700 ms

zglb.org

916 ms

www.zglb.org

1149 ms

bootstrap.min.css

467 ms

index_flash.css

698 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 70% of them (47 requests) were addressed to the original Zglb.org, 12% (8 requests) were made to Img.t.sinajs.cn and 3% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain Zglb.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.5 kB (8%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zglb.org main page is 2.1 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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 28.4 kB

  • Original 36.6 kB
  • After minification 34.1 kB
  • After compression 8.2 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 28.4 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 34.7 kB

  • Original 1.7 MB
  • After minification 1.7 MB

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. Zglb images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 65.9 kB

  • Original 229.2 kB
  • After minification 229.2 kB
  • After compression 163.3 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 65.9 kB or 29% of the original size.

CSS Optimization

-56%

Potential reduce by 38.5 kB

  • Original 68.5 kB
  • After minification 68.5 kB
  • After compression 30.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. Zglb.org needs all CSS files to be minified and compressed as it can save up to 38.5 kB or 56% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (17%)

Requests Now

64

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zglb. 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 from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

zglb.org

zglb.org

700 ms

zglb.org

zglb.org

916 ms

www.zglb.org

www.zglb.org

1149 ms

bootstrap.min.css

bootstrap.min.css

467 ms

index_flash.css

index_flash.css

698 ms

softmoon_zglb.css

softmoon_zglb.css

883 ms

jquery.min.js

jquery.min.js

2039 ms

cms.js

cms.js

1122 ms

bootstrap.js

bootstrap.js

1137 ms

logo.gif

logo.gif

231 ms

index.php

index.php

1519 ms

top-mlsh.jpg

top-mlsh.jpg

223 ms

head_menu_bg.jpg

head_menu_bg.jpg

331 ms

3b9ff0c10a1e674.png

3b9ff0c10a1e674.png

2514 ms

880ea4732e5b0.jpg

880ea4732e5b0.jpg

2445 ms

28fb57b14318b39.jpg

28fb57b14318b39.jpg

1272 ms

d498ecacfbc02d4.jpg

d498ecacfbc02d4.jpg

882 ms

25edd4a53e484d8.jpg

25edd4a53e484d8.jpg

784 ms

348x217_auto.jpg

348x217_auto.jpg

2048 ms

348x217_auto.jpg

348x217_auto.jpg

1659 ms

index_ad_years_bg.png

index_ad_years_bg.png

5272 ms

212x140_auto.jpg

212x140_auto.jpg

3390 ms

134P16451-0-lp.jpg

134P16451-0-lp.jpg

3410 ms

10363R506-0-lp.jpg

10363R506-0-lp.jpg

4132 ms

index_lbfw_title.jpg

index_lbfw_title.jpg

2673 ms

cht_i7.jpg

cht_i7.jpg

5357 ms

zt2.jpg

zt2.jpg

3362 ms

zt4.jpg

zt4.jpg

3840 ms

jianjun86.jpg

jianjun86.jpg

4161 ms

206x120_auto.jpg

206x120_auto.jpg

4160 ms

206x120_auto.jpg

206x120_auto.jpg

4295 ms

206x120_auto.jpg

206x120_auto.jpg

4575 ms

206x120_auto.jpg

206x120_auto.jpg

4422 ms

206x120_auto.jpg

206x120_auto.jpg

4609 ms

206x120_auto.jpg

206x120_auto.jpg

6476 ms

206x120_auto.jpg

206x120_auto.jpg

4813 ms

1-1411252232340-L.jpg

1-1411252232340-L.jpg

4922 ms

22320G438-0-lp.jpg

22320G438-0-lp.jpg

4957 ms

22314915J-0-lp.jpg

22314915J-0-lp.jpg

6218 ms

f_rmw.jpg

f_rmw.jpg

5129 ms

f_gfb.jpg

f_gfb.jpg

5147 ms

f_zgjw.jpg

f_zgjw.jpg

5352 ms

f_xhjw.jpg

f_xhjw.jpg

5372 ms

f_zgw.jpg

f_zgw.jpg

5425 ms

f_hqw.jpg

f_hqw.jpg

5501 ms

f_sohu.jpg

f_sohu.jpg

5575 ms

hm.js

hm.js

1161 ms

push.js

push.js

1135 ms

f_tx.jpg

f_tx.jpg

5452 ms

f_ml.jpg

f_ml.jpg

5509 ms

hm.gif

hm.gif

313 ms

weiboShow.css

weiboShow.css

1311 ms

skin_default.css

skin_default.css

1789 ms

gaea_1_20.js

gaea_1_20.js

815 ms

show.js

show.js

818 ms

suda.js

suda.js

966 ms

718810f5gw1emewfer8zdj20yu0yu0wn.jpg

718810f5gw1emewfer8zdj20yu0yu0wn.jpg

1514 ms

48f1c255gw1erjz7a4hgkg20se0kv1is.gif

48f1c255gw1erjz7a4hgkg20se0kv1is.gif

1222 ms

wb_logo16_a.png

wb_logo16_a.png

551 ms

icon_user.png

icon_user.png

593 ms

btns_bg.png

btns_bg.png

540 ms

icon_follow.png

icon_follow.png

613 ms

567acccajw1eriy35rtnwj20hs0nogot.jpg

567acccajw1eriy35rtnwj20hs0nogot.jpg

1301 ms

bg_trans.png

bg_trans.png

507 ms

icon_tips.png

icon_tips.png

478 ms

a.gif

a.gif

1174 ms

tmp.gif

tmp.gif

1100 ms

Accessibility Review

zglb.org accessibility score

69

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

zglb.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

zglb.org SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zglb.org 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 Zglb.org 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.

Social Sharing Optimization

zglb.org

Open Graph description is not detected on the main page of Zglb. 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: