Tools & Wizards About Us
gitbooks.io screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gitbooks.io

GitBook (Legacy) · Documentation made easy

Page Load Speed

2.8 sec in total

First Response

81 ms

Resources Loaded

2.5 sec

Page Rendered

295 ms

gitbooks.io screenshot

About Website

Welcome to gitbooks.io homepage info - get ready to check Git Book S best content for China right away, or after learning these important things about gitbooks.io

GitBook is where you create, write and organize documentation and books with your team.

Visit gitbooks.io

Key Findings

We analyzed Gitbooks.io page load time and found that the first response time was 81 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

gitbooks.io performance score

0

Network Requests Diagram

www.gitbook.io

81 ms

www.gitbook.com

101 ms

style.css

72 ms

socicon.css

104 ms

128.png

240 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Gitbooks.io, 29% (8 requests) were made to Gitbook.com and 11% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (329 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 334.1 kB (57%)

Content Size

584.2 kB

After Optimization

250.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gitbooks.io main page is 584.2 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. 30% of websites need less resources to load. Javascripts take 222.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.7 kB

  • Original 29.2 kB
  • After minification 24.0 kB
  • After compression 6.5 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 5.2 kB, which is 18% 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 22.7 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 9.8 kB

  • Original 151.0 kB
  • After minification 141.2 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. Git Book S images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 148.3 kB

  • Original 222.6 kB
  • After minification 222.6 kB
  • After compression 74.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 148.3 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 153.3 kB

  • Original 181.4 kB
  • After minification 180.5 kB
  • After compression 28.1 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. Gitbooks.io needs all CSS files to be minified and compressed as it can save up to 153.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (19%)

Requests Now

26

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.gitbook.io

www.gitbook.io

81 ms

www.gitbook.com

www.gitbook.com

101 ms

style.css

style.css

72 ms

socicon.css

socicon.css

104 ms

128.png

128.png

240 ms

ZeroClipboard.min.js

ZeroClipboard.min.js

152 ms

app.js

app.js

166 ms

237 ms

databricks.png

databricks.png

232 ms

cloudfoundry.jpg

cloudfoundry.jpg

233 ms

djangogirl.jpg

djangogirl.jpg

223 ms

google-developers.jpg

google-developers.jpg

221 ms

jan.jpg

jan.jpg

222 ms

columbia.jpg

columbia.jpg

300 ms

kowen.jpg

kowen.jpg

299 ms

dale.jpg

dale.jpg

298 ms

preview.jpg

preview.jpg

300 ms

sdk.js

sdk.js

329 ms

widgets.js

widgets.js

247 ms

book.png

book.png

118 ms

robot.png

robot.png

119 ms

octicons.woff

octicons.woff

8 ms

channel.html

channel.html

16 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

30 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

90 ms

62 ms

xd_arbiter.php

xd_arbiter.php

268 ms

jot

jot

96 ms

SEO Factors

gitbooks.io SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gitbooks.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Gitbooks.io 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

gitbooks.io

Open Graph data is detected on the main page of Git Book S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: