1.6 sec in total
176 ms
1.3 sec
133 ms
Click here to check amazing Endive content. Otherwise, check out these important facts you probably never knew about endive.com
Endive recipes, news, product information, and company history from grower devoted to California endive.
Visit endive.comWe analyzed Endive.com page load time and found that the first response time was 176 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
endive.com performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value3.5 s
62/100
25%
Value2.6 s
97/100
10%
Value160 ms
94/100
30%
Value0.006
100/100
15%
Value5.2 s
75/100
10%
176 ms
385 ms
63 ms
126 ms
179 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 93% of them (43 requests) were addressed to the original Endive.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (422 ms) belongs to the original domain Endive.com.
Page size can be reduced by 51.0 kB (11%)
470.5 kB
419.5 kB
In fact, the total size of Endive.com main page is 470.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. 30% of websites need less resources to load. Images take 349.2 kB which makes up the majority of the site volume.
Potential reduce by 18.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. 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 18.7 kB or 76% of the original size.
Potential reduce by 11.9 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. Endive images are well optimized though.
Potential reduce by 14.6 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.6 kB or 18% of the original size.
Potential reduce by 5.8 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. Endive.com needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 40% of the original size.
Number of requests can be reduced by 22 (51%)
43
21
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Endive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
endive.com
176 ms
endive.com
385 ms
system.base.css
63 ms
system.menus.css
126 ms
system.messages.css
179 ms
system.theme.css
180 ms
views_slideshow.css
183 ms
aggregator.css
184 ms
comment.css
184 ms
field.css
185 ms
node.css
241 ms
search.css
241 ms
user.css
241 ms
views.css
243 ms
ctools.css
243 ms
views_slideshow_controls_text.css
245 ms
views_slideshow_cycle.css
302 ms
superfish.css
305 ms
endivestyle.css
302 ms
MyFontsWebfontsKit.css
303 ms
js_YD9ro0PAqY25gGWrTki6TjRUG8TdokmmxjfqpNNfzVU.js
365 ms
js_lboD8mxHbiFYKzdGkJi9JvFQWJGyCslzWjcNjvVR3X0.js
307 ms
js_SpzRgM3AWBAiHfz1njlTBrs65frbxss-N97EJiNkQV0.js
422 ms
js_fgELh6HgqJGWxTqyjvWa2R6LVW0I0EmUGx5VI85FfeA.js
365 ms
analytics.js
43 ms
homepage-green.gif
68 ms
EndiveField3.jpg
71 ms
CAEndiveFarms-LogoLG.png
152 ms
mcdoel_062122.jpg
152 ms
twitter.gif
69 ms
pinterest.gif
65 ms
youtube.gif
153 ms
arrows-rule.gif
153 ms
4EndiveRoots.jpg
188 ms
CROP_Braised_Endive_Butter_Thyme.jpg
154 ms
RedEndive.jpg
241 ms
slideshow-endive-group-crop.jpg
185 ms
bacon_and_sp_endive_3_of_4.jpg
242 ms
Rich_3.jpg
246 ms
Endive-Avocado-Cups.jpg
193 ms
_13P8162.jpg
260 ms
clipped-leaf-assort.jpg
261 ms
Endive-Product-Packs.jpg
261 ms
26AADF_0_0.woff
303 ms
collect
11 ms
js
52 ms
endive.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
endive.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
endive.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Endive.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 Endive.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.
endive.com
Open Graph description is not detected on the main page of Endive. 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: