Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wholefood.com

Whole Foods Market | America’s Healthiest Grocery Store

Page Load Speed

5.2 sec in total

First Response

126 ms

Resources Loaded

4.3 sec

Page Rendered

688 ms

wholefood.com screenshot

About Website

Visit wholefood.com now to see the best up-to-date Whole Food content and also check out these interesting facts you probably never knew about wholefood.com

Are you hungry for better? When it comes to what we put in and on our bodies, Whole Foods Market® believes the full story of those products is important as we make our choices. Join us as we encourage...

Visit wholefood.com

Key Findings

We analyzed Wholefood.com page load time and found that the first response time was 126 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wholefood.com performance score

0

Network Requests Diagram

www.wholefoodsmarket.com

126 ms

capture_client.js

128 ms

css__6xjlWvLItzA40FWf0gbszWDZWgnBxiYOcpw1BT_wqbA__jZaSR4HZzBBliaBMOlbMCEL3r0eQ1LmugFrFYc-fuw8__HL4ux6Nk0a-Ajg9WMM6p45rdWWyCWAXMtpUIOFcb7Xc.css

111 ms

css__A6LxqOXxNOes7BC6SpCuA23vUwD8rUeYlvJiOfJyi-E__8TNe-nJWyVtNppr-3EoFvapplnWfnLGqxXWjH5ZqRsg__HL4ux6Nk0a-Ajg9WMM6p45rdWWyCWAXMtpUIOFcb7Xc.css

115 ms

css__ZEXcTf9PRyTAeSgk7YSGR8hGzZUKksYAjgCrZ2WUjDA__TpOrO88RGaDbek4apiBDvmfXoOZrgOiYKCbz7KMnoDU__HL4ux6Nk0a-Ajg9WMM6p45rdWWyCWAXMtpUIOFcb7Xc.css

115 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wholefood.com, 8% (11 requests) were made to D.adroll.com and 5% (7 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (43%)

Content Size

2.6 MB

After Optimization

1.5 MB

In fact, the total size of Wholefood.com main page is 2.6 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. 80% 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 196.7 kB

  • Original 256.4 kB
  • After minification 246.7 kB
  • After compression 59.7 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 196.7 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 41.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. Whole Food images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 380.8 kB

  • Original 601.4 kB
  • After minification 584.3 kB
  • After compression 220.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 380.8 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 490.1 kB

  • Original 601.1 kB
  • After minification 587.1 kB
  • After compression 111.0 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. Wholefood.com needs all CSS files to be minified and compressed as it can save up to 490.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 87 (72%)

Requests Now

121

After Optimization

34

The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whole Food. 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 7 to 1 for CSS and as a result speed up the page load time.

SEO Factors

wholefood.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wholefood.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 Wholefood.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Whole Food. 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: