Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

controlgap.com

Control Gap Home Page

Page Load Speed

5.7 sec in total

First Response

140 ms

Resources Loaded

5.1 sec

Page Rendered

459 ms

controlgap.com screenshot

About Website

Click here to check amazing Control Gap content for Canada. Otherwise, check out these important facts you probably never knew about controlgap.com

Control Gap helps you safeguard sensitive data and reduce security risk. We are Canada’s foremost leader in compliance validation and advisory services.

Visit controlgap.com

Key Findings

We analyzed Controlgap.com page load time and found that the first response time was 140 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

controlgap.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

controlgap.com

140 ms

controlgap.com

3211 ms

wp-emoji-release.min.js

73 ms

styles.css

138 ms

style.css

200 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 59% of them (48 requests) were addressed to the original Controlgap.com, 9% (7 requests) were made to Google.com and 6% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Controlgap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 725.3 kB (29%)

Content Size

2.5 MB

After Optimization

1.8 MB

In fact, the total size of Controlgap.com main page is 2.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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 61.4 kB

  • Original 74.5 kB
  • After minification 70.3 kB
  • After compression 13.1 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 61.4 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 94.7 kB

  • Original 1.6 MB
  • After minification 1.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. Control Gap images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 337.6 kB

  • Original 516.6 kB
  • After minification 510.5 kB
  • After compression 179.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 337.6 kB or 65% of the original size.

CSS Optimization

-63%

Potential reduce by 231.6 kB

  • Original 367.7 kB
  • After minification 364.1 kB
  • After compression 136.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. Controlgap.com needs all CSS files to be minified and compressed as it can save up to 231.6 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (57%)

Requests Now

67

After Optimization

29

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

Accessibility Review

controlgap.com accessibility score

93

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.

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

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

controlgap.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

controlgap.com SEO score

93

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

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 Controlgap.com 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 Controlgap.com 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 Control Gap. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: