Tools & Wizards About Us
traffictoronto.ca screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

traffictoronto.ca

LIVE Toronto Traffic Cameras, TorontoTraffic.ca - Where do you want to go today?

Page Load Speed

2.4 sec in total

First Response

82 ms

Resources Loaded

1.9 sec

Page Rendered

337 ms

traffictoronto.ca screenshot

About Website

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

Toronto traffic cameras. Live Traffic Cameras located along Highway 401, the DVP, the Gardiner and the Allen Expressway.

Visit traffictoronto.ca

Key Findings

We analyzed Traffictoronto.ca page load time and found that the first response time was 82 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

traffictoronto.ca performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value2,070 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

traffictoronto.ca

82 ms

main.htm

73 ms

main.css

18 ms

adsbygoogle.js

137 ms

plusone.js

27 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Traffictoronto.ca, 18% (9 requests) were made to Pagead2.googlesyndication.com and 16% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (837 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 240.8 kB (13%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Traffictoronto.ca main page is 1.9 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 31.6 kB

  • Original 38.5 kB
  • After minification 37.8 kB
  • After compression 6.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. 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 31.6 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 45.8 kB

  • Original 1.1 MB
  • After minification 1.0 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. Traffic Toronto images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 163.0 kB

  • Original 782.1 kB
  • After minification 782.0 kB
  • After compression 619.1 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 163.0 kB or 21% of the original size.

CSS Optimization

-8%

Potential reduce by 371 B

  • Original 4.9 kB
  • After minification 4.9 kB
  • After compression 4.5 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. Traffictoronto.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (48%)

Requests Now

44

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

traffictoronto.ca

traffictoronto.ca

82 ms

main.htm

main.htm

73 ms

main.css

main.css

18 ms

adsbygoogle.js

adsbygoogle.js

137 ms

plusone.js

plusone.js

27 ms

loc9113.jpg

loc9113.jpg

194 ms

loc39--2

loc39--2

112 ms

ga.js

ga.js

57 ms

loc9201.jpg

loc9201.jpg

190 ms

loc9400.jpg

loc9400.jpg

191 ms

loc32--2

loc32--2

111 ms

loc24--2

loc24--2

110 ms

loc57--2

loc57--2

242 ms

loc70--2

loc70--2

112 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

84 ms

fastbutton

fastbutton

80 ms

__utm.gif

__utm.gif

80 ms

show_ads_impl.js

show_ads_impl.js

370 ms

collect

collect

36 ms

postmessageRelay

postmessageRelay

33 ms

developers.google.com

developers.google.com

560 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

21 ms

rpc:shindig_random.js

rpc:shindig_random.js

5 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

zrt_lookup.html

zrt_lookup.html

30 ms

ads

ads

744 ms

ads

ads

470 ms

ads

ads

837 ms

ads

ads

470 ms

ads

ads

751 ms

10789507575672306004

10789507575672306004

23 ms

abg_lite.js

abg_lite.js

26 ms

s

s

4 ms

window_focus.js

window_focus.js

24 ms

qs_click_protection.js

qs_click_protection.js

32 ms

ufs_web_display.js

ufs_web_display.js

14 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

198 ms

icon.png

icon.png

8 ms

6327388269656625272

6327388269656625272

246 ms

activeview

activeview

246 ms

810186006763681720

810186006763681720

118 ms

activeview

activeview

160 ms

7227108142789745098

7227108142789745098

53 ms

activeview

activeview

65 ms

reactive_library.js

reactive_library.js

217 ms

ca-pub-0395189298049993

ca-pub-0395189298049993

122 ms

0vQLayOeqdxXV3Fq9j4WhHVRESBnruWTliEoYkmwt9E.js

0vQLayOeqdxXV3Fq9j4WhHVRESBnruWTliEoYkmwt9E.js

33 ms

activeview

activeview

88 ms

Accessibility Review

traffictoronto.ca accessibility score

96

Accessibility Issues

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

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

High

Page has valid source maps

SEO Factors

traffictoronto.ca SEO score

92

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

traffictoronto.ca

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