4 sec in total
546 ms
3.2 sec
244 ms
Visit world.openfoodfacts.org now to see the best up-to-date World Openfoodfacts content for Germany and also check out these interesting facts you probably never knew about world.openfoodfacts.org
A collaborative, free and open database of ingredients, nutrition facts and information on food products from around the world
Visit world.openfoodfacts.orgWe analyzed World.openfoodfacts.org page load time and found that the first response time was 546 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
world.openfoodfacts.org performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value3.3 s
69/100
25%
Value7.8 s
24/100
10%
Value3,070 ms
2/100
30%
Value0.01
100/100
15%
Value9.3 s
31/100
10%
546 ms
557 ms
326 ms
250 ms
484 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original World.openfoodfacts.org, 79% (87 requests) were made to Static.openfoodfacts.org and 5% (5 requests) were made to Slack.openfoodfacts.org. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.openfoodfacts.org.
Page size can be reduced by 813.6 kB (57%)
1.4 MB
607.6 kB
In fact, the total size of World.openfoodfacts.org main page is 1.4 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. 55% of websites need less resources to load. Javascripts take 675.6 kB which makes up the majority of the site volume.
Potential reduce by 43.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 43.0 kB or 76% of the original size.
Potential reduce by 67.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. Obviously, World Openfoodfacts needs image optimization as it can save up to 67.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 503.5 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 503.5 kB or 75% of the original size.
Potential reduce by 199.5 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. World.openfoodfacts.org needs all CSS files to be minified and compressed as it can save up to 199.5 kB or 86% of the original size.
Number of requests can be reduced by 21 (20%)
104
83
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of World Openfoodfacts. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
world.openfoodfacts.org
546 ms
app.css
557 ms
foundation-icons.css
326 ms
modernizr.js
250 ms
jquery.js
484 ms
jquery-ui.min.js
1062 ms
jquery-ui.css
1030 ms
select2.min.css
21 ms
slackin.js
264 ms
foundation.min.js
490 ms
jquery.cookie.js
249 ms
select2.min.js
10 ms
jquery.iframe-transport.js
326 ms
jquery.fileupload.js
483 ms
load-image.min.js
451 ms
canvas-to-blob.min.js
481 ms
jquery.fileupload-ip.js
485 ms
ga.js
28 ms
openfoodfacts-logo-en-178x150.png
94 ms
front.8.100.jpg
120 ms
front.9.100.jpg
120 ms
front.4.100.jpg
120 ms
front.20.100.jpg
118 ms
front.6.100.jpg
119 ms
front.5.100.jpg
167 ms
front.6.100.jpg
188 ms
front.5.100.jpg
189 ms
front.7.100.jpg
191 ms
front.18.100.jpg
187 ms
front.7.100.jpg
189 ms
front.7.100.jpg
226 ms
front.9.100.jpg
248 ms
front.10.100.jpg
245 ms
front.5.100.jpg
251 ms
front.5.100.jpg
261 ms
front.5.100.jpg
261 ms
front.7.100.jpg
303 ms
front.9.100.jpg
322 ms
front.7.100.jpg
324 ms
Available_on_the_App_Store_Badge_EN_135x40.png
327 ms
android-app-on-google-play-en_app_rgb_wo_135x47.png
339 ms
154x40_WP_Store_blk.png
336 ms
android-apk.112x40.png
381 ms
foundation-icons.woff
430 ms
__utm.gif
54 ms
iframe
176 ms
all.js
49 ms
plusone.js
100 ms
widgets.js
206 ms
front.8.100.jpg
294 ms
front.9.100.jpg
295 ms
front.4.100.jpg
306 ms
front.20.100.jpg
310 ms
front.6.100.jpg
350 ms
front.5.100.jpg
380 ms
front.6.100.jpg
381 ms
front.5.100.jpg
397 ms
front.7.100.jpg
397 ms
front.18.100.jpg
428 ms
front.7.100.jpg
444 ms
collect
98 ms
front.7.100.jpg
441 ms
front.9.100.jpg
526 ms
front.10.100.jpg
458 ms
front.5.100.jpg
463 ms
front.5.100.jpg
456 ms
front.5.100.jpg
471 ms
82 ms
cb=gapi.loaded_0
9 ms
front.7.100.jpg
450 ms
front.9.100.jpg
467 ms
front.7.100.jpg
470 ms
Available_on_the_App_Store_Badge_EN_135x40.png
511 ms
xd_arbiter.php
213 ms
xd_arbiter.php
424 ms
android-app-on-google-play-en_app_rgb_wo_135x47.png
523 ms
154x40_WP_Store_blk.png
489 ms
socket.io-1.3.2.js
38 ms
android-apk.112x40.png
484 ms
front.8.100.jpg
491 ms
front.9.100.jpg
490 ms
front.4.100.jpg
516 ms
front.20.100.jpg
528 ms
86 ms
front.6.100.jpg
489 ms
front.5.100.jpg
479 ms
front.6.100.jpg
485 ms
front.5.100.jpg
487 ms
front.7.100.jpg
522 ms
front.18.100.jpg
529 ms
88 ms
front.7.100.jpg
489 ms
front.7.100.jpg
480 ms
front.9.100.jpg
564 ms
front.10.100.jpg
480 ms
front.5.100.jpg
521 ms
front.5.100.jpg
489 ms
269 ms
front.5.100.jpg
463 ms
front.7.100.jpg
470 ms
front.9.100.jpg
468 ms
front.7.100.jpg
512 ms
Available_on_the_App_Store_Badge_EN_135x40.png
520 ms
android-app-on-google-play-en_app_rgb_wo_135x47.png
490 ms
154x40_WP_Store_blk.png
485 ms
android-apk.112x40.png
492 ms
xd_arbiter.php
143 ms
like.php
59 ms
qeKvIRsJabD.js
485 ms
LVx-xkvaJ0b.png
550 ms
world.openfoodfacts.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
ARIA IDs are not unique
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
Buttons do not have an accessible name
No form fields have multiple labels
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
world.openfoodfacts.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
world.openfoodfacts.org 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
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 World.openfoodfacts.org 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 World.openfoodfacts.org 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.
world.openfoodfacts.org
Open Graph data is detected on the main page of World Openfoodfacts. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: