3.7 sec in total
88 ms
3.2 sec
396 ms
Visit waterloo.ca now to see the best up-to-date Waterloo content for Canada and also check out these interesting facts you probably never knew about waterloo.ca
The official website of the City of Waterloo, Ontario, Canada. Our services include recreation, parks, bylaw, roads, planning and development, arts and culture, and more.
Visit waterloo.caWe analyzed Waterloo.ca page load time and found that the first response time was 88 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
waterloo.ca performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value14.2 s
0/100
25%
Value9.1 s
13/100
10%
Value7,560 ms
0/100
30%
Value0
100/100
15%
Value17.9 s
3/100
10%
88 ms
720 ms
57 ms
98 ms
62 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 69% of them (84 requests) were addressed to the original Waterloo.ca, 8% (10 requests) were made to Static.xx.fbcdn.net and 7% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Btn.weather.ca.
Page size can be reduced by 687.9 kB (18%)
3.8 MB
3.1 MB
In fact, the total size of Waterloo.ca main page is 3.8 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. 65% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 37.6 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 37.6 kB or 75% of the original size.
Potential reduce by 183.7 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. Waterloo images are well optimized though.
Potential reduce by 382.6 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 382.6 kB or 72% of the original size.
Potential reduce by 84.0 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. Waterloo.ca needs all CSS files to be minified and compressed as it can save up to 84.0 kB or 84% of the original size.
Number of requests can be reduced by 44 (37%)
120
76
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waterloo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
waterloo.ca
88 ms
www.waterloo.ca
720 ms
base.css
57 ms
structure.css
98 ms
sitecontent.css
62 ms
icreate.css
57 ms
navigation.css
100 ms
jquery.autocomplete.css
95 ms
jquery-ui-1.9.1.custom.css
104 ms
Calendar.css
99 ms
jquery-1.8.2.min.js
158 ms
jquery-ui-1.9.1.custom.min.js
176 ms
jquery.cookies.js
122 ms
date.js
127 ms
dropdown.js
125 ms
general.js
127 ms
gaTracking.js
155 ms
quicklinks-dropdown.js
154 ms
jquery.autocomplete.min.js
154 ms
email.js
153 ms
jquery.mini-calendar.js
214 ms
jquery.gallery.js
237 ms
EmergencyBanner.css
204 ms
jquery.rotatingbanners.css
323 ms
bg-stretcher.js
229 ms
jquery.rotatingbanners.js
311 ms
youtubeV3.js
202 ms
grey.jpg
81 ms
Cover_Skyline.UofW_waterloo.ca_hero.jpg
637 ms
connect.png
36 ms
social_bg.png
33 ms
icon_facebook.gif
34 ms
icon_youtube.gif
36 ms
icon_twitter.gif
78 ms
logo.png
81 ms
spacer.gif
79 ms
living_rental-license_280px.jpg
216 ms
living_community-grants.jpg
199 ms
living_stormwater_280px.jpg
172 ms
large_Earth_Day-2015_280px.jpg
201 ms
getting_active_transportation_280px.jpg
175 ms
pa-day_activities.jpg
318 ms
register_for_programs.jpg
293 ms
large_living_poolsched_280px2.jpg
293 ms
photo_gallery.jpg
248 ms
travel.jpg
263 ms
uptown_waterloo.jpg
315 ms
large_visiting_280px.jpg
457 ms
bid_opportunities.jpg
382 ms
economic_development.jpg
456 ms
business_planning_development_280px.jpg
455 ms
large_business_280px.jpg
453 ms
government_council_meetings.jpg
603 ms
jobs_280px.jpg
457 ms
government_bylaw_280px.jpg
498 ms
large_government_CouncilForADay_280px.jpg
477 ms
atoz.png
470 ms
cal_right.jpg
458 ms
eventtab_festivals_0214.jpg
495 ms
eventtab_council_0215.jpg
510 ms
eventtab_museum-general_0215.jpg
519 ms
YouTubeAPI.ashx
510 ms
searchBox.png
511 ms
emailus.aspx
519 ms
homepageSignup.aspx
541 ms
eservices_home_closed.png
565 ms
template1.php
1963 ms
mainNav_home.png
515 ms
ga.js
38 ms
TwitterTimeline.ashx
498 ms
topFive.aspx
515 ms
GetEmergencyBanner.ashx
525 ms
broadcast.aspx
528 ms
inpage_linkid.js
10 ms
__utm.gif
26 ms
likebox.php
175 ms
GetCalendarsDateWithEvent.ashx
793 ms
home_popup_navTab01.png
443 ms
home_popup_navTab02.png
432 ms
home_popup_navTab03.png
437 ms
home_popup_navTab04.png
424 ms
home_popup_navTab05.png
396 ms
news_box.png
393 ms
xYm_UD1pmAz.css
39 ms
TGpOWuX6Pv8.css
48 ms
_rx8naC75Dy.js
63 ms
x5F9OMjKyLw.js
92 ms
ICDbTSzjQEg.js
89 ms
TTCre3391I0.js
90 ms
say.png
364 ms
footer_bg.jpg
366 ms
quicklink_advanced.png
345 ms
12728802_10154103325046842_2256308903247529603_n.jpg
74 ms
12418011_10154019026886842_3973092282868875481_n.jpg
35 ms
12249703_840464466072068_150358281510022980_n.jpg
35 ms
12250013_10153874696846802_5444176717606794469_n.jpg
38 ms
12734088_130648003989231_1282360323817300864_n.jpg
38 ms
1509249_10206871112710781_4334016272366896080_n.jpg
35 ms
12243077_138987239823695_4355241003270147577_n.jpg
38 ms
12742046_1696226680633658_4882803754428915994_n.jpg
42 ms
12801301_10156656809840571_4697405552245073845_n.jpg
41 ms
wL6VQj7Ab77.png
17 ms
s7jcwEQH7Sx.png
18 ms
I6-MnjEovm5.js
15 ms
vlXaquuXMrr.js
16 ms
mqdefault.jpg
57 ms
mqdefault.jpg
69 ms
mqdefault.jpg
80 ms
mqdefault.jpg
84 ms
mqdefault.jpg
85 ms
NoBot.js
120 ms
WebResource.axd
138 ms
WebResource.axd
113 ms
print.css
27 ms
weatherbuttons.js
33 ms
wbtn_240x60.css
59 ms
counter.gif
77 ms
referer.gif
32 ms
logo.gif
54 ms
btn_alert_23460.gif
58 ms
r.gif
64 ms
swirl.gif
37 ms
waterloo.ca accessibility score
waterloo.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
General
Impact
Issue
Detected JavaScript libraries
waterloo.ca SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waterloo.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 Waterloo.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.
waterloo.ca
Open Graph description is not detected on the main page of Waterloo. 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: