8.7 sec in total
241 ms
4.9 sec
3.5 sec
Visit urbantoronto.ca now to see the best up-to-date Urban Toronto content for Canada and also check out these interesting facts you probably never knew about urbantoronto.ca
UrbanToronto is a website focusing on the skyscrapers, architecture, design, construction and development of urban centres in Toronto.
Visit urbantoronto.caWe analyzed Urbantoronto.ca page load time and found that the first response time was 241 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
urbantoronto.ca performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value14.8 s
0/100
25%
Value6.6 s
37/100
10%
Value340 ms
74/100
30%
Value0.108
88/100
15%
Value10.6 s
23/100
10%
241 ms
10 ms
247 ms
150 ms
432 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 39% of them (50 requests) were addressed to the original Urbantoronto.ca, 16% (21 requests) were made to Facebook.com and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Urbantoronto.ca.
Page size can be reduced by 498.5 kB (33%)
1.5 MB
1.0 MB
In fact, the total size of Urbantoronto.ca main page is 1.5 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 903.5 kB which makes up the majority of the site volume.
Potential reduce by 143.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 143.6 kB or 84% of the original size.
Potential reduce by 60.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. Urban Toronto images are well optimized though.
Potential reduce by 246.0 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 246.0 kB or 66% of the original size.
Potential reduce by 48.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. Urbantoronto.ca needs all CSS files to be minified and compressed as it can save up to 48.0 kB or 80% of the original size.
Number of requests can be reduced by 47 (38%)
125
78
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Urban 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 28 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
urbantoronto.ca
241 ms
widgets.js
10 ms
css_91a64bfd72f57190aefa2545150f2c13.css
247 ms
spcjs.php
150 ms
js_60f41203aceb56083f456a3e694b6223.js
432 ms
show_ads.js
5 ms
spc.php
119 ms
fl.js
128 ms
analytics.js
59 ms
icon-skyline.png
138 ms
logo.gif
139 ms
separator-15.gif
137 ms
facebook.png
211 ms
twitter.png
249 ms
instagram.png
239 ms
19715-66829.jpeg
347 ms
19677-66662.jpg
288 ms
19736-66859.png
569 ms
urbantoronto-148-3072.jpg
288 ms
16807-58985.jpeg
349 ms
19736-66859.png
568 ms
icon-addtoany.png
419 ms
19748-66899.jpg
433 ms
19741-66906.jpg
513 ms
19732-66839.png
760 ms
19726-66818.jpeg
568 ms
19731-66838.png
761 ms
19697-66692.jpg
735 ms
19725-66816.jpg
746 ms
19715-66829.jpeg
747 ms
19573-66845.jpg
759 ms
19677-66662.jpg
822 ms
19723-66811.jpg
831 ms
19686-66664.jpg
832 ms
19714-66802.jpg
831 ms
19693-66741.jpeg
832 ms
19708-66786.png
1088 ms
19690-66682.jpg
904 ms
19688-66678.jpeg
905 ms
map.png
1120 ms
ca-pub-2659021865271040.js
183 ms
zrt_lookup.html
214 ms
show_ads_impl.js
98 ms
lg.php
937 ms
border-teaser.gif
935 ms
page.js
171 ms
collect
103 ms
separator-10.gif
961 ms
ajs.php
965 ms
ads
198 ms
osd.js
41 ms
share_button.php
136 ms
share_button.php
139 ms
share_button.php
153 ms
share_button.php
142 ms
share_button.php
141 ms
share_button.php
144 ms
share_button.php
167 ms
share_button.php
168 ms
share_button.php
201 ms
share_button.php
210 ms
share_button.php
203 ms
share_button.php
213 ms
zH0IPw-UmpL.js
154 ms
LVx-xkvaJ0b.png
203 ms
share_button.php
229 ms
share_button.php
205 ms
share_button.php
198 ms
share_button.php
200 ms
share_button.php
225 ms
share_button.php
344 ms
4734363428780129852
42 ms
abg.js
45 ms
m_js_controller.js
65 ms
googlelogo_color_112x36dp.png
35 ms
share_button.php
308 ms
share_button.php
303 ms
s
11 ms
x_button_blue2.png
33 ms
-Wxc5n6ag8mSVPmrosQZJ6hEHpQooK3Qr1Gxv0lUkvE.js
63 ms
ads
180 ms
lg.php
98 ms
js
191 ms
css_c2164eaf8a14665705f50a584f47d3d2.css
237 ms
lg.php
470 ms
ai.php
464 ms
lg.php
457 ms
f3f6d992d0f228fb02bf59b6b4aa4782.jpg
454 ms
pixel
440 ms
lg.php
626 ms
ck-confirm
670 ms
lg.php
607 ms
ai.php
649 ms
lg.php
648 ms
ads
543 ms
sm13.html
538 ms
count.js
505 ms
button.b059c0eb61ea902a882e5c5b3c66a17a.js
530 ms
likebox.php
266 ms
activeview
254 ms
favicon
928 ms
nessie_icon_tiamat_white.png
100 ms
Upava29zfl-.css
127 ms
Az8D8BdSeJX.css
321 ms
mm0vjjrXdxr.js
880 ms
Ta5YnQdNSFy.js
959 ms
XXn49zk5GnD.js
837 ms
OwNnuMlrnxQ.js
838 ms
ga.js
317 ms
count-data.js
285 ms
count-data.js
274 ms
tweet_button.baa54ded21a982344c4ced326592f3de.en.html
482 ms
12003970_10153638933959814_8732140745663155665_n.png
719 ms
228429_10150188945104814_3671868_n.jpg
692 ms
12219507_716289331840032_5998277017195587148_n.jpg
692 ms
12345431_624767724332077_1690328785373983668_n.jpg
692 ms
578029_10151366985152244_128014760_n.jpg
692 ms
1930782_10208345138926526_6643154491959892489_n.jpg
692 ms
1937062_10207730288325494_3282665380935902357_n.jpg
690 ms
11224629_826267730817259_7042180808301162814_n.jpg
700 ms
11903773_1627618387508390_2320857879339144930_n.jpg
692 ms
wL6VQj7Ab77.png
670 ms
s7jcwEQH7Sx.png
668 ms
activeview
120 ms
wBg80dBy2Ra.js
66 ms
WIQcBxwlOXr.js
74 ms
ui
67 ms
jot.html
3 ms
urbantoronto.ca accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
urbantoronto.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
urbantoronto.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Urbantoronto.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 Urbantoronto.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.
urbantoronto.ca
Open Graph description is not detected on the main page of Urban 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: