Tools & Wizards About Us

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

ipperwashinquiry.ca

The Ipperwash Inquiry - Home Page

Page Load Speed

2.7 sec in total

First Response

100 ms

Resources Loaded

2.5 sec

Page Rendered

81 ms

About Website

Welcome to ipperwashinquiry.ca homepage info - get ready to check Ipperwash Inquiry best content right away, or after learning these important things about ipperwashinquiry.ca

The Ipperwash Inquiry was established by the Government of Ontario on November 12, 2003, under Public Inquiries Act. Its mandate is to inquire and report on events surrounding the death of Dudley Geor...

Visit ipperwashinquiry.ca

Key Findings

We analyzed Ipperwashinquiry.ca page load time and found that the first response time was 100 ms and then it took 2.6 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

ipperwashinquiry.ca performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

index.html

100 ms

index.html

421 ms

wombat.js

325 ms

AIT_Analytics.js

342 ms

disclaim-element.js

135 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ipperwashinquiry.ca, 8% (1 request) were made to Attorneygeneral.jus.gov.on.ca and 8% (1 request) were made to Partner.archive-it.org. The less responsive or slowest element that took the longest time to load (664 ms) relates to the external source Wayback.archive-it.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.8 kB (75%)

Content Size

174.1 kB

After Optimization

43.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ipperwashinquiry.ca main page is 174.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 128.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 32.9 kB

  • Original 41.5 kB
  • After minification 40.1 kB
  • After compression 8.6 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 32.9 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 36 B

  • Original 2.8 kB
  • After minification 2.8 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. Ipperwash Inquiry images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 97.2 kB

  • Original 128.9 kB
  • After minification 128.8 kB
  • After compression 31.7 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 97.2 kB or 75% of the original size.

CSS Optimization

-74%

Potential reduce by 612 B

  • Original 831 B
  • After minification 402 B
  • After compression 219 B

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. Ipperwashinquiry.ca needs all CSS files to be minified and compressed as it can save up to 612 B or 74% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ipperwash Inquiry. According to our analytics all requests are already optimized.

Network Requests Diagram

Accessibility Review

ipperwashinquiry.ca accessibility score

52

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

ipperwashinquiry.ca best practices score

58

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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

ipperwashinquiry.ca SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    US-ASCII

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ipperwashinquiry.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ipperwashinquiry.ca main page’s claimed encoding is us-ascii. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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