4.6 sec in total
205 ms
4 sec
381 ms
Click here to check amazing Pride Toronto content for Canada. Otherwise, check out these important facts you probably never knew about pridetoronto.com
Founded in 1981, Pride Toronto continues a legacy that is deeply intertwined with the rich, progressive history of Toronto’s queer community.
Visit pridetoronto.comWe analyzed Pridetoronto.com page load time and found that the first response time was 205 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pridetoronto.com performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value11.9 s
0/100
25%
Value6.0 s
46/100
10%
Value2,770 ms
3/100
30%
Value0.077
95/100
15%
Value15.3 s
7/100
10%
205 ms
800 ms
70 ms
270 ms
27 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 81% of them (58 requests) were addressed to the original Pridetoronto.com, 13% (9 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Pridetoronto.com.
Page size can be reduced by 765.9 kB (34%)
2.2 MB
1.5 MB
In fact, the total size of Pridetoronto.com main page is 2.2 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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 74.0 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 74.0 kB or 88% of the original size.
Potential reduce by 0 B
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. Pride Toronto images are well optimized though.
Potential reduce by 292.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 292.6 kB or 74% of the original size.
Potential reduce by 399.2 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. Pridetoronto.com needs all CSS files to be minified and compressed as it can save up to 399.2 kB or 89% of the original size.
Number of requests can be reduced by 18 (30%)
60
42
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pride 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 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
pridetoronto.com
205 ms
www.pridetoronto.com
800 ms
wp-emoji-release.min.js
70 ms
style.css
270 ms
css
27 ms
css
39 ms
css
50 ms
style.css
1071 ms
shortcodes.css
138 ms
magnific_popup.css
1070 ms
jquery.js
1348 ms
jquery-migrate.min.js
2077 ms
asyncjs.php
263 ms
frontend-builder-global-functions.js
329 ms
jquery.mobile.custom.min.js
330 ms
custom.js
398 ms
jquery.fitvids.js
397 ms
waypoints.min.js
465 ms
jquery.magnific-popup.js
465 ms
frontend-builder-scripts.js
599 ms
wp-embed.min.js
531 ms
analytics.js
22 ms
collect
62 ms
logo-flower-optimized.svg
195 ms
you_can_sit_with_us.png
398 ms
events_teambob2.jpg
332 ms
info_volunteer_group.jpg
401 ms
dyke_march_town_hall_april.jpg
333 ms
info_bathhouse_raids.jpg
435 ms
RW_Pride2016_8859_1.jpg
336 ms
city_toronto_logo_sm.jpg
399 ms
province_ontario_logo_sm.jpg
400 ms
heritage_canada_logo_sm.jpg
403 ms
ocaf_fmco_logo_sm.jpg
464 ms
td_logo_sm.jpg
465 ms
labatt_bud_light_logo_sm.jpg
466 ms
ontario_lottery_gaming_logo_sm.jpg
466 ms
molson_logo_sm.jpg
469 ms
palm_bay_logo_sm.jpg
502 ms
smart_logo_sm.jpg
531 ms
viagra_logo_sm.jpg
532 ms
stoli_logo_sm.jpg
533 ms
manulife_logo_sm.jpg
532 ms
air_canada_logo_sm.jpg
534 ms
eska_logo_sm.jpg
569 ms
loblaws_logo_sm.jpg
597 ms
trojan_logo_sm.jpg
598 ms
winners_logo_sm.jpg
598 ms
ctv_logo_sm.jpg
599 ms
cp24_logo_sm.jpg
600 ms
cieslok_media_logo_sm.jpg
635 ms
in_magazine_logo_sm.jpg
665 ms
out_tv_logo_sm.jpg
665 ms
proud_fm_logo_sm.jpg
666 ms
toronto_star_logo_sm.jpg
668 ms
fugues_logo_sm.jpg
670 ms
pride_toronto_you_can_sit_with_us_pride_month.svg
702 ms
toadOcfmlt9b38dHJxOBGAE-U1AYRUXXE0Dth8uKIE0.woff
157 ms
toadOcfmlt9b38dHJxOBGLhvvL6PHcOvkHgRlzWiaCU.woff
158 ms
toadOcfmlt9b38dHJxOBGAAD_zxmsR6vL1X3tnvCZYo.woff
159 ms
ODelI1aHBYDBqgeIAH2zlBBHWFfxJXS04xYOz0jw624.woff
159 ms
toadOcfmlt9b38dHJxOBGIPZSf8Ud0kNoe3bGnF7K24.woff
160 ms
toadOcfmlt9b38dHJxOBGLhZfOo4eSOlrve6pGrXHAo.woff
159 ms
ETmodules_v2_4.ttf
765 ms
l1cOQ90roY9yC7voEhngDD8E0i7KZn-EPnyo3HZu7kw.woff
159 ms
PyqsDANUgLi2UsdO-d4iZQ.woff
158 ms
dI-qzxlKVQA6TUC5RKSb3z8E0i7KZn-EPnyo3HZu7kw.woff
159 ms
asyncspc.php
607 ms
919c84b0979a1b4068066e2282473482.png
69 ms
lg.php
125 ms
575bff1e8f80448dd3ba6404fab4905f.png
69 ms
lg.php
114 ms
pridetoronto.com accessibility score
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
Links do not have a discernible name
pridetoronto.com 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
pridetoronto.com 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pridetoronto.com 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 Pridetoronto.com 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.
pridetoronto.com
Open Graph data is detected on the main page of Pride Toronto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: