Tools & Wizards About Us
dfsintorontowest.ca screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

dfsintorontowest.ca

Toronto West | Desjardins Financial Security Independent Network

Page Load Speed

2.6 sec in total

First Response

76 ms

Resources Loaded

1.9 sec

Page Rendered

647 ms

dfsintorontowest.ca screenshot

About Website

Welcome to dfsintorontowest.ca homepage info - get ready to check Dfsin Toronto West best content right away, or after learning these important things about dfsintorontowest.ca

Visit dfsintorontowest.ca

Key Findings

We analyzed Dfsintorontowest.ca page load time and found that the first response time was 76 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

dfsintorontowest.ca performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.9 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

dfsintorontowest.ca

76 ms

dfsintorontowest.ca

72 ms

toronto-west

421 ms

scriptCookie.js

67 ms

lodash.js

15 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Dfsintorontowest.ca, 90% (53 requests) were made to Dfsin.ca and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (575 ms) relates to the external source Dfsin.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (41%)

Content Size

4.0 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dfsintorontowest.ca main page is 4.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. 80% 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. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 76.5 kB

  • Original 94.3 kB
  • After minification 83.1 kB
  • After compression 17.8 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 11.3 kB, which is 12% 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 76.5 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 35.6 kB

  • Original 1.8 MB
  • After minification 1.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. Dfsin Toronto West images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.5 MB

  • Original 2.0 MB
  • After minification 1.6 MB
  • After compression 529.9 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 1.5 MB or 74% of the original size.

CSS Optimization

-31%

Potential reduce by 518 B

  • Original 1.7 kB
  • After minification 1.6 kB
  • After compression 1.2 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. Dfsintorontowest.ca needs all CSS files to be minified and compressed as it can save up to 518 B or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (74%)

Requests Now

53

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dfsintorontowest.ca

dfsintorontowest.ca

76 ms

dfsintorontowest.ca

dfsintorontowest.ca

72 ms

toronto-west

toronto-west

421 ms

scriptCookie.js

scriptCookie.js

67 ms

lodash.js

lodash.js

15 ms

util.js

util.js

21 ms

clay.css

clay.css

110 ms

main.css

main.css

161 ms

combo

combo

139 ms

js_loader_modules

js_loader_modules

283 ms

js_loader_config

js_loader_config

102 ms

combo

combo

394 ms

combo

combo

375 ms

combo

combo

377 ms

combo

combo

251 ms

config.js

config.js

173 ms

loader.3.js

loader.3.js

243 ms

js_bundle_config

js_bundle_config

372 ms

main.css

main.css

375 ms

rwc.css

rwc.css

370 ms

remote-web-component-admin-web.js

remote-web-component-admin-web.js

370 ms

combo

combo

506 ms

combo

combo

512 ms

n3.css

n3.css

505 ms

main.css

main.css

377 ms

sfl.css

sfl.css

384 ms

aos.css

aos.css

384 ms

styles.css

styles.css

504 ms

banner.css

banner.css

509 ms

aos.js

aos.js

504 ms

n3.js

n3.js

508 ms

menuburger.js

menuburger.js

507 ms

sfl.js

sfl.js

507 ms

cybermetrie.js

cybermetrie.js

508 ms

scripts.js

scripts.js

506 ms

combo

combo

575 ms

logo_assurance_dfsin_en.svg

logo_assurance_dfsin_en.svg

52 ms

logo_placement_dfsin_en.svg

logo_placement_dfsin_en.svg

109 ms

b0ff627e-9eb8-4847-6064-c05119665326

b0ff627e-9eb8-4847-6064-c05119665326

246 ms

961ae58a-2359-2004-662a-b46a81a6d7c1

961ae58a-2359-2004-662a-b46a81a6d7c1

248 ms

32f841b9-32e1-a289-1658-b77686dbff12

32f841b9-32e1-a289-1658-b77686dbff12

253 ms

6a5e9b37-fef4-04a6-a86a-8d7328bb5ce7

6a5e9b37-fef4-04a6-a86a-8d7328bb5ce7

246 ms

37df88d6-ebd6-bb1d-f154-dfeafeca9ea4

37df88d6-ebd6-bb1d-f154-dfeafeca9ea4

131 ms

62d9c62b-cd8e-6368-640b-779127ecbb1e

62d9c62b-cd8e-6368-640b-779127ecbb1e

247 ms

9acac933-1306-5aab-71f4-ddfed0e6fd61

9acac933-1306-5aab-71f4-ddfed0e6fd61

278 ms

80fa63e1-0e4a-f656-dded-f35aa35c4188

80fa63e1-0e4a-f656-dded-f35aa35c4188

278 ms

regulatedbyOCRI_logo_en_White_web_72.png

regulatedbyOCRI_logo_en_White_web_72.png

246 ms

c2c4b132-1597-4e3a-09dd-d35241d3d1a6

c2c4b132-1597-4e3a-09dd-d35241d3d1a6

299 ms

roboto-v18-latin-regular.woff

roboto-v18-latin-regular.woff

197 ms

roboto-v18-latin-500.woff

roboto-v18-latin-500.woff

224 ms

roboto-v18-latin-700.woff

roboto-v18-latin-700.woff

291 ms

173 ms

310 ms

289 ms

287 ms

gtm.js

gtm.js

97 ms

analytics.js

analytics.js

39 ms

gtm.js

gtm.js

255 ms

174 ms

Accessibility Review

dfsintorontowest.ca accessibility score

98

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.

Best Practices

dfsintorontowest.ca 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

dfsintorontowest.ca SEO score

77

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

High

robots.txt is not valid

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 Dfsintorontowest.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 Dfsintorontowest.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

dfsintorontowest.ca

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