3.7 sec in total
245 ms
3.3 sec
222 ms
Click here to check amazing Foodland content for United States. Otherwise, check out these important facts you probably never knew about foodland.com
Visit foodland.comWe analyzed Foodland.com page load time and found that the first response time was 245 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.
foodland.com performance score
name
value
score
weighting
Value11.3 s
0/100
10%
Value35.5 s
0/100
25%
Value24.4 s
0/100
10%
Value490 ms
59/100
30%
Value0.649
9/100
15%
Value30.6 s
0/100
10%
245 ms
833 ms
248 ms
355 ms
235 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 96% of them (75 requests) were addressed to the original Foodland.com, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Foodland.com.
Page size can be reduced by 494.6 kB (19%)
2.7 MB
2.2 MB
In fact, the total size of Foodland.com main page is 2.7 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. 25% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 64.2 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 64.2 kB or 80% of the original size.
Potential reduce by 69.4 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. Foodland images are well optimized though.
Potential reduce by 282.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 282.3 kB or 72% of the original size.
Potential reduce by 78.7 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. Foodland.com needs all CSS files to be minified and compressed as it can save up to 78.7 kB or 81% of the original size.
Number of requests can be reduced by 39 (52%)
75
36
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foodland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and as a result speed up the page load time.
foodland.com
245 ms
www.foodland.com
833 ms
css_a81c2b2ba18d34bf41ea9459918defc0.css
248 ms
jquery.js
355 ms
drupal.js
235 ms
markermanager.js
240 ms
img_assist.js
234 ms
lightbox.js
258 ms
fivestar.js
369 ms
googleanalytics.js
352 ms
superfish.js
369 ms
jquery.bgiframe.min.js
371 ms
jquery.hoverIntent.minified.js
375 ms
nice_menus.js
469 ms
spamspan.compressed.js
470 ms
jquery.cycle.all.min.js
477 ms
views_slideshow.js
477 ms
views_slideshow.js
484 ms
extlink.js
497 ms
cufon-yui.js
589 ms
gmap_views_ajax.js
584 ms
base.js
594 ms
ajax_view.js
595 ms
mediarif_store.store_finder_block.js
599 ms
BlackJack_400.font.js
626 ms
Neutra400_400.font.js
704 ms
Neutra_Text_Alt_500.font.js
711 ms
jquery.fancybox.js
722 ms
swfobject.js
714 ms
jquery.highestheight.js
715 ms
jquery.header_width.js
747 ms
jquery.placeholder.js
820 ms
jquery.nav.js
828 ms
cufon-drupal.js
724 ms
bg_site.jpg
147 ms
bg_page_mid.png
144 ms
bg_header.jpg
149 ms
logo.png
147 ms
EmailIcon.png
144 ms
icon_twitter.png
145 ms
icon_facebook.png
239 ms
icon_instagram.png
239 ms
bg_search.png
240 ms
bg_top-nav.gif
240 ms
bg_dropdown_mid.png
268 ms
arrow-right.png
256 ms
bg_home-content_top-strip.jpg
356 ms
bg_home-content.jpg
471 ms
bg_hero_top.png
356 ms
bg_hero_btm.png
355 ms
bg_hero_mid.png
372 ms
flonline16_6415_foodland-vitacocosweeps-slider.jpg
881 ms
flonline16_6423_foodland-shopforhighereducationhomepagesliderthumbnail.jpg
717 ms
flonline15_5733_eltdigitalassets-10-27-onedayproducesale-homepageflash_1.jpg
1061 ms
flonline15_6188_tgifoodland-homepageslider.jpg
826 ms
flonline16_6519_foodland-updatethepotluckpartieshomepagesliderthumbnail.jpg
840 ms
flonline16_6457_foodland-newplatelunchreusablebaghomepageslider.jpg
932 ms
bg_weekly-specials.png
838 ms
bg_4box_hdr.png
947 ms
msw022416weeklyspecialsblockweb.jpg
1423 ms
bg_4box_btm.png
967 ms
email_signup.jpg
503 ms
arrow_red.png
1003 ms
emvideo-youtube-C0zLIjTh7to.jpg
1048 ms
my-rewards-coupon2.png
1066 ms
flmaikai15_6162_foodland-myrewardswebsitebug-tide2-24.png
1084 ms
store-locator.png
1129 ms
bg_zipcode.png
1164 ms
bg_footer_top.png
1175 ms
bg_footer.jpg
1146 ms
ga.js
88 ms
green-button.png
1065 ms
bg_page_btm.png
1113 ms
maikai-card.png
1142 ms
bg_dropdown_top.png
1153 ms
bg_dropdown_btm.png
1160 ms
__utm.gif
13 ms
collect
62 ms
foodland.com 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
foodland.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
foodland.com 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Foodland.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 Foodland.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.
foodland.com
Open Graph description is not detected on the main page of Foodland. 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: