2.2 sec in total
242 ms
1.8 sec
141 ms
Visit en.openfoodfacts.org now to see the best up-to-date En Openfoodfacts content for Germany and also check out these interesting facts you probably never knew about en.openfoodfacts.org
A collaborative, free and open database of ingredients, nutrition facts and information on food products from around the world
Visit en.openfoodfacts.orgWe analyzed En.openfoodfacts.org page load time and found that the first response time was 242 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
en.openfoodfacts.org performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value5.6 s
17/100
25%
Value11.1 s
6/100
10%
Value2,580 ms
4/100
30%
Value0.01
100/100
15%
Value11.0 s
21/100
10%
242 ms
433 ms
542 ms
313 ms
236 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original En.openfoodfacts.org, 58% (39 requests) were made to Static.openfoodfacts.org and 12% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (617 ms) relates to the external source Static.openfoodfacts.org.
Page size can be reduced by 776.7 kB (68%)
1.1 MB
368.3 kB
In fact, the total size of En.openfoodfacts.org main page is 1.1 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 686.1 kB which makes up the majority of the site volume.
Potential reduce by 42.9 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 42.9 kB or 76% of the original size.
Potential reduce by 24.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, En Openfoodfacts needs image optimization as it can save up to 24.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 509.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 509.6 kB or 74% 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. En.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 27 (44%)
62
35
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of En 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 25 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
en.openfoodfacts.org
242 ms
world.openfoodfacts.org
433 ms
app.css
542 ms
foundation-icons.css
313 ms
modernizr.js
236 ms
jquery.js
465 ms
jquery-ui.min.js
617 ms
jquery-ui.css
310 ms
select2.min.css
10 ms
slackin.js
268 ms
foundation.min.js
520 ms
jquery.cookie.js
239 ms
select2.min.js
4 ms
jquery.iframe-transport.js
239 ms
jquery.fileupload.js
444 ms
load-image.min.js
316 ms
canvas-to-blob.min.js
443 ms
jquery.fileupload-ip.js
444 ms
ga.js
58 ms
openfoodfacts-logo-en-178x150.png
189 ms
front.7.100.jpg
188 ms
front.9.100.jpg
189 ms
front.10.100.jpg
188 ms
front.5.100.jpg
187 ms
front.5.100.jpg
187 ms
front.5.100.jpg
219 ms
front.7.100.jpg
219 ms
front.9.100.jpg
192 ms
front.7.100.jpg
191 ms
front.18.100.jpg
192 ms
front.8.100.jpg
192 ms
front.9.100.jpg
318 ms
front.9.100.jpg
317 ms
front.10.100.jpg
317 ms
front.6.100.jpg
316 ms
front.13.100.jpg
317 ms
front.10.100.jpg
317 ms
front.3.100.jpg
393 ms
front.8.100.jpg
392 ms
front.6.100.jpg
392 ms
Available_on_the_App_Store_Badge_EN_135x40.png
390 ms
android-app-on-google-play-en_app_rgb_wo_135x47.png
389 ms
154x40_WP_Store_blk.png
393 ms
android-apk.112x40.png
466 ms
foundation-icons.woff
427 ms
all.js
52 ms
plusone.js
144 ms
widgets.js
287 ms
iframe
203 ms
__utm.gif
35 ms
collect
170 ms
121 ms
cb=gapi.loaded_0
49 ms
cb=gapi.loaded_1
46 ms
fastbutton
114 ms
xd_arbiter.php
40 ms
xd_arbiter.php
115 ms
postmessageRelay
98 ms
cb=gapi.loaded_0
46 ms
cb=gapi.loaded_1
45 ms
socket.io-1.3.2.js
262 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
59 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
63 ms
3193398744-postmessagerelay.js
37 ms
rpc:shindig_random.js
69 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
88 ms
cb=gapi.loaded_0
34 ms
en.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.
en.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
en.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 En.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 En.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.
en.openfoodfacts.org
Open Graph data is detected on the main page of En Openfoodfacts. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: