5.3 sec in total
305 ms
4.5 sec
457 ms
Click here to check amazing Calgary content for Canada. Otherwise, check out these important facts you probably never knew about calgary.ca
Visit calgary.caWe analyzed Calgary.ca page load time and found that the first response time was 305 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
calgary.ca performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value21.7 s
0/100
25%
Value9.4 s
12/100
10%
Value1,610 ms
12/100
30%
Value0
100/100
15%
Value19.5 s
2/100
10%
305 ms
735 ms
70 ms
54 ms
61 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 52% of them (32 requests) were addressed to the original Calgary.ca, 5% (3 requests) were made to Script.crazyegg.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Calgary.ca.
Page size can be reduced by 518.6 kB (18%)
2.8 MB
2.3 MB
In fact, the total size of Calgary.ca main page is 2.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. 75% 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 74.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 21.0 kB, which is 24% 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 74.8 kB or 86% of the original size.
Potential reduce by 171.9 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. Calgary images are well optimized though.
Potential reduce by 271.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 271.8 kB or 44% of the original size.
Number of requests can be reduced by 25 (46%)
54
29
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Calgary. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.calgary.ca
305 ms
home.html
735 ms
css
70 ms
jquery-3.6.0.min.js
54 ms
jquery-ui.min.js
61 ms
bootstrap.min.js
67 ms
main.min.css
408 ms
main.min.js
875 ms
csrf.min.js
308 ms
WTCalgarycaV3.load.js
262 ms
launch-EN300d6f3dd9f74d8f85792c2dae95d30e.min.js
59 ms
9840.js
104 ms
homepage.js
455 ms
homepage.css
534 ms
clientlibs.min.js
334 ms
clientlibs.min.js
466 ms
clientlibs.min.js
747 ms
api.js
102 ms
element.js
103 ms
token.json
320 ms
webtrends.min.js
50 ms
gtm.js
158 ms
animate.min.css
60 ms
id
49 ms
EX695b51bd7c574ec288222435eaa43e4b-libraryCode_source.min.js
25 ms
www.calgary.ca.json
21 ms
webtrends.fb.js
7 ms
webtrends.yt.js
12 ms
wtid.js
339 ms
6735f9594d6bb8a4f1fe56c6b3e21cf5.js
69 ms
coc-logo-simplify.svg
321 ms
coc-logo.svg
154 ms
dest5.html
83 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
139 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
227 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
228 ms
cicon.ttf
445 ms
cicon.ttf
818 ms
ibs:dpid=411&dpuuid=ZjfIswAAAENtjwOH
72 ms
js
90 ms
recaptcha__en.js
75 ms
1714498823451.jpg
1106 ms
1704213985565.jpg
857 ms
1684447118367.jpg
839 ms
1706114479161.jpg
951 ms
1705684896665.jpg
873 ms
1714677890931.jpg
1070 ms
1660842598379.jpg
1161 ms
dcs.gif
148 ms
delivery
76 ms
1714423370942.jpg
1141 ms
1705436984511.jpg
1348 ms
1714423389471.jpg
1175 ms
1714423362104.jpg
1233 ms
1714580563068.jpg
1282 ms
1714580460879.jpg
1056 ms
1714580327177.jpg
1441 ms
1714423422785.jpg
1092 ms
s01061978130601
25 ms
1714423380723.jpg
1386 ms
1714423431021.jpg
1004 ms
calgary.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 IDs are not unique
calgary.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
calgary.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 Calgary.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 Calgary.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.
calgary.ca
Open Graph description is not detected on the main page of Calgary. 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: