Tools & Wizards About Us
jbake.org screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

jbake.org

JBake - Java based open source static site/blog generator

Page Load Speed

843 ms in total

First Response

58 ms

Resources Loaded

683 ms

Page Rendered

102 ms

jbake.org screenshot

About Website

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

JBake is a Java based, open source, static site/blog generator for developers.

Visit jbake.org

Key Findings

We analyzed Jbake.org page load time and found that the first response time was 58 ms and then it took 785 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

jbake.org performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

jbake.org

58 ms

jbake.org

62 ms

bootstrap.min.css

40 ms

asciidoctor.css

48 ms

bootstrap-responsive.min.css

57 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 45% of them (10 requests) were addressed to the original Jbake.org, 18% (4 requests) were made to Platform.twitter.com and 9% (2 requests) were made to Badges.gitter.im. The less responsive or slowest element that took the longest time to load (389 ms) relates to the external source Badges.gitter.im.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.5 kB (60%)

Content Size

12.5 kB

After Optimization

5.0 kB

  • HTML
  • Images

In fact, the total size of Jbake.org main page is 12.5 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. 20% of websites need less resources to load. HTML takes 10.8 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 7.4 kB

  • Original 10.8 kB
  • After minification 8.8 kB
  • After compression 3.4 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 2.0 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 7.4 kB or 69% of the original size.

Image Optimization

-1%

Potential reduce by 16 B

  • Original 1.7 kB
  • After minification 1.7 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. JBake images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 9 (47%)

Requests Now

19

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jbake.org

jbake.org

58 ms

jbake.org

jbake.org

62 ms

bootstrap.min.css

bootstrap.min.css

40 ms

asciidoctor.css

asciidoctor.css

48 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

57 ms

prettify.css

prettify.css

51 ms

jbake_logo.png

jbake_logo.png

51 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

71 ms

bootstrap.min.js

bootstrap.min.js

71 ms

prettify.js

prettify.js

89 ms

js

js

64 ms

font-awesome.css

font-awesome.css

26 ms

widgets.js

widgets.js

79 ms

master.svg

master.svg

218 ms

2q7hvg03wsjx953b

2q7hvg03wsjx953b

385 ms

jbake.svg

jbake.svg

389 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

21 ms

settings

settings

71 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

embeds

embeds

23 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

13 ms

repo.svg

repo.svg

95 ms

Accessibility Review

jbake.org accessibility score

59

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

jbake.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

jbake.org SEO score

92

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

jbake.org

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