2.9 sec in total
237 ms
1.5 sec
1.2 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 237 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
wellsfoodservice.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value5.1 s
26/100
25%
Value3.1 s
92/100
10%
Value1,350 ms
17/100
30%
Value0.23
54/100
15%
Value8.7 s
36/100
10%
237 ms
172 ms
52 ms
38 ms
72 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Wellsfoodservice.com, 41% (20 requests) were made to Wellsfoodservice.azureedge.net and 18% (9 requests) were made to Wellsmanagedcontent.azureedge.net. The less responsive or slowest element that took the longest time to load (801 ms) relates to the external source Wellsmanagedcontent.azureedge.net.
Page size can be reduced by 55.0 kB (7%)
738.5 kB
683.5 kB
In fact, the total size of Wellsfoodservice.com main page is 738.5 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. 35% of websites need less resources to load. Images take 537.8 kB which makes up the majority of the site volume.
Potential reduce by 31.0 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 31.0 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 14.8 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 14.8 kB or 11% 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 29 (60%)
48
19
The browser has sent 48 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 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
wellsfoodservice.com
237 ms
baz6ckk.css
172 ms
css2
52 ms
slick.css
38 ms
style.min.css
72 ms
site.min.css
83 ms
v2.js
51 ms
jquery.min.js
101 ms
slick.min.js
38 ms
lazysizes.min.js
108 ms
ls.bgset.min.js
110 ms
picturefill.min.js
110 ms
micromodal.min.js
112 ms
tinysort.min.js
110 ms
bundled-components.js
111 ms
contact.js
116 ms
search.js
116 ms
product-details.js
117 ms
filtering.js
120 ms
jquery.unobtrusive-ajax.min.js
118 ms
jquery.validate.min.js
42 ms
jquery.validate.unobtrusive.min.js
53 ms
normalize.css
51 ms
p.css
30 ms
gtm.js
143 ms
wells-logo.svg
102 ms
e0d66e7b-45aa-47d8-b0ec-6efba2c27b34.v1.svg
384 ms
4oz-hero.v1.png
396 ms
wells-logo-blended.svg
35 ms
wells-logo-footer.svg
29 ms
1e084615-6ccd-4a7c-8ef0-b1a6af7a83d3.v1.svg
467 ms
369b2516-3805-4da3-b697-57c458fa2f05.v1.svg
329 ms
4fd8dc88-159c-4a19-8708-bfdae85a8789.v2.svg
334 ms
b141d2a5-bcca-4628-a772-849d4522362f.v1.svg
328 ms
8c2ca759-9123-435c-a4b4-957b71490c15.v1.svg
487 ms
f6c2d668-00ac-4edb-9e98-b0fbec1b0936.v1.svg
345 ms
e2cf2946-73a7-438e-8181-83641100f4ae.v1.svg
801 ms
bf071cc0-dda3-448c-bec1-661d3cc460b2.v1.svg
346 ms
ai.2.min.js
96 ms
wells-logo-blended.svg
265 ms
js
63 ms
analytics.js
147 ms
20865621.js
204 ms
collect
27 ms
foodservice-guide-2024.v1.jpg
465 ms
collect
16 ms
20865621.js
89 ms
banner.js
86 ms
collectedforms.js
39 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.
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: