Tools & Wizards About Us
owasp.github.io screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

owasp.github.io

OWASP Foundation, the Open Source Foundation for Application Security | OWASP Foundation

Page Load Speed

1.8 sec in total

First Response

20 ms

Resources Loaded

1 sec

Page Rendered

724 ms

owasp.github.io screenshot

About Website

Welcome to owasp.github.io homepage info - get ready to check OWASP Github best content for China right away, or after learning these important things about owasp.github.io

OWASP Foundation, the Open Source Foundation for Application Security on the main website for The OWASP Foundation. OWASP is a nonprofit foundation that works to improve the security of software.

Visit owasp.github.io

Key Findings

We analyzed Owasp.github.io page load time and found that the first response time was 20 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

owasp.github.io performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.965

2/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

owasp.github.io

20 ms

owasp.org

49 ms

owasp.org

87 ms

js.cookie.min.js

31 ms

analytics.js

24 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Owasp.github.io, 79% (27 requests) were made to Owasp.org and 9% (3 requests) were made to Calendar.google.com. The less responsive or slowest element that took the longest time to load (526 ms) relates to the external source Calendar.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 803.4 kB (23%)

Content Size

3.5 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Owasp.github.io main page is 3.5 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. 60% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 53.7 kB

  • Original 69.6 kB
  • After minification 67.5 kB
  • After compression 15.9 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 53.7 kB or 77% of the original size.

Image Optimization

-23%

Potential reduce by 749.4 kB

  • Original 3.2 MB
  • After minification 2.5 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. Obviously, OWASP Github needs image optimization as it can save up to 749.4 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 288 B

  • Original 219.3 kB
  • After minification 219.3 kB
  • After compression 219.0 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.

Requests Breakdown

Number of requests can be reduced by 8 (31%)

Requests Now

26

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

owasp.github.io

owasp.github.io

20 ms

owasp.org

owasp.org

49 ms

owasp.org

owasp.org

87 ms

js.cookie.min.js

js.cookie.min.js

31 ms

analytics.js

analytics.js

24 ms

styles.css

styles.css

70 ms

jquery-3.7.1.min.js

jquery-3.7.1.min.js

139 ms

util.js

util.js

201 ms

yaml.min.js

yaml.min.js

58 ms

kjua.min.js

kjua.min.js

124 ms

embed

embed

526 ms

logo.png

logo.png

180 ms

ams-preso-new.jpg

ams-preso-new.jpg

179 ms

SFHeader.png

SFHeader.png

203 ms

staff_andrew.jpg

staff_andrew.jpg

180 ms

bionic_logo_1.png

bionic_logo_1.png

32 ms

tenable_logo.png

tenable_logo.png

27 ms

SailPoint.png

SailPoint.png

79 ms

nedap_logo_hero_digital_blue.png

nedap_logo_hero_digital_blue.png

24 ms

salesforce.png

salesforce.png

28 ms

GuardSquare.png

GuardSquare.png

45 ms

Hitachi.png

Hitachi.png

67 ms

Zimperiumlogo_300x90px.jpeg

Zimperiumlogo_300x90px.jpeg

86 ms

Bloomberg.png

Bloomberg.png

57 ms

Rakuten2022.png

Rakuten2022.png

51 ms

ubuntu-regular.woff

ubuntu-regular.woff

84 ms

fa-solid-900.ttf

fa-solid-900.ttf

124 ms

fa-regular-400.ttf

fa-regular-400.ttf

120 ms

ubuntu-medium.woff

ubuntu-medium.woff

124 ms

fa-brands-400.ttf

fa-brands-400.ttf

153 ms

rs=ABFko382MEpmUkytL_vzKnvVIyQUjehskA

rs=ABFko382MEpmUkytL_vzKnvVIyQUjehskA

4 ms

m=embed

m=embed

10 ms

client.js

client.js

31 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

Accessibility Review

owasp.github.io accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

<frame> or <iframe> elements do not have a title

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

owasp.github.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

owasp.github.io SEO score

92

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

owasp.github.io

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