3.3 sec in total
402 ms
2.3 sec
618 ms
Click here to check amazing LilyBLOOMS content. Otherwise, check out these important facts you probably never knew about lilyblooms.com
Pond plants shipped directly from the grower! Hardy and Tropical Water Lilies and Bog Plants, Tropical Bog Plants, Submerged Plants, Pond Supplies, Tadpoles, Japanese Trapdoor Pond Snails
Visit lilyblooms.comWe analyzed Lilyblooms.com page load time and found that the first response time was 402 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
lilyblooms.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value9.9 s
0/100
25%
Value11.5 s
5/100
10%
Value19,300 ms
0/100
30%
Value0.181
67/100
15%
Value25.4 s
0/100
10%
402 ms
178 ms
199 ms
197 ms
172 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Lilyblooms.com, 42% (39 requests) were made to Cdn5.bigcommerce.com and 36% (33 requests) were made to Cdn6.bigcommerce.com. The less responsive or slowest element that took the longest time to load (749 ms) relates to the external source Cdn5.bigcommerce.com.
Page size can be reduced by 860.7 kB (39%)
2.2 MB
1.4 MB
In fact, the total size of Lilyblooms.com main page is 2.2 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 62.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. 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 62.4 kB or 81% of the original size.
Potential reduce by 21.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. LilyBLOOMS images are well optimized though.
Potential reduce by 460.9 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 460.9 kB or 70% of the original size.
Potential reduce by 315.5 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. Lilyblooms.com needs all CSS files to be minified and compressed as it can save up to 315.5 kB or 82% of the original size.
Number of requests can be reduced by 50 (58%)
86
36
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LilyBLOOMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.lilyblooms.com
402 ms
css
178 ms
css
199 ms
css
197 ms
styles.css
172 ms
styles.css
312 ms
iselector.css
189 ms
flexslider.css
178 ms
slide-show.css
251 ms
styles-slide-show.css
435 ms
social.css
178 ms
white.css
237 ms
theme.css
390 ms
product.attributes.css
191 ms
ui.all.css
195 ms
product.quickview.css
282 ms
store.css
239 ms
imodal.css
749 ms
jquery.min.js
161 ms
menudrop.js
175 ms
common.js
224 ms
iselector.js
183 ms
jquery.flexslider.js
185 ms
viewport.js
184 ms
jquery.autobox.js
241 ms
init.js
215 ms
imagesLoaded.js
255 ms
jquery-ui.min.js
250 ms
jquery.validate.js
252 ms
product.functions.js
253 ms
product.attributes.js
255 ms
quickview.js
258 ms
quickview.initialise.js
259 ms
jquery.form.js
284 ms
imodal.js
487 ms
quicksearch.js
286 ms
bc_pinstrumentation.min.js
314 ms
jquery.bgiframe.min.js
308 ms
superfish.js
308 ms
visitor.js
309 ms
css
14 ms
beacon_api.js
21 ms
analytics.min.js
19 ms
ajax-loader.gif
161 ms
plantcollage.jpg
131 ms
Search.gif
17 ms
pdlogoblank.gif
129 ms
bp3.gif
42 ms
pondsuppliescheapsm.gif
47 ms
pond-plants-r-us-sm.gif
239 ms
logo_1481218073__47465.png
41 ms
banner.jpg
45 ms
SALE.jpg
44 ms
Purple_Fantasy.jpg
44 ms
Dalen_Pond_Cover__51712.1448999573.220.290.jpg
263 ms
IcoRating0.gif
126 ms
snow-princess__75673.1470172157.220.290.jpg
127 ms
Dalen_Solar_Owl__63303.1423767058.220.290.jpg
126 ms
IcoRating5.gif
126 ms
Microbe_lift_Autumn_Winter_Prep__12992.1423685450.220.290.png
186 ms
1__64227.1502194932.220.290.jpg
185 ms
Attraction_Lily__32150.1421338362.220.290.jpg
217 ms
IcoRating4.gif
186 ms
Highland_Rim_Fertilizer_300_count__11676.1423679156.220.290.jpg
183 ms
Dewitt_Deluxe_Netting__33670.1423769201.220.290.jpg
187 ms
Mermaidweed__94718.1422476151.386.513.jpg
41 ms
Rosette_Water_Lettuce__49743.1446578985.1280.1280.jpg
38 ms
Pond_Snails__61837.1443198305.1280.1280.jpg
41 ms
Wanvisa__02254.1422462945.1280.1280.jpg
43 ms
Tanzanite__33545.1447106286.1280.1280.jpg
38 ms
UnsortedWhiteLily__80954.1421342845.1280.1280.jpg
125 ms
water-lily-background.jpg
217 ms
WJ6D195CfbTRlIs49IbkFw.woff
140 ms
qMLNvuP8jIE
211 ms
w68clGaCSpI
408 ms
fornax.min.js
116 ms
hero_prev.gif
147 ms
hero_next.gif
145 ms
sprite-social.png
148 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
84 ms
index.php
112 ms
icon-eye-open.png
68 ms
arrows-ffffff.png
36 ms
www-player-vflMqr8uC.css
11 ms
www-embed-player.js
24 ms
base.js
33 ms
id
164 ms
8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js
164 ms
ad_status.js
172 ms
logo_ringo-vflOpz8ZI.png
154 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
25 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
25 ms
lilyblooms.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
lilyblooms.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
lilyblooms.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilyblooms.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 Lilyblooms.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.
lilyblooms.com
Open Graph description is not detected on the main page of LilyBLOOMS. 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: