4 sec in total
1.2 sec
2.4 sec
331 ms
Visit where.ca now to see the best up-to-date Where content for Canada and also check out these interesting facts you probably never knew about where.ca
Canada's Travel Planner
Visit where.caWe analyzed Where.ca page load time and found that the first response time was 1.2 sec and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
where.ca performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value4.9 s
28/100
25%
Value3.7 s
85/100
10%
Value250 ms
84/100
30%
Value0.009
100/100
15%
Value5.6 s
69/100
10%
1214 ms
30 ms
40 ms
25 ms
62 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 26% of them (38 requests) were addressed to the original Where.ca, 43% (63 requests) were made to Cdn.where.ca and 8% (12 requests) were made to Farm2.staticflickr.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Where.ca.
Page size can be reduced by 795.9 kB (26%)
3.0 MB
2.2 MB
In fact, the total size of Where.ca main page is 3.0 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 66.1 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 66.1 kB or 76% of the original size.
Potential reduce by 101.6 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. Where images are well optimized though.
Potential reduce by 441.2 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 441.2 kB or 70% of the original size.
Potential reduce by 187.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. Where.ca needs all CSS files to be minified and compressed as it can save up to 187.0 kB or 73% of the original size.
Number of requests can be reduced by 59 (41%)
145
86
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Where. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.where.ca
1214 ms
bY7BDoMwDEN_iNKCtMO-ZqpKBBFpU9UFtL9fgcM0aac4z1ac0bln0Bg12WOhQq_RDa5z91KL30m-xtg97OSxcNCEPnLqBntsaaIyF23TeoAqbAB-eIsF3xRIDIQbt1g5wVafZr30eSmbsKFqpGIK7UwH_rGWzJo38cVkRWtDfQu1ZD4dlsvwMxnhtN6_gGMW6i_wAQ.css
30 ms
M9QvzsrVTUkr0M1NzEtMTy3STy4uhosllxaX5OcCAA.css
40 ms
nY7ZCsJQDER_qJfY3xB9EnyvbWxTcheT3Kp_bxcUNxB8S-bMDFOC9t5ZbKIjQ69Qqz6kooQBQxPFMalRaBVSl4DpoLBbb2E_w82dTdE3_x8N_SmjXF2mMTsNaSvmUZjZkfGiTA3KF_j0OzXJtWXBHz7r0GOxgnOHgibVgPzi__SWkCT6aBSDW6YspfN5Aw.css
25 ms
css
62 ms
font-awesome.min.css
46 ms
jquery.js
79 ms
jquery-migrate.min.js
78 ms
core.min.js
77 ms
widget.min.js
102 ms
position.min.js
55 ms
menu.min.js
100 ms
autocomplete.min.js
105 ms
widget.min.js
44 ms
jquery.jcarousel.min.js
40 ms
jquery.jj_ngg_shuffle.js
42 ms
wp-customer-reviews.js
97 ms
sjm_dfp_autopos.js
38 ms
js
143 ms
promoslider.js
71 ms
buttons.js
36 ms
barker_theme.js
44 ms
sjm_dfp_gallery_connector.js
66 ms
sjm-gaq-trackers.js
66 ms
sjm_gaq_gallery_connector.js
43 ms
sjm-todo.js
102 ms
jquery.mousewheel.min.js
101 ms
jquery.flexslider-min.js
102 ms
jquery.sjm-gallery.min.js
99 ms
sjm-gallery-theme.js
98 ms
start-journey.js
96 ms
header-rotate.js
100 ms
count.js
101 ms
wp-emoji-release.min.js
53 ms
gpt.js
180 ms
analytics.js
181 ms
header-home.png
180 ms
nav-dropdown-arrow.png
177 ms
24722139234_4050600435_s.jpg
342 ms
widgets.js
267 ms
count.js
161 ms
getAllAppDefault.esi
97 ms
24985110239_2d46e1db57_s.jpg
217 ms
24718861164_0589133cb0_s.jpg
215 ms
24966848519_9646b05b40_s.jpg
258 ms
25299624175_f05138496f_s.jpg
369 ms
25268655325_12da2520c5_s.jpg
257 ms
24640829773_bc1d39e6aa_s.jpg
257 ms
24899845039_dc7395b9c9_s.jpg
258 ms
24638242303_0f7e639b65_s.jpg
256 ms
25171745151_487e0271ed_s.jpg
268 ms
24879866659_4aec89dc83_s.jpg
272 ms
24619289393_dd3a9b75c2_s.jpg
267 ms
smi-blue.png
35 ms
gplus-blue.png
36 ms
gobg.png
36 ms
bocflag.png
35 ms
Arrow.png
35 ms
syj_bg.png
37 ms
slide.png
48 ms
prev-horizontal.png
49 ms
next-horizontal.png
48 ms
orange-pin.png
48 ms
next-old.png
48 ms
circle-dot.png
49 ms
circle.png
58 ms
prev-old.png
59 ms
pic1.png
28 ms
pic2.png
29 ms
pic3.png
29 ms
pic4.png
28 ms
pic5.png
28 ms
pic6.png
29 ms
pic7.png
37 ms
pic8.png
36 ms
pic9.png
36 ms
pic10.png
40 ms
pic11.png
40 ms
pic12.png
36 ms
BSM-Arctic-ADS-wheredigital-module-550x367.gif
56 ms
patios_pillar.jpg
200 ms
Whistler-Travel-Guide.jpg
154 ms
Winnipeg-Manitoba.jpg
57 ms
Canadian-Rockies-Travel.jpg
141 ms
Victoria-BC.jpg
141 ms
Edmonton-Travel-Guide.jpg
183 ms
Halifax-Travel-Guide.jpg
151 ms
Ottawa-Travel-Guide.jpg
220 ms
Vancouver-Travel-Guide.jpg
184 ms
BSM-Arctic-ADS-wheredigital-module-550x367-88x88.gif
182 ms
patios_pillar-88x88.jpg
183 ms
Whistler-Travel-Guide-88x88.jpg
196 ms
Winnipeg-Manitoba-88x88.jpg
199 ms
Canadian-Rockies-Travel-88x88.jpg
197 ms
Victoria-BC-88x88.jpg
198 ms
Edmonton-Travel-Guide-88x88.jpg
269 ms
Halifax-Travel-Guide-88x88.jpg
249 ms
Ottawa-Travel-Guide-88x88.jpg
210 ms
Vancouver-Travel-Guide-88x88.jpg
210 ms
Battistas-Calzone-Co.-IMG_3447-88x88.jpg
248 ms
Glissade_2013_small-88x88.jpg
217 ms
The-Marriage-of-Figaro-by-Monika-Rittershaus-88x88.jpg
216 ms
MViwy4K6e56oHcyeMzjbCQ.ttf
87 ms
gift-guide-1.jpg
213 ms
pubads_impl_81.js
41 ms
linkid.js
28 ms
like.php
153 ms
Lussier.jpg
450 ms
HM_Ottawa_Event_11.jpg
223 ms
The-Great-Canadian-Bucket-List-50-Things-to-Do-Before-You-Die.jpg
226 ms
243-front-web-aerial.jpg
244 ms
06-FundyNationalPark.jpg
230 ms
Unusual-Getaways-from-Toronto-Sundance-Balloons.jpg
229 ms
Alberta-highway.jpg
239 ms
fronthouse_cloisters.jpg
241 ms
calgary.jpg
225 ms
Canadian-Rockies.jpg
234 ms
Edmonton.jpg
240 ms
Halifax.jpg
239 ms
collect
200 ms
collect
200 ms
Muskoka.jpg
219 ms
container.html
96 ms
Ottawa.jpg
193 ms
activity.php
120 ms
ads
153 ms
getSegment.php
158 ms
checkOAuth.esi
58 ms
Toronto.jpg
143 ms
Vancouver.jpg
145 ms
Victoria.jpg
132 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
164 ms
Whistler.jpg
113 ms
vpc6VNjRPXV.js
117 ms
LVx-xkvaJ0b.png
115 ms
Winnipeg.jpg
105 ms
t.dhj
7 ms
t.dhj
12 ms
cm
52 ms
s-3271.xgi
24 ms
syndication
108 ms
350275414779912192
208 ms
hbpix
138 ms
6 ms
pixel
22 ms
6 ms
xrefid.xgi
6 ms
2981
31 ms
where.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
where.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
Page has valid source maps
where.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Where.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 Where.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.
where.ca
Open Graph data is detected on the main page of Where. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: