5.1 sec in total
976 ms
3.4 sec
745 ms
Visit houseplantz.net now to see the best up-to-date House Plantz content and also check out these interesting facts you probably never knew about houseplantz.net
house plants - care and propagation
Visit houseplantz.netWe analyzed Houseplantz.net page load time and found that the first response time was 976 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
houseplantz.net performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value3.0 s
78/100
25%
Value6.9 s
34/100
10%
Value2,400 ms
5/100
30%
Value0
100/100
15%
Value9.5 s
30/100
10%
976 ms
221 ms
245 ms
552 ms
245 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 64% of them (35 requests) were addressed to the original Houseplantz.net, 13% (7 requests) were made to Pagead2.googlesyndication.com and 11% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Houseplantz.net.
Page size can be reduced by 160.3 kB (19%)
830.6 kB
670.2 kB
In fact, the total size of Houseplantz.net main page is 830.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. 35% of websites need less resources to load. Images take 606.6 kB which makes up the majority of the site volume.
Potential reduce by 26.1 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 26.1 kB or 77% of the original size.
Potential reduce by 13.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. House Plantz images are well optimized though.
Potential reduce by 105.5 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 105.5 kB or 61% of the original size.
Potential reduce by 14.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. Houseplantz.net needs all CSS files to be minified and compressed as it can save up to 14.8 kB or 80% of the original size.
Number of requests can be reduced by 13 (25%)
51
38
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of House Plantz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
houseplantz.net
976 ms
style.css
221 ms
front.css
245 ms
jquery.js
552 ms
jquery-migrate.min.js
245 ms
show_ads.js
8 ms
front.js
217 ms
wp-embed.min.js
220 ms
wp-emoji-release.min.js
346 ms
Indoor-Plant-Site.jpg
435 ms
aspidistra-elatior-01.jpg
563 ms
tmb_aspidistra-elatior-01.jpg
335 ms
tmb_aspidistra-elatior-02.jpg
335 ms
tmb_aspidistra-elatior-03.jpg
332 ms
tmb_aspidistra-elatior-04.jpg
335 ms
tmb_aspidistra-elatior-05.jpg
564 ms
tmb_aspidistra-elatior-06.jpg
564 ms
ornithogalum-dubium.jpg
884 ms
ornithogalum-dubium-flowers.jpg
775 ms
episcia-silver-frog1-480x320.jpg
987 ms
episcia-flower-480x320.jpg
1080 ms
euphorbia-horrida1-480x320.jpg
1092 ms
euphorbia-horrida-flowers-480x320.jpg
1100 ms
crassula-ausensis1-480x320.jpg
1210 ms
crassula-ausensis-leaves-480x320.jpg
1426 ms
chirita-sinensis-480x320.jpg
1530 ms
chirita-sinensis-leaf-480x320.jpg
1743 ms
peperomia-columella.jpg
1533 ms
peperomia-rotundifolia-1.jpg
1638 ms
tmb_peperomia-rotundifolia-1.jpg
1428 ms
tmb_peperomia-rotundifolia-2.jpg
1644 ms
tmb_peperomia-rotundifolia-3.jpg
1648 ms
adromischus-bolusii.jpg
1961 ms
ca-pub-7836581778119886.js
258 ms
zrt_lookup.html
272 ms
show_ads_impl.js
211 ms
header.jpg
1951 ms
848 ms
ads
187 ms
osd.js
19 ms
ads
200 ms
ads
203 ms
ads
147 ms
google_adsense_script.html
1411 ms
abg.js
43 ms
google_adsense_script.html
1386 ms
m_js_controller.js
31 ms
favicon
46 ms
s
16 ms
googlelogo_color_112x36dp.png
30 ms
nessie_icon_tiamat_white.png
16 ms
x_button_blue2.png
16 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
4 ms
activeview
16 ms
google_adsense_script.js
5 ms
houseplantz.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
houseplantz.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
houseplantz.net 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
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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Houseplantz.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Houseplantz.net 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.
houseplantz.net
Open Graph description is not detected on the main page of House Plantz. 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: