Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

go.oceg.org

OCEG is the ultimate source for GRC certifications and resources - OCEG

Page Load Speed

3.3 sec in total

First Response

79 ms

Resources Loaded

2.3 sec

Page Rendered

862 ms

go.oceg.org screenshot

About Website

Click here to check amazing Go OCEG content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about go.oceg.org

Your source for all things GRC: governance, risk, and compliance. GRC certifications, education and resources for GRC Professionals.

Visit go.oceg.org

Key Findings

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

Performance Metrics

go.oceg.org performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

go.oceg.org

79 ms

www.oceg.org

142 ms

global.css

294 ms

js

59 ms

2314.js

34 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Go.oceg.org, 69% (45 requests) were made to Cdn.sanity.io and 23% (15 requests) were made to Oceg.org. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn.sanity.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 352.2 kB (16%)

Content Size

2.1 MB

After Optimization

1.8 MB

In fact, the total size of Go.oceg.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. 25% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 137.5 kB

  • Original 164.3 kB
  • After minification 135.7 kB
  • After compression 26.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. This page needs HTML code to be minified as it can gain 28.6 kB, which is 17% 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 137.5 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 214.7 kB

  • Original 2.0 MB
  • After minification 1.8 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, Go OCEG needs image optimization as it can save up to 214.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 22 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 2.5 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 3 (5%)

Requests Now

63

After Optimization

60

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

Accessibility Review

go.oceg.org accessibility score

98

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

Links do not have a discernible name

Best Practices

go.oceg.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

go.oceg.org SEO score

83

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

Links do not have descriptive text

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 Go.oceg.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 Go.oceg.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

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