3.2 sec in total
849 ms
2.1 sec
247 ms
Click here to check amazing Houseplant 411 content for United States. Otherwise, check out these important facts you probably never knew about houseplant411.com
Have a houseplant that needs to be identified? Want to know how to care for your houseplant correctly? Ask Judy, the houseplant care expert, today at
Visit houseplant411.comWe analyzed Houseplant411.com page load time and found that the first response time was 849 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
houseplant411.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value12.5 s
0/100
25%
Value13.3 s
2/100
10%
Value990 ms
27/100
30%
Value0.292
41/100
15%
Value17.2 s
4/100
10%
849 ms
70 ms
22 ms
35 ms
94 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 81% of them (44 requests) were addressed to the original Houseplant411.com, 4% (2 requests) were made to Seal.networksolutions.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (849 ms) belongs to the original domain Houseplant411.com.
Page size can be reduced by 399.6 kB (53%)
757.6 kB
358.0 kB
In fact, the total size of Houseplant411.com main page is 757.6 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. Javascripts take 474.5 kB which makes up the majority of the site volume.
Potential reduce by 20.8 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 20.8 kB or 77% of the original size.
Potential reduce by 28.6 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. Obviously, Houseplant 411 needs image optimization as it can save up to 28.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 317.2 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 317.2 kB or 67% of the original size.
Potential reduce by 33.1 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. Houseplant411.com needs all CSS files to be minified and compressed as it can save up to 33.1 kB or 81% of the original size.
Number of requests can be reduced by 28 (55%)
51
23
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Houseplant 411. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
www.houseplant411.com
849 ms
style.css
70 ms
jquery-ui.css
22 ms
colorbox.css
35 ms
jquery.js
94 ms
jquery-migrate.min.js
42 ms
core.min.js
41 ms
datepicker.min.js
87 ms
widget.min.js
85 ms
mouse.min.js
85 ms
slider.min.js
86 ms
jquery-ui-timepicker-addon.js
115 ms
jquery.adrotate.dyngroup.js
88 ms
jquery.adrotate.clicktracker.js
87 ms
scripts.js
86 ms
jquery.sctabs.js
86 ms
jquery.colorbox-min.js
117 ms
jquery.validate.min.js
120 ms
siteseal.js
176 ms
wp-embed.min.js
114 ms
ga.js
45 ms
wp-emoji-release.min.js
58 ms
gpt.js
29 ms
__utm.gif
176 ms
pubads_impl_81.js
7 ms
container.html
147 ms
bg-repeating.png
142 ms
bg-footer.png
40 ms
logo.jpg
55 ms
butlogin.jpg
40 ms
butregister.jpg
37 ms
hdbuthoverl.jpg
37 ms
hdbuthoverr.jpg
51 ms
homepage-top-bg-new.png
60 ms
bg-feat-plant.png
57 ms
Anthurium-Red-061-256x202.jpg
62 ms
bg-read-about-featured.png
59 ms
bul-leaf.png
71 ms
divider-rpt.gif
79 ms
popular-houseplants.png
80 ms
divider.gif
79 ms
plant-wizard1.png
81 ms
watering-reminders.png
84 ms
ask-judy.png
91 ms
glossary.png
101 ms
foogrd.gif
99 ms
face.jpg
100 ms
twit.jpg
102 ms
overlay.png
104 ms
border.png
110 ms
controls.png
120 ms
basicrecgreen.gif
32 ms
collect
65 ms
ga-audiences
36 ms
houseplant411.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
Buttons do not have an accessible name
Links do not have a discernible name
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
houseplant411.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
houseplant411.com SEO score
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 Houseplant411.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 Houseplant411.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.
houseplant411.com
Open Graph description is not detected on the main page of Houseplant 411. 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: