Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

cors.ca

Welcome to Canadian Operational Research Society | Canadian Operational Research Society

Page Load Speed

706 ms in total

First Response

208 ms

Resources Loaded

375 ms

Page Rendered

123 ms

cors.ca screenshot

About Website

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

Visit cors.ca

Key Findings

We analyzed Cors.ca page load time and found that the first response time was 208 ms and then it took 498 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

cors.ca performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.685

7/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

cors.ca

208 ms

cors.css

29 ms

top.jpg

32 ms

men_left.jpg

17 ms

bt_soc_off.jpg

93 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that all of those requests were addressed to Cors.ca and no external sources were called. The less responsive or slowest element that took the longest time to load (208 ms) belongs to the original domain Cors.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.9 kB (18%)

Content Size

248.6 kB

After Optimization

202.6 kB

In fact, the total size of Cors.ca main page is 248.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 220.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 13.8 kB

  • Original 16.7 kB
  • After minification 10.6 kB
  • After compression 2.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 6.1 kB, which is 37% 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 13.8 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 21.3 kB

  • Original 220.1 kB
  • After minification 198.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. Cors images are well optimized though.

CSS Optimization

-92%

Potential reduce by 10.8 kB

  • Original 11.8 kB
  • After minification 9.9 kB
  • After compression 943 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. Cors.ca needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 92% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

19

After Optimization

19

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

Accessibility Review

cors.ca accessibility score

80

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

Best Practices

cors.ca best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

cors.ca SEO score

85

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cors.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 Cors.ca main page’s claimed encoding is windows-1252. 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 Cors. 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: