2.3 sec in total
27 ms
1.8 sec
422 ms
Visit plantlust.com now to see the best up-to-date Plant Lust content for United States and also check out these interesting facts you probably never knew about plantlust.com
Shop multiple independent nurseries in a single spot. Inspired garden plants, houseplants, and gifts for plant lovers
Visit plantlust.comWe analyzed Plantlust.com page load time and found that the first response time was 27 ms and then it took 2.2 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.
plantlust.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.4 s
1/100
25%
Value6.4 s
40/100
10%
Value950 ms
29/100
30%
Value0.095
91/100
15%
Value8.6 s
37/100
10%
27 ms
1753 ms
72 ms
43 ms
67 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Plantlust.com, 65% (33 requests) were made to D17vsf20mehj1i.cloudfront.net and 10% (5 requests) were made to Widgets.shopifyapps.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Use.typekit.net.
Page size can be reduced by 609.9 kB (40%)
1.5 MB
897.5 kB
In fact, the total size of Plantlust.com main page is 1.5 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. 45% of websites need less resources to load. Images take 657.6 kB which makes up the majority of the site volume.
Potential reduce by 26.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 6.4 kB, which is 20% 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 26.4 kB or 83% of the original size.
Potential reduce by 7.1 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. Plant Lust images are well optimized though.
Potential reduce by 423.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 423.6 kB or 67% of the original size.
Potential reduce by 152.9 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. Plantlust.com needs all CSS files to be minified and compressed as it can save up to 152.9 kB or 81% of the original size.
Number of requests can be reduced by 9 (18%)
49
40
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plant Lust. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
plantlust.com
27 ms
izq2dtq.js
1753 ms
dff6f017066b.css
72 ms
jsapi
43 ms
059e9f60a4fc.js
67 ms
client.js
59 ms
background-repeat.png
8 ms
plant_lust_logo.png
7 ms
11_20111211T181925_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
43 ms
14776_20110423T022641_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
48 ms
4877_20101102T021521_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
52 ms
4881_20101226T173512_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
45 ms
69_20110602T201232_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
13 ms
6226_20101201T045131_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
15 ms
3678_20101031T233725_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
28 ms
22344_20110608T145342_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
84 ms
2481349355_f423e314d2_jpg_140x100_crop-0%2C0_upscale_q85.jpg
42 ms
9600_20110123T073105_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
48 ms
9459_20110309T192137_0_JPG_140x100_crop-0%2C0_upscale_q85.jpg
52 ms
8487_20101226T152114_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
211 ms
14737_20110226T205912_0_JPG_140x100_crop-0%2C0_upscale_q85.jpg
81 ms
25060_20111113T102035_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
52 ms
21295_20110520T234400_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
82 ms
4714682775_5dde596ddd_b_jpg_140x100_crop-0%2C0_upscale_q85.jpg
376 ms
2403_20110429T093304_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
82 ms
11287_20130118T190930_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
82 ms
13845_20110221T112951_0_JPG_140x100_crop-0%2C0_upscale_q85.jpg
83 ms
11128_20110209T142532_0_jpg_140x100_crop-0%2C0_upscale_q85.jpg
83 ms
jquery.min.js
61 ms
jquery-ui.min.js
94 ms
search_clear_button.png
49 ms
search_button.png
52 ms
libertia_peregrinans_by_megan_hansen_jpg_1024x640_crop-center_upscale_q85.jpg
29 ms
2015-07-11_09.53.07_jpg_570x365_crop-center_upscale_q85.jpg
18 ms
paeonia_suffruticosa_by_james_gaither_jpg_570x365_crop-center_upscale_q85.jpg
30 ms
saruma_henry_by_megan_hansen_jpg_570x365_crop-center_upscale_q85.jpg
40 ms
pachypodium_namaquanum_by_mh_jpg_570x365_crop-center_upscale_q85.jpg
43 ms
rhododendron_teddy_bear_by_MH_jpg_570x365_crop-center_upscale_q85.jpg
55 ms
agave_parryi_jpg_570x365_crop-center_upscale_q85.jpg
58 ms
ga.js
51 ms
cart
420 ms
cart_content
454 ms
__utm.gif
16 ms
collect
56 ms
bugsnag-2.min.js
93 ms
application-85ca3fdf3e312f01fdf38a44c078eebbced5f67faf8d346b293146007500dac6.js
36 ms
application-941e1745db39336c58edfb21d2764ae8b803874a42cd88c4091a504102c5cad8.css
39 ms
meta.json
203 ms
trekkie.buy_now.min.js
72 ms
identify
129 ms
identify
127 ms
plantlust.com 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
button, link, and menuitem elements do not have accessible names.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
plantlust.com 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
plantlust.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 Plantlust.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 Plantlust.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.
plantlust.com
Open Graph description is not detected on the main page of Plant Lust. 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: