33.8 sec in total
214 ms
26.4 sec
7.2 sec
Welcome to foodsafety.gov homepage info - get ready to check Food Safety best content for United States right away, or after learning these important things about foodsafety.gov
Get the latest news, tips, and alerts from foodsafety.gov and find out what you need to know about safely handling and storing food to prevent food poisoning.
Visit foodsafety.govWe analyzed Foodsafety.gov page load time and found that the first response time was 214 ms and then it took 33.6 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.
foodsafety.gov performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value11.3 s
0/100
25%
Value11.1 s
6/100
10%
Value2,920 ms
3/100
30%
Value0.009
100/100
15%
Value23.4 s
1/100
10%
214 ms
560 ms
1153 ms
304 ms
378 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 60% of them (55 requests) were addressed to the original Foodsafety.gov, 10% (9 requests) were made to Google-analytics.com and 5% (5 requests) were made to Hhsfoodsafety.mpeasylink.com. The less responsive or slowest element that took the longest time to load (11.3 sec) relates to the external source Rules.quantcount.com.
Page size can be reduced by 1.3 MB (65%)
2.0 MB
707.9 kB
In fact, the total size of Foodsafety.gov main page is 2.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. 55% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 30.4 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 5.2 kB, which is 13% 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 30.4 kB or 76% of the original size.
Potential reduce by 37.8 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, Food Safety needs image optimization as it can save up to 37.8 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 1.2 MB
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 1.2 MB or 72% of the original size.
Potential reduce by 61.8 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. Foodsafety.gov needs all CSS files to be minified and compressed as it can save up to 61.8 kB or 81% of the original size.
Number of requests can be reduced by 49 (55%)
89
40
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Food Safety. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
foodsafety.gov
214 ms
www.foodsafety.gov
560 ms
326351909.js
1153 ms
style.css
304 ms
home-new.css
378 ms
addthis.css
1052 ms
suggestion.css
1053 ms
jquery-1.4.2.min.js
1053 ms
main.js
1051 ms
date.js
1052 ms
jgfeed.js
1052 ms
mp_linkcode.js
1149 ms
swfobject.js
1148 ms
home_text.js
1122 ms
share.css
1121 ms
share.js
1061 ms
common.js
1121 ms
aria-menu.js
3375 ms
suggestion.js
3580 ms
mpel.js
2493 ms
search-button.png
892 ms
billboard-harvey.jpg
888 ms
more-recalls-button.png
887 ms
foodsafety_recall-alert-section-photo-363x152px.jpg
993 ms
read-more-btn.png
886 ms
papaya-outbreak.jpg
957 ms
4-simple-steps-type.png
882 ms
clean-button.png
957 ms
separate-button.png
955 ms
cook-button.png
922 ms
chill-button.png
955 ms
footer-logo.png
955 ms
mail-icon.png
955 ms
facebook-icon.png
954 ms
twitter-icon.png
863 ms
pinterest-icon.png
864 ms
rss-icon.png
1126 ms
whitehouse-logo.png
862 ms
hhs-logo.png
894 ms
usda-logo.png
861 ms
fda-logo.png
1321 ms
cdc-logo.png
1293 ms
nih-logo.png
1294 ms
us-flag.png
1324 ms
gtm.js
2001 ms
header-bg.png
1314 ms
logo.png
1313 ms
media-nav-separator.png
1314 ms
navbar.gif
1314 ms
main-nav-sep.png
1045 ms
learn-more-arrow.png
1315 ms
recalls-icon.png
1283 ms
recall-title-separator.png
1282 ms
bottom-section-bg.png
1472 ms
featured-blog-post-icon.png
1472 ms
whats-hot-icon.png
1471 ms
whats-hot-search-title-separator.png
1471 ms
popular-search-icon.png
1470 ms
yql
1181 ms
mpel_storage.html
635 ms
quant.js
1294 ms
analytics.js
1473 ms
Universal-Federated-Analytics-Min.js
3338 ms
measure.min.js
2541 ms
mobile-detect.min.js
3240 ms
mpel
648 ms
mpel_ssd.js
1453 ms
rules-p-MHnPPHBQmnXL1.js
11349 ms
linkid.js
1580 ms
mpel_storage.html
8249 ms
textlink-ads.jpg
7953 ms
textlink-ads.jpg
7792 ms
collect
8437 ms
iframe_api
8084 ms
gpt.js
5544 ms
collect
2274 ms
collect
2273 ms
collect
2372 ms
collect
2191 ms
collect
2190 ms
collect
2189 ms
collect
2454 ms
collect
2832 ms
pixel;r=1649182913;labels=wwwfoodsafetygov;rf=0;a=p-MHnPPHBQmnXL1;url=https%3A%2F%2Fwww.foodsafety.gov%2F;fpan=1;fpa=P0-1774383118-1504642070264;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504642070263;tzo=-180;ogl=
1318 ms
a.js
1512 ms
www-widgetapi.js
1531 ms
pubads_impl_147.js
2212 ms
ga-audiences
2095 ms
ga-audiences
2095 ms
ga-audiences
2094 ms
container.html
282 ms
tags
324 ms
foodsafety.gov accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
foodsafety.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
foodsafety.gov SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Foodsafety.gov 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 Foodsafety.gov 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.
foodsafety.gov
Open Graph description is not detected on the main page of Food Safety. 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: