Tools & Wizards About Us
zhangge.net screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

zhangge.net

张戈博客 | 关注IT运维技术及互联网的个人博客

Page Load Speed

26.1 sec in total

First Response

279 ms

Resources Loaded

25 sec

Page Rendered

877 ms

zhangge.net screenshot

About Website

Welcome to zhangge.net homepage info - get ready to check Zhangge best content for China right away, or after learning these important things about zhangge.net

张戈博客是关注互联网以及分享IT运维工作经验的个人博客，由系统运维、脚本编程以及资源分享等分类组成，涵盖了操作系统教程、运维经验、脚本语言以及网络资源等。

Visit zhangge.net

Key Findings

We analyzed Zhangge.net page load time and found that the first response time was 279 ms and then it took 25.8 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.

Performance Metrics

zhangge.net performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

zhangge.net

279 ms

zhangge.net

55 ms

play_font.min.css

313 ms

app.min.css

854 ms

style.css

313 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Zhangge.net, 92% (97 requests) were made to Res.zgboke.com and 2% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (13.1 sec) relates to the external source Res.zgboke.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 246.5 kB (11%)

Content Size

2.3 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zhangge.net main page is 2.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 106.9 kB

  • Original 148.7 kB
  • After minification 148.4 kB
  • After compression 41.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. 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 106.9 kB or 72% of the original size.

Image Optimization

-8%

Potential reduce by 137.2 kB

  • Original 1.8 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. Zhangge images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.8 kB

  • Original 233.1 kB
  • After minification 233.1 kB
  • After compression 231.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 620 B

  • Original 77.8 kB
  • After minification 77.8 kB
  • After compression 77.2 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. Zhangge.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

95

After Optimization

79

  • Images
  • JavaScript
  • CSS

The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zhangge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

zhangge.net

zhangge.net

279 ms

zhangge.net

zhangge.net

55 ms

play_font.min.css

play_font.min.css

313 ms

app.min.css

app.min.css

854 ms

style.css

style.css

313 ms

style.css

style.css

313 ms

style.min.css

style.min.css

315 ms

jquery.js

jquery.js

333 ms

jquery-migrate.min.js

jquery-migrate.min.js

322 ms

app.min.js

app.min.js

520 ms

email-decode.min.js

email-decode.min.js

4 ms

diydialog.js

diydialog.js

328 ms

default.css

default.css

324 ms

baiduAudio.js

baiduAudio.js

329 ms

baiduAudio.css

baiduAudio.css

334 ms

comment-reply.min.js

comment-reply.min.js

341 ms

custom.js

custom.js

343 ms

text-autospace.js

text-autospace.js

342 ms

push.js

push.js

1267 ms

hm.js

hm.js

10778 ms

logo-ge.png

logo-ge.png

178 ms

1548595106-logo.jpg

1548595106-logo.jpg

161 ms

nexus1.jpg

nexus1.jpg

331 ms

1548309339-docker.jpg

1548309339-docker.jpg

161 ms

fast.jpg

fast.jpg

877 ms

ccs.jpg

ccs.jpg

160 ms

ceph.jpg

ceph.jpg

164 ms

attack.jpg

attack.jpg

162 ms

1635418963-APISIX.png

1635418963-APISIX.png

164 ms

baiduyjs.png

baiduyjs.png

163 ms

1660738087-grpc.webp

1660738087-grpc.webp

328 ms

python.png

python.png

165 ms

1650021797-logo.png

1650021797-logo.png

164 ms

safe.jpg

safe.jpg

165 ms

41.jpg

41.jpg

166 ms

sendcloud.png

sendcloud.png

167 ms

SSL-Security.jpg

SSL-Security.jpg

167 ms

qiniu.png

qiniu.png

168 ms

bat.png

bat.png

169 ms

14.jpg

14.jpg

169 ms

26.jpg

26.jpg

170 ms

backup.png

backup.png

169 ms

404.png

404.png

170 ms

linux.jpg

linux.jpg

170 ms

linux.jpg

linux.jpg

171 ms

10.jpg

10.jpg

172 ms

SecureCRT3.png

SecureCRT3.png

172 ms

disk.gif

disk.gif

173 ms

a9d1c576a7f4b37672b04a057e4f6a03.jpg

a9d1c576a7f4b37672b04a057e4f6a03.jpg

174 ms

45.jpg

45.jpg

174 ms

myloud2.png

myloud2.png

175 ms

http-2.0.jpg

http-2.0.jpg

174 ms

web1.png

web1.png

175 ms

nginx.png

nginx.png

176 ms

42.jpg

42.jpg

176 ms

21.jpg

21.jpg

177 ms

php7.png

php7.png

27 ms

web2.png

web2.png

26 ms

wordpress.png

wordpress.png

25 ms

7.jpg

7.jpg

26 ms

feed.gif

feed.gif

29 ms

crazy.png

crazy.png

27 ms

face-happy.png

face-happy.png

49 ms

Play-regular.ttf

Play-regular.ttf

10284 ms

Play-bold.ttf

Play-bold.ttf

31 ms

fa-solid-900.woff

fa-solid-900.woff

697 ms

fa-regular-400.woff

fa-regular-400.woff

10283 ms

fa-brands-400.woff

fa-brands-400.woff

699 ms

bulletin.gif

bulletin.gif

669 ms

1660738087-grpc.webp

1660738087-grpc.webp

10139 ms

bl.png

bl.png

9745 ms

tr.png

tr.png

9591 ms

wechat-zan.png

wechat-zan.png

9897 ms

wechat.jpg

wechat.jpg

9592 ms

zfb.png

zfb.png

9591 ms

1548595106-logo.jpg

1548595106-logo.jpg

10382 ms

nexus1.jpg

nexus1.jpg

11982 ms

1548309339-docker.jpg

1548309339-docker.jpg

11930 ms

fast.jpg

fast.jpg

9836 ms

ccs.jpg

ccs.jpg

13083 ms

ceph.jpg

ceph.jpg

0 ms

attack.jpg

attack.jpg

10075 ms

1635418963-APISIX.png

1635418963-APISIX.png

11355 ms

baiduyjs.png

baiduyjs.png

12172 ms

chat_server.png

chat_server.png

12057 ms

ccs.jpg

ccs.jpg

2212 ms

hm.gif

hm.gif

340 ms

ceph.jpg

ceph.jpg

14 ms

1660738087-grpc.webp

1660738087-grpc.webp

114 ms

1635418963-APISIX.png

1635418963-APISIX.png

110 ms

baiduyjs.png

baiduyjs.png

191 ms

1548595106-logo.jpg

1548595106-logo.jpg

111 ms

nexus1.jpg

nexus1.jpg

111 ms

1548309339-docker.jpg

1548309339-docker.jpg

112 ms

fast.jpg

fast.jpg

115 ms

1548595106-logo.jpg

1548595106-logo.jpg

113 ms

nexus1.jpg

nexus1.jpg

363 ms

1548309339-docker.jpg

1548309339-docker.jpg

114 ms

fast.jpg

fast.jpg

114 ms

ccs.jpg

ccs.jpg

364 ms

ceph.jpg

ceph.jpg

114 ms

1635418963-APISIX.png

1635418963-APISIX.png

364 ms

baiduyjs.png

baiduyjs.png

115 ms

1660738087-grpc.webp

1660738087-grpc.webp

77 ms

ccs.jpg

ccs.jpg

206 ms

Accessibility Review

zhangge.net accessibility score

64

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

zhangge.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

zhangge.net SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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

High

Tap targets are not sized appropriately

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 Zhangge.net 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 Zhangge.net 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

zhangge.net

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