3.7 sec in total
241 ms
2.5 sec
1 sec
Visit wellsfoodservice.com now to see the best up-to-date Wells Foodservice content for United States and also check out these interesting facts you probably never knew about wellsfoodservice.com
Discover the #1 manufacturer of ice cream and frozen novelties in the foodservice channel. We're leading the industry in marketing support, insights, and innovation.
Visit wellsfoodservice.comWe analyzed Wellsfoodservice.com page load time and found that the first response time was 241 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.
wellsfoodservice.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.5 s
64/100
25%
Value4.1 s
79/100
10%
Value2,350 ms
5/100
30%
Value0.261
47/100
15%
Value9.7 s
29/100
10%
241 ms
43 ms
51 ms
33 ms
525 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Wellsfoodservice.com, 49% (20 requests) were made to Wellsfoodservice.azureedge.net and 22% (9 requests) were made to Wellsmanagedcontent.azureedge.net. The less responsive or slowest element that took the longest time to load (940 ms) relates to the external source Wellsfoodservice.azureedge.net.
Page size can be reduced by 47.3 kB (7%)
634.1 kB
586.9 kB
In fact, the total size of Wellsfoodservice.com main page is 634.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 502.8 kB which makes up the majority of the site volume.
Potential reduce by 30.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. This page needs HTML code to be minified as it can gain 5.7 kB, which is 14% 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.2 kB or 76% of the original size.
Potential reduce by 0 B
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. Wells Foodservice images are well optimized though.
Potential reduce by 7.9 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 7.9 kB or 13% of the original size.
Potential reduce by 9.2 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. Wellsfoodservice.com needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 30% of the original size.
Number of requests can be reduced by 23 (58%)
40
17
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wells Foodservice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
{{url}}
{{time}} ms
wellsfoodservice.com accessibility score
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
Links do not have a discernible name
wellsfoodservice.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wellsfoodservice.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
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 Wellsfoodservice.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 Wellsfoodservice.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.
{{og_description}}
wellsfoodservice.com
Open Graph description is not detected on the main page of Wells Foodservice. 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: