Tools & Wizards About Us
proof.utoronto.ca screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

proof.utoronto.ca

PROOF - Identifying policy options to reduce household food insecurity

Page Load Speed

3.6 sec in total

First Response

407 ms

Resources Loaded

2.3 sec

Page Rendered

871 ms

proof.utoronto.ca screenshot

About Website

Welcome to proof.utoronto.ca homepage info - get ready to check PROOF Utoronto best content for Canada right away, or after learning these important things about proof.utoronto.ca

Identifying Policy Options to Reduce Household Food Insecurity in Canada Despite the long history of food banks in Canada, household food insecurity has persisted at high rates. PROOF’s research highl...

Visit proof.utoronto.ca

Key Findings

We analyzed Proof.utoronto.ca page load time and found that the first response time was 407 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 60% of websites can load faster.

Performance Metrics

proof.utoronto.ca performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.9 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value820 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

proof.utoronto.ca

407 ms

style.min.css

98 ms

styles.css

64 ms

front.css

65 ms

817bc64da3fba42b3be200882f0a4201.min.css

223 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 89% of them (25 requests) were addressed to the original Proof.utoronto.ca, 4% (1 request) were made to Googletagmanager.com and 4% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (407 ms) belongs to the original domain Proof.utoronto.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (36%)

Content Size

7.0 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Proof.utoronto.ca main page is 7.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 117.3 kB

  • Original 137.0 kB
  • After minification 136.2 kB
  • After compression 19.7 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 117.3 kB or 86% of the original size.

Image Optimization

-17%

Potential reduce by 761.9 kB

  • Original 4.6 MB
  • After minification 3.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, PROOF Utoronto needs image optimization as it can save up to 761.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 583.6 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 453.8 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 583.6 kB or 56% of the original size.

CSS Optimization

-87%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 165.3 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. Proof.utoronto.ca needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (58%)

Requests Now

24

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proof.utoronto.ca

proof.utoronto.ca

407 ms

style.min.css

style.min.css

98 ms

styles.css

styles.css

64 ms

front.css

front.css

65 ms

817bc64da3fba42b3be200882f0a4201.min.css

817bc64da3fba42b3be200882f0a4201.min.css

223 ms

jquery.min.js

jquery.min.js

125 ms

jquery-migrate.min.js

jquery-migrate.min.js

116 ms

js

js

57 ms

hooks.min.js

hooks.min.js

99 ms

i18n.min.js

i18n.min.js

100 ms

index.js

index.js

102 ms

index.js

index.js

108 ms

api.js

api.js

34 ms

wp-polyfill.min.js

wp-polyfill.min.js

137 ms

index.js

index.js

119 ms

0286d37a0706423faebec49b898f09f7.min.js

0286d37a0706423faebec49b898f09f7.min.js

312 ms

PROOF-3.png

PROOF-3.png

51 ms

homepage.png

homepage.png

61 ms

Illustration-A-problem-of-inadequate-income-not-solved-by-food.png

Illustration-A-problem-of-inadequate-income-not-solved-by-food.png

60 ms

PROOF-2022-report-spread-1.png

PROOF-2022-report-spread-1.png

51 ms

Household-Food-Insecurity-2022-cover.png

Household-Food-Insecurity-2022-cover.png

111 ms

senate-submission-thumb.png

senate-submission-thumb.png

114 ms

2023budgetreflection.png

2023budgetreflection.png

68 ms

PROOF-COLOUR.png

PROOF-COLOUR.png

112 ms

recaptcha__en.js

recaptcha__en.js

26 ms

awb-icons.woff

awb-icons.woff

60 ms

fa-solid-900.woff

fa-solid-900.woff

61 ms

fa-regular-400.woff

fa-regular-400.woff

77 ms

Accessibility Review

proof.utoronto.ca accessibility score

95

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.

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

proof.utoronto.ca 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

proof.utoronto.ca SEO score

93

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

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 Proof.utoronto.ca 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 Proof.utoronto.ca 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

proof.utoronto.ca

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