Tools & Wizards About Us
tomatogrowers.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

tomatogrowers.com

Tomato Growers Supply Co: Tomatoes, Peppers, & More Seeds. Non-GMO – Tomato Growers Supply Company

Page Load Speed

1.3 sec in total

First Response

180 ms

Resources Loaded

944 ms

Page Rendered

187 ms

tomatogrowers.com screenshot

About Website

Visit tomatogrowers.com now to see the best up-to-date Tomato Growers content for United States and also check out these interesting facts you probably never knew about tomatogrowers.com

Tomato Growers Supply Company has a catalog of over 600 varieties of fruit and vegetable seeds, including tomatoes, peppers, eggplants, tomatillos, cucumbers, squash, onions, herbs, lettuce, broccoli,...

Visit tomatogrowers.com

Key Findings

We analyzed Tomatogrowers.com page load time and found that the first response time was 180 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

tomatogrowers.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

tomatogrowers.com

180 ms

www.tomatogrowers.com

372 ms

topnav.css

157 ms

sidenav.css

166 ms

storestyle.css

168 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 86% of them (19 requests) were addressed to the original Tomatogrowers.com, 9% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (372 ms) belongs to the original domain Tomatogrowers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.6 kB (35%)

Content Size

186.4 kB

After Optimization

121.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tomatogrowers.com main page is 186.4 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. 15% of websites need less resources to load. Images take 96.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 12.6 kB

  • Original 16.3 kB
  • After minification 13.1 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 3.2 kB, which is 20% 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 12.6 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 2.6 kB

  • Original 96.0 kB
  • After minification 93.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. Tomato Growers images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

CSS Optimization

-82%

Potential reduce by 17.4 kB

  • Original 21.1 kB
  • After minification 16.3 kB
  • After compression 3.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. Tomatogrowers.com needs all CSS files to be minified and compressed as it can save up to 17.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (21%)

Requests Now

19

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tomato Growers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tomatogrowers.com

tomatogrowers.com

180 ms

www.tomatogrowers.com

www.tomatogrowers.com

372 ms

topnav.css

topnav.css

157 ms

sidenav.css

sidenav.css

166 ms

storestyle.css

storestyle.css

168 ms

footernav.css

footernav.css

182 ms

design.css

design.css

184 ms

analytics.js

analytics.js

13 ms

HeaderLogo1_fade.jpg

HeaderLogo1_fade.jpg

245 ms

cart-icon.png

cart-icon.png

101 ms

goldbg.jpg

goldbg.jpg

102 ms

search-bg.gif

search-bg.gif

99 ms

btn_go.gif

btn_go.gif

99 ms

6064-th.jpg

6064-th.jpg

100 ms

6148-th.jpg

6148-th.jpg

183 ms

2783-th.jpg

2783-th.jpg

182 ms

3980-th.jpg

3980-th.jpg

189 ms

6313-th.jpg

6313-th.jpg

192 ms

3310-th.jpg

3310-th.jpg

194 ms

logo-sitelink7.png

logo-sitelink7.png

265 ms

collect

collect

13 ms

collect

collect

51 ms

Accessibility Review

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

tomatogrowers.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tomatogrowers.com SEO score

99

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomatogrowers.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Tomatogrowers.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

tomatogrowers.com

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