Tools & Wizards About Us
wellsfoodservice.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wellsfoodservice.com

Your Ice Cream & Frozen Novelties Supplier - Wells Foodservice

Page Load Speed

3.7 sec in total

First Response

241 ms

Resources Loaded

2.5 sec

Page Rendered

1 sec

wellsfoodservice.com screenshot

About Website

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.com

Key Findings

We 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.

Performance Metrics

wellsfoodservice.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value2,350 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.261

47/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

wellsfoodservice.com

241 ms

baz6ckk.css

43 ms

css2

51 ms

slick.css

33 ms

style.min.css

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 Optimization Overview & Recommendations

Page size can be reduced by 47.3 kB (7%)

Content Size

634.1 kB

After Optimization

586.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-76%

Potential reduce by 30.2 kB

  • Original 39.6 kB
  • After minification 33.9 kB
  • After compression 9.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.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.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 502.8 kB
  • After minification 502.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. Wells Foodservice images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 7.9 kB

  • Original 60.6 kB
  • After minification 60.5 kB
  • After compression 52.7 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.

CSS Optimization

-30%

Potential reduce by 9.2 kB

  • Original 31.1 kB
  • After minification 31.0 kB
  • After compression 21.9 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.

Requests Breakdown

Number of requests can be reduced by 23 (58%)

Requests Now

40

After Optimization

17

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

wellsfoodservice.com

wellsfoodservice.com

241 ms

baz6ckk.css

baz6ckk.css

43 ms

css2

css2

51 ms

slick.css

slick.css

33 ms

style.min.css

style.min.css

525 ms

site.min.css

site.min.css

729 ms

v2.js

v2.js

61 ms

jquery.min.js

jquery.min.js

874 ms

slick.min.js

slick.min.js

35 ms

lazysizes.min.js

lazysizes.min.js

724 ms

ls.bgset.min.js

ls.bgset.min.js

728 ms

picturefill.min.js

picturefill.min.js

718 ms

micromodal.min.js

micromodal.min.js

711 ms

tinysort.min.js

tinysort.min.js

940 ms

bundled-components.js

bundled-components.js

738 ms

contact.js

contact.js

734 ms

search.js

search.js

915 ms

product-details.js

product-details.js

923 ms

filtering.js

filtering.js

919 ms

jquery.unobtrusive-ajax.min.js

jquery.unobtrusive-ajax.min.js

909 ms

jquery.validate.min.js

jquery.validate.min.js

45 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

62 ms

p.css

p.css

20 ms

normalize.css

normalize.css

583 ms

gtm.js

gtm.js

102 ms

e0d66e7b-45aa-47d8-b0ec-6efba2c27b34.v1.svg

e0d66e7b-45aa-47d8-b0ec-6efba2c27b34.v1.svg

359 ms

wells-logo.svg

wells-logo.svg

377 ms

4oz-hero.v1.png

4oz-hero.v1.png

376 ms

wells-logo-footer.svg

wells-logo-footer.svg

248 ms

1e084615-6ccd-4a7c-8ef0-b1a6af7a83d3.v1.svg

1e084615-6ccd-4a7c-8ef0-b1a6af7a83d3.v1.svg

542 ms

369b2516-3805-4da3-b697-57c458fa2f05.v1.svg

369b2516-3805-4da3-b697-57c458fa2f05.v1.svg

539 ms

4fd8dc88-159c-4a19-8708-bfdae85a8789.v2.svg

4fd8dc88-159c-4a19-8708-bfdae85a8789.v2.svg

547 ms

b141d2a5-bcca-4628-a772-849d4522362f.v1.svg

b141d2a5-bcca-4628-a772-849d4522362f.v1.svg

739 ms

8c2ca759-9123-435c-a4b4-957b71490c15.v1.svg

8c2ca759-9123-435c-a4b4-957b71490c15.v1.svg

557 ms

f6c2d668-00ac-4edb-9e98-b0fbec1b0936.v1.svg

f6c2d668-00ac-4edb-9e98-b0fbec1b0936.v1.svg

703 ms

e2cf2946-73a7-438e-8181-83641100f4ae.v1.svg

e2cf2946-73a7-438e-8181-83641100f4ae.v1.svg

841 ms

bf071cc0-dda3-448c-bec1-661d3cc460b2.v1.svg

bf071cc0-dda3-448c-bec1-661d3cc460b2.v1.svg

716 ms

ai.2.min.js

ai.2.min.js

111 ms

wells-logo-blended.svg

wells-logo-blended.svg

349 ms

wells-logo-blended.svg

wells-logo-blended.svg

47 ms

foodservice-guide-2024.v2.jpg

foodservice-guide-2024.v2.jpg

709 ms

Accessibility Review

wellsfoodservice.com accessibility score

98

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

wellsfoodservice.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

wellsfoodservice.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 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.

Social Sharing Optimization

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: