4.5 sec in total
780 ms
3.3 sec
422 ms
Visit foodora.ca now to see the best up-to-date Food Ora content for Canada and also check out these interesting facts you probably never knew about foodora.ca
foodora - Food, groceries and more - All you need, minutes away from your door
Visit foodora.caWe analyzed Foodora.ca page load time and found that the first response time was 780 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
foodora.ca performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value3.4 s
66/100
25%
Value2.6 s
97/100
10%
Value90 ms
99/100
30%
Value0.042
99/100
15%
Value3.4 s
93/100
10%
780 ms
36 ms
70 ms
120 ms
54 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 18% of them (13 requests) were addressed to the original Foodora.ca, 14% (10 requests) were made to Volo-images.s3.amazonaws.com and 11% (8 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Volo-images.s3.amazonaws.com.
Page size can be reduced by 1.1 MB (28%)
4.0 MB
2.9 MB
In fact, the total size of Foodora.ca main page is 4.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. 45% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 60.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. 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 60.8 kB or 76% of the original size.
Potential reduce by 65.5 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. Food Ora images are well optimized though.
Potential reduce by 847.3 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 847.3 kB or 64% of the original size.
Potential reduce by 167.6 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. Foodora.ca needs all CSS files to be minified and compressed as it can save up to 167.6 kB or 85% of the original size.
Number of requests can be reduced by 40 (66%)
61
21
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Food Ora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
www.foodora.ca
780 ms
style-ca.css
36 ms
tracker.js
70 ms
js
120 ms
all-libs.js
54 ms
head.js
52 ms
sdk.js
312 ms
routing
497 ms
apple-store-white.png
6 ms
google-play-white.png
15 ms
gtm.js
112 ms
teaser_4000.jpg
55 ms
hompage-restaurant-01.jpg
445 ms
intl.js
21 ms
hompage-restaurant-02.jpg
427 ms
hompage-restaurant-03.jpg
517 ms
hompage-restaurant-04.jpg
606 ms
hompage-restaurant-05.jpg
436 ms
hompage-restaurant-06.jpg
438 ms
city-2.jpg
1358 ms
city-2-hover.jpg
1562 ms
city-3.jpg
1298 ms
city-3-hover.jpg
1623 ms
2ED58B_1_0.woff
21 ms
2ED58B_0_0.woff
20 ms
icomoon.ttf
20 ms
en-CA.json
422 ms
fbds.js
58 ms
18 ms
19 ms
149 ms
common.js
40 ms
util.js
98 ms
controls.js
98 ms
places_impl.js
57 ms
map.js
48 ms
conversion_async.js
148 ms
analytics.js
131 ms
roundtrip.js
222 ms
tsc
505 ms
i4261624contC.js
592 ms
oct.js
105 ms
a.js;m=11142200782641;cache=0.016778544755652547
140 ms
tfa.js
170 ms
xd_arbiter.php
340 ms
usage.gif
204 ms
onion.js
51 ms
powered-by-google-on-white3.png
71 ms
autocomplete-icons.png
83 ms
stats.js
41 ms
collect
18 ms
collect
96 ms
45 ms
88 ms
ga-audiences
53 ms
MEPVEPVJOZD2ZH3NFPVH3L.js
174 ms
adsct
140 ms
adsct
105 ms
out
12 ms
46 ms
out
8 ms
out
47 ms
out
47 ms
sync
72 ms
33 ms
pixel
76 ms
adsct
42 ms
tap.php
23 ms
377928.gif
6 ms
sd
6 ms
in
5 ms
nr-885.min.js
47 ms
4 ms
foodora.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
foodora.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
foodora.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foodora.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Foodora.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.
foodora.ca
Open Graph description is not detected on the main page of Food Ora. 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: