2.1 sec in total
160 ms
1.8 sec
192 ms
Welcome to eeplants.com homepage info - get ready to check EEplants best content right away, or after learning these important things about eeplants.com
Visit eeplants.comWe analyzed Eeplants.com page load time and found that the first response time was 160 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
eeplants.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value2.9 s
80/100
25%
Value2.9 s
95/100
10%
Value160 ms
93/100
30%
Value0.182
67/100
15%
Value4.3 s
84/100
10%
160 ms
231 ms
95 ms
237 ms
98 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 98% of them (138 requests) were addressed to the original Eeplants.com, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (365 ms) belongs to the original domain Eeplants.com.
Page size can be reduced by 308.0 kB (11%)
2.7 MB
2.4 MB
In fact, the total size of Eeplants.com main page is 2.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 42.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 8.0 kB, which is 16% 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 42.4 kB or 86% of the original size.
Potential reduce by 13.0 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. EEplants images are well optimized though.
Potential reduce by 160.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 160.6 kB or 69% of the original size.
Potential reduce by 92.0 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. Eeplants.com needs all CSS files to be minified and compressed as it can save up to 92.0 kB or 92% of the original size.
Number of requests can be reduced by 12 (9%)
137
125
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EEplants. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eeplants.com
160 ms
www.eeplants.com
231 ms
style.css
95 ms
homegallery.css
237 ms
jquery.fancybox.css
98 ms
jquery.mCustomScrollbar.css
96 ms
responsive.css
96 ms
jquery-1.8.3.min.js
218 ms
bootstrap.js
140 ms
homegalleryscript.js
150 ms
jquery.masonry.js
145 ms
jquery.fancybox.js
228 ms
jquery-ui.min.js
13 ms
jquery.mousewheel.min.js
106 ms
jquery.mCustomScrollbar.js
250 ms
bg-body-home.jpg
85 ms
logo.png
88 ms
35years.jpg
87 ms
35years-ipad.jpg
83 ms
35years-iphone.jpg
86 ms
owner-small.png
127 ms
darkbg.jpg
120 ms
image-loader.gif
122 ms
img1.jpg
125 ms
img2.jpg
129 ms
img3.jpg
130 ms
img4.jpg
151 ms
img5.jpg
149 ms
img6.jpg
173 ms
img7.jpg
174 ms
img8.jpg
178 ms
img9.jpg
223 ms
img10.jpg
241 ms
img11.jpg
202 ms
img12.jpg
220 ms
img15.jpg
228 ms
img16.jpg
230 ms
img13.jpg
267 ms
img14.jpg
308 ms
img17.jpg
267 ms
img18.jpg
276 ms
img19.jpg
280 ms
img20.jpg
296 ms
img21.jpg
313 ms
img22.jpg
316 ms
img23.jpg
323 ms
img24.jpg
329 ms
img25.jpg
345 ms
img26.jpg
353 ms
img27.jpg
332 ms
img28.jpg
331 ms
ga.js
34 ms
img29.jpg
298 ms
img30.jpg
301 ms
img31.jpg
323 ms
img32.jpg
340 ms
__utm.gif
13 ms
img33.jpg
304 ms
img34.jpg
365 ms
img35.jpg
325 ms
img36.jpg
309 ms
img37.jpg
332 ms
img38.jpg
342 ms
img39.jpg
345 ms
img40.jpg
333 ms
img41.jpg
351 ms
img42.jpg
335 ms
img43.jpg
344 ms
img44.jpg
344 ms
img45.jpg
326 ms
img46.jpg
334 ms
img47.jpg
326 ms
img48.jpg
339 ms
img49.jpg
337 ms
img50.jpg
329 ms
img51.jpg
311 ms
img52.jpg
338 ms
img53.jpg
329 ms
img54.jpg
334 ms
img1.jpg
319 ms
img2.jpg
314 ms
img3.jpg
316 ms
img5.jpg
335 ms
img4.jpg
328 ms
img6.jpg
332 ms
img7a.jpg
318 ms
img7b.jpg
311 ms
img8.jpg
308 ms
img9.jpg
334 ms
img10.jpg
333 ms
img11.jpg
332 ms
img12.jpg
313 ms
img13.jpg
298 ms
img14.jpg
300 ms
img15.jpg
321 ms
img16.jpg
314 ms
img17.jpg
306 ms
img19.jpg
295 ms
img18.jpg
296 ms
img20.jpg
292 ms
img21.jpg
316 ms
img22.jpg
311 ms
img23.jpg
302 ms
img24.jpg
294 ms
img25.jpg
301 ms
img26.jpg
291 ms
img27.jpg
300 ms
img29.jpg
303 ms
img28.jpg
293 ms
img30.jpg
288 ms
img32.jpg
296 ms
img31.jpg
289 ms
img33.jpg
289 ms
img34.jpg
299 ms
img35.jpg
295 ms
img36.jpg
292 ms
img37.jpg
294 ms
img38.jpg
287 ms
img39.jpg
292 ms
img40.jpg
303 ms
img41.jpg
294 ms
img42.jpg
296 ms
img43.jpg
293 ms
img44.jpg
294 ms
img45.jpg
288 ms
img46.jpg
295 ms
img47.jpg
298 ms
img48.jpg
294 ms
img49.jpg
295 ms
img50.jpg
296 ms
img51.jpg
293 ms
img52.jpg
295 ms
img53.jpg
297 ms
img54.jpg
296 ms
logo-footer.png
309 ms
icon-fb.png
311 ms
icon-twitter.png
304 ms
icon-link-in.png
290 ms
icon-rss.png
294 ms
badge.png
298 ms
bg-footer.jpg
324 ms
eeplants.com accessibility score
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
eeplants.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
eeplants.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eeplants.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 Eeplants.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.
eeplants.com
Open Graph description is not detected on the main page of EEplants. 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: