1.4 sec in total
76 ms
1.2 sec
166 ms
Click here to check amazing Traffic Ottawa content for Canada. Otherwise, check out these important facts you probably never knew about traffic.ottawa.ca
Visit traffic.ottawa.caWe analyzed Traffic.ottawa.ca page load time and found that the first response time was 76 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
traffic.ottawa.ca performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value8.5 s
1/100
25%
Value5.2 s
59/100
10%
Value860 ms
33/100
30%
Value0.008
100/100
15%
Value7.8 s
45/100
10%
76 ms
114 ms
58 ms
26 ms
335 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 41% of them (28 requests) were addressed to the original Traffic.ottawa.ca, 36% (25 requests) were made to Maps.googleapis.com and 12% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (354 ms) belongs to the original domain Traffic.ottawa.ca.
Page size can be reduced by 907.9 kB (52%)
1.7 MB
832.5 kB
In fact, the total size of Traffic.ottawa.ca main page is 1.7 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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 36.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 36.8 kB or 85% of the original size.
Potential reduce by 15.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. Traffic Ottawa images are well optimized though.
Potential reduce by 804.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 804.8 kB or 73% of the original size.
Potential reduce by 50.6 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. Traffic.ottawa.ca needs all CSS files to be minified and compressed as it can save up to 50.6 kB or 84% of the original size.
Number of requests can be reduced by 28 (44%)
63
35
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Traffic Ottawa. 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 from 5 to 1 for CSS and as a result speed up the page load time.
map
76 ms
114 ms
js
58 ms
jquery.min.js
26 ms
prototype.js
335 ms
application.js
228 ms
google_custom_controls.js
115 ms
wards.js
354 ms
map_style.css
119 ms
jquery.js
290 ms
app.css
200 ms
ot_globals_css.css
273 ms
ot_main_css.css
245 ms
ot_img_background.jpg
265 ms
ot_img_ottawa_logo.png
80 ms
ot_img_so_logo_white.png
79 ms
camera_printImage.gif
83 ms
roadinfo_printImage.gif
81 ms
special_event_printImage.gif
81 ms
incident_printImage.gif
159 ms
vms_printImage.gif
160 ms
parking_printImage.gif
159 ms
p_and_r_printImage.gif
160 ms
ottawa_logo24.jpg
161 ms
red_light_camera_printImage.gif
237 ms
ottawanav.jpg
235 ms
Ride_Match_Transparent.png
243 ms
OC_Transpo_Bus_Transparent.png
244 ms
Twitter_Logo_Transparent.png
243 ms
ga.js
10 ms
__utm.gif
21 ms
common.js
19 ms
map.js
18 ms
home_transparent.png
80 ms
util.js
29 ms
onion.js
16 ms
openhand_8_8.cur
19 ms
ViewportInfoService.GetViewportInfo
87 ms
stats.js
11 ms
controls.js
30 ms
transparent.png
14 ms
css
33 ms
google4.png
23 ms
marker.js
17 ms
mapcnt6.png
37 ms
tmapctrl.png
32 ms
cb_scout5.png
36 ms
tmapctrl4.png
35 ms
imgs8.png
35 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
32 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
34 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
34 ms
vt
26 ms
vt
25 ms
vt
17 ms
vt
19 ms
vt
23 ms
vt
24 ms
vt
22 ms
vt
20 ms
vt
24 ms
vt
27 ms
vt
31 ms
vt
29 ms
vt
32 ms
vt
31 ms
vt
32 ms
vt
34 ms
traffic.ottawa.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
traffic.ottawa.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
traffic.ottawa.ca SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Traffic.ottawa.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 Traffic.ottawa.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.
traffic.ottawa.ca
Open Graph description is not detected on the main page of Traffic Ottawa. 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: