Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

torontosaints.com

St. Stanislaus College Alumni Association - Toronto | Home

Page Load Speed

2.3 sec in total

First Response

732 ms

Resources Loaded

1.3 sec

Page Rendered

243 ms

torontosaints.com screenshot

About Website

Click here to check amazing Toronto Saints content. Otherwise, check out these important facts you probably never knew about torontosaints.com

St. Stanislaus College Canada Alumni Association

Visit torontosaints.com

Key Findings

We analyzed Torontosaints.com page load time and found that the first response time was 732 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

torontosaints.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.232

54/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

torontosaints.com

732 ms

base.css

57 ms

ddlevelsmenu-base.css

111 ms

ddlevelsmenu-topbar.css

109 ms

ddlevelsmenu-sidebar.css

112 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 95% of them (37 requests) were addressed to the original Torontosaints.com, 3% (1 request) were made to Statcounter.com and 3% (1 request) were made to C.statcounter.com. The less responsive or slowest element that took the longest time to load (732 ms) belongs to the original domain Torontosaints.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.2 kB (11%)

Content Size

305.4 kB

After Optimization

272.2 kB

In fact, the total size of Torontosaints.com main page is 305.4 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. 25% of websites need less resources to load. Images take 259.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 24.4 kB

  • Original 29.7 kB
  • After minification 22.1 kB
  • After compression 5.3 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 7.6 kB, which is 26% 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 24.4 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 1.8 kB

  • Original 259.0 kB
  • After minification 257.3 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. Toronto Saints images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 3.7 kB

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

CSS Optimization

-40%

Potential reduce by 3.4 kB

  • Original 8.5 kB
  • After minification 8.5 kB
  • After compression 5.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. Torontosaints.com needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 40% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

24

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

Accessibility Review

torontosaints.com accessibility score

56

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

torontosaints.com best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

torontosaints.com SEO score

58

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

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torontosaints.com 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 Torontosaints.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 description is not detected on the main page of Toronto Saints. 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: