1.3 sec in total
153 ms
738 ms
449 ms
Visit produce1.com now to see the best up-to-date Produce1 content and also check out these interesting facts you probably never knew about produce1.com
Fresh Produce Price Directory, Produce Historical prices, Fresh Produce FOB Market Prices and Reports, Fruit Prices, Vegetable Prices, sales@produce1.com, Skype: earlhb, General Farm Classifieds
Visit produce1.comWe analyzed Produce1.com page load time and found that the first response time was 153 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
produce1.com performance score
153 ms
234 ms
17 ms
133 ms
11 ms
Our browser made a total of 13 requests to load all elements on the main page. We found that 23% of them (3 requests) were addressed to the original Produce1.com, 31% (4 requests) were made to Ssl.google-analytics.com and 15% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (294 ms) relates to the external source Produceone.com.
Page size can be reduced by 23.9 kB (50%)
48.0 kB
24.1 kB
In fact, the total size of Produce1.com main page is 48.0 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. HTML takes 30.5 kB which makes up the majority of the site volume.
Potential reduce by 23.9 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 23.9 kB or 78% 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. Produce1 images are well optimized though.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
We found no issues to fix!
9
9
The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Produce1. According to our analytics all requests are already optimized.
produce1.com
153 ms
produce1.com
234 ms
ga.js
17 ms
producemarket.htm
133 ms
__utm.gif
11 ms
Produce1-facebook1aa.gif
294 ms
like.php
223 ms
__utm.gif
50 ms
tf.php
7 ms
counter.js
9 ms
__utm.gif
7 ms
ps-Eilrh7GF.js
21 ms
FEppCFCt76d.png
10 ms
produce1.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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
produce1.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
produce1.com SEO score
EN
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Produce1.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Produce1.com main page’s claimed encoding is windows-1252. 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.
produce1.com
Open Graph description is not detected on the main page of Produce1. 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: