9.1 sec in total
291 ms
8 sec
826 ms
Click here to check amazing Foodora content for Germany. Otherwise, check out these important facts you probably never knew about foodora.de
Einfach Essen bestellen mit Lieferando.de! Heute Lust auf Pizza, Sushi oder Vegetarisch? Genieße deine Lieblingsgerichte schnell geliefert oder als Takeaway.
Visit foodora.deWe analyzed Foodora.de page load time and found that the first response time was 291 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
foodora.de performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value9.3 s
1/100
25%
Value6.2 s
43/100
10%
Value690 ms
43/100
30%
Value0.123
83/100
15%
Value11.2 s
20/100
10%
291 ms
881 ms
11 ms
42 ms
91 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 14% of them (15 requests) were addressed to the original Foodora.de, 17% (18 requests) were made to Volo-images.s3.amazonaws.com and 8% (9 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Volo-images.s3.amazonaws.com.
Page size can be reduced by 1.1 MB (44%)
2.6 MB
1.5 MB
In fact, the total size of Foodora.de main page is 2.6 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. 50% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 74.5 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.5 kB or 77% of the original size.
Potential reduce by 47.0 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. Foodora images are well optimized though.
Potential reduce by 849.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 849.2 kB or 64% of the original size.
Potential reduce by 165.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.de needs all CSS files to be minified and compressed as it can save up to 165.6 kB or 85% of the original size.
Number of requests can be reduced by 53 (62%)
85
32
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foodora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
foodora.de
291 ms
www.foodora.de
881 ms
style-de.css
11 ms
tracker.js
42 ms
js
91 ms
all-libs.js
31 ms
head.js
32 ms
sdk.js
306 ms
routing
186 ms
apple-store-white.png
81 ms
google-play-white.png
6 ms
gtm.js
203 ms
hompage-restaurant-01.jpg
508 ms
intl.js
28 ms
hompage-restaurant-02.jpg
496 ms
hompage-restaurant-03.jpg
602 ms
hompage-restaurant-04.jpg
496 ms
hompage-restaurant-05.jpg
511 ms
hompage-restaurant-06.jpg
487 ms
city-7.jpg
917 ms
city-7-hover.jpg
795 ms
city-9.jpg
981 ms
city-9-hover.jpg
805 ms
city-10.jpg
916 ms
city-10-hover.jpg
914 ms
city-8.jpg
1123 ms
city-8-hover.jpg
1092 ms
city-12.jpg
1143 ms
city-12-hover.jpg
1112 ms
city-11.jpg
1117 ms
city-11-hover.jpg
1205 ms
teaser_4000.jpg
955 ms
2ED58B_1_0.woff
36 ms
2ED58B_0_0.woff
25 ms
icomoon.ttf
20 ms
de-DE.json
140 ms
fbds.js
90 ms
oct.js
339 ms
264 ms
common.js
49 ms
util.js
135 ms
controls.js
108 ms
places_impl.js
171 ms
map.js
164 ms
conversion_async.js
212 ms
analytics.js
216 ms
roundtrip.js
155 ms
tsc
517 ms
i3856898contC.js
525 ms
a.js;m=11142200782641;cache=0.6784878957550973
149 ms
srt
555 ms
xd_arbiter.php
328 ms
190 ms
232 ms
powered-by-google-on-white3.png
135 ms
autocomplete-icons.png
176 ms
onion.js
67 ms
59 ms
collect
27 ms
collect
85 ms
stats.js
14 ms
C3BZUZMEPVFO3BM7MHMXJ2.js
157 ms
adsct
85 ms
adsct
102 ms
56 ms
ga-audiences
27 ms
out
8 ms
tr
33 ms
33 ms
out
47 ms
out
49 ms
out
48 ms
out
46 ms
out
48 ms
u.php
91 ms
sync
78 ms
35 ms
adsct
56 ms
pixel
102 ms
favicon-16x16.png
52 ms
api
384 ms
sd
10 ms
377928.gif
9 ms
in
11 ms
widget_v2.132.js
17 ms
__$$__stringtable_lang_de.js
21 ms
api
267 ms
container
268 ms
yieldlabRedirect
656 ms
pixel
13 ms
improveDigitalRedirect
656 ms
rubiconRedirect
670 ms
adxSyncDone
661 ms
avatar_simple_visitor.png
144 ms
aL63HcygAAVYuCCsAAA==
2 ms
adscaleSyncDone
253 ms
match
7 ms
tap.php
12 ms
AuthenticationService.Authenticate
27 ms
retarget
304 ms
conversion.js
13 ms
beacon_call.js
75 ms
19 ms
18 ms
beacon
25 ms
nr-885.min.js
56 ms
25 ms
foodora.de 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
Links do not have a discernible name
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.
foodora.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
foodora.de 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foodora.de can be misinterpreted by Google and other search engines. Our service has detected that German 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.de 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.de
Open Graph description is not detected on the main page of Foodora. 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: