35.9 sec in total
165 ms
10.7 sec
25 sec
Click here to check amazing Food Facts content for United States. Otherwise, check out these important facts you probably never knew about foodfacts.com
Foodfacts: Find out whats REALLY in your food. Find nutritional information on food allergies, ingredients, calories, diet and more.
Visit foodfacts.comWe analyzed Foodfacts.com page load time and found that the first response time was 165 ms and then it took 35.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
foodfacts.com performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value17.2 s
0/100
25%
Value1.6 s
100/100
10%
Value50 ms
100/100
30%
Value0
100/100
15%
Value2.1 s
99/100
10%
165 ms
1253 ms
868 ms
1527 ms
379 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 52% of them (51 requests) were addressed to the original Foodfacts.com, 32% (32 requests) were made to Themefiles.foodfacts.com and 5% (5 requests) were made to Cdn.foodfacts.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Google.com.
Page size can be reduced by 1.5 MB (25%)
6.0 MB
4.5 MB
In fact, the total size of Foodfacts.com main page is 6.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 61.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. This page needs HTML code to be minified as it can gain 16.0 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 61.9 kB or 84% of the original size.
Potential reduce by 328.2 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 Facts images are well optimized though.
Potential reduce by 640.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 640.3 kB or 68% of the original size.
Potential reduce by 457.9 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. Foodfacts.com needs all CSS files to be minified and compressed as it can save up to 457.9 kB or 78% of the original size.
Number of requests can be reduced by 45 (48%)
93
48
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Food Facts. 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 20 to 1 for CSS and as a result speed up the page load time.
foodfacts.com
165 ms
www.foodfacts.com
1253 ms
jquery-3.2.1.min.js
868 ms
jquery-ui.min.js
1527 ms
typeahead.css
379 ms
bootstrap.css
523 ms
bootstrap-theme.css
637 ms
font-awesome.min.css
637 ms
themify-icons.css
636 ms
colortip-1.0-jquery.css
515 ms
animate.css
514 ms
magnific-popup.css
730 ms
bootstrap-datetimepicker.min.css
730 ms
custom.css
731 ms
style.css
728 ms
widget.css
523 ms
styles.css
407 ms
social_widget.css
523 ms
css.php
406 ms
style-front-end.css
522 ms
style.css
522 ms
dashicons.min.css
729 ms
jquery-ui-dialog.min.css
727 ms
api.js
2479 ms
bootstrap.min.js
475 ms
jquery.magnific-popup.min.js
474 ms
moment.js
1151 ms
bootstrap-datetimepicker.min.js
1077 ms
colortip-1.0-jquery.js
1077 ms
foodfacts.js
1149 ms
ff_product_results.js
1150 ms
typeahead.bundle.js
1075 ms
ff_product_search.js
2221 ms
ff_login.js
2221 ms
login-with-ajax.js
470 ms
upload.js
470 ms
wp-embed.min.js
469 ms
css
255 ms
recaptcha__en.js
1422 ms
made_in_usa.png
304 ms
curved_arrow.png
304 ms
303062.jpg
1388 ms
slide1.png
288 ms
slide2.png
365 ms
slide3.png
308 ms
slide4.png
289 ms
slide5.png
301 ms
slide6.png
430 ms
slide7.png
429 ms
slide8.png
595 ms
slide9.png
430 ms
download-apple.png
430 ms
download-google.png
380 ms
peanuts-icon.png
546 ms
animal-derived-icon.png
547 ms
msg-icon.png
546 ms
eggs-icon.png
545 ms
soy-icon.png
545 ms
fish-icon.png
1335 ms
shellfish-icon.png
1334 ms
tree-nuts-icon.png
1335 ms
dairy-icon.png
1334 ms
wheat-icon.png
1245 ms
sugars-icon.png
1244 ms
nightshades-icon.png
1884 ms
corn-icon.png
1966 ms
FullSizeR-1-551x402.jpg
1884 ms
FullSizeRender-74-535x402.jpg
1746 ms
FullSizeRender-73-494x402.jpg
1745 ms
weight-watcher-home.png
1745 ms
egg-icon.png
1830 ms
sulfites-icon.png
1829 ms
gluten-icon.png
1871 ms
flavorings-icon.png
1829 ms
shell-fish-icon.png
1829 ms
controversial-ingredients-icon.png
1829 ms
image3.png
1904 ms
303066.jpg
1825 ms
303059.jpg
1826 ms
303182.jpg
1903 ms
303064.jpg
1842 ms
download-apple.png
207 ms
download-google.png
206 ms
food-facts-apple.png
207 ms
rfna-logo.png
262 ms
analytics.js
1794 ms
counter.js
347 ms
image2.png
1824 ms
image1.png
1845 ms
t.php
1283 ms
ff_new_back.jpg
1225 ms
score_sprite_small.png
469 ms
bnW1TuTV2YGcoh1HyWNQ_IMG_0207-second.png
2228 ms
fruit-bg-3.png
2115 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
2066 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
2061 ms
themify.woff
2109 ms
collect
355 ms
fontawesome-webfont.woff
212 ms
foodfacts.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
foodfacts.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
foodfacts.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foodfacts.com 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 Foodfacts.com 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.
foodfacts.com
Open Graph description is not detected on the main page of Food Facts. 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: