1.8 sec in total
114 ms
1.3 sec
400 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 114 ms and then it took 1.7 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.
lilyblooms.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.7 s
57/100
25%
Value4.0 s
81/100
10%
Value290 ms
80/100
30%
Value0.058
98/100
15%
Value7.7 s
46/100
10%
114 ms
77 ms
538 ms
115 ms
92 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Lilyblooms.com, 71% (42 requests) were made to Cdn11.bigcommerce.com and 5% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (538 ms) belongs to the original domain Lilyblooms.com.
Page size can be reduced by 375.3 kB (15%)
2.5 MB
2.1 MB
In fact, the total size of Lilyblooms.com main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 374.5 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 72.2 kB, which is 18% 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 374.5 kB or 93% of the original size.
Potential reduce by 0 B
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 785 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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 has all CSS files already compressed.
Number of requests can be reduced by 15 (29%)
52
37
The browser has sent 52 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 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lilyblooms.com
114 ms
lilyblooms.com
77 ms
www.lilyblooms.com
538 ms
theme-bundle.polyfills.js
115 ms
theme-bundle.head_async.js
92 ms
webfont.js
61 ms
css
117 ms
theme-e2022630-e88e-013c-8559-7a40a4d12694.css
93 ms
vault-e2022630-e88e-013c-8559-7a40a4d12694.css
107 ms
custom-e2022630-e88e-013c-8559-7a40a4d12694.css
154 ms
google_analytics4-9a468da7c21d2e9e41cd445d567f3f3a5a9b6759.js
93 ms
loader.js
114 ms
index.js
116 ms
jquery-3.5.1.min.js
95 ms
all.css
193 ms
jquery-ui.min.js
95 ms
theme-bundle.main.js
227 ms
csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js
226 ms
visitor_stencil.js
189 ms
1.js
61 ms
logo_1481218073__47465.original.png
183 ms
Lemon_Meringue_20190331_113736__02259.1703480940.jpg
183 ms
Sunfire_-_DSC01750__20639.1703479031.jpg
184 ms
Citrus_Twist_copy__90954.1702614589.jpg
184 ms
Pin_Waree_LB_PXL_20220406_163627656__97461.1678918745.jpg
183 ms
Ceratophyllum_01-20-04_188_watermark_copy__45108.1698682403.jpg
183 ms
Clyde_Ikins_PXL_20240403_184223961__53507.1712549146.jpg
185 ms
Texas_Dawn__43719.1676917531.jpg
186 ms
Virginalis2__71533.1676924226.jpg
184 ms
Black_Princess_08-09-08_045__33374.1711683058.jpg
185 ms
Trapdoor_snail_copy__01775.1711119188.jpg
186 ms
Water_Hyacinth__01177.1421269411.jpg
184 ms
Limnobium_spongia_10-16_03_022__64145.1704815047.jpg
186 ms
Rosette_Water_Lettuce__49743.1446578985.jpg
185 ms
Golden_Creeping_Jenny_1__82479.1676842155.jpg
186 ms
LemonBacopa__06854.1700023250.jpg
187 ms
Aeschnomene_fluitans_IMG_20200806_122007_copy__01352.1702960285.jpg
187 ms
BulkFertilizer__52174.1446581853.gif
187 ms
Water_Poppy__52695.1422461432.jpg
188 ms
Pickerel_Rush_2__75173.1421862847.jpg
188 ms
PlantingBagMd__41777.1423755784.gif
188 ms
Gunnera_PXL_20230824_201751232__01938.1716699868.jpg
188 ms
Night_Day__25686.1716262743.jpg
190 ms
Phyllanthus_PXL_20220916_203007012__86395.1714188643.jpg
189 ms
Nasturtium_officinale_Purple_PXL_20240407_203533953__65993.1713070334.jpg
189 ms
Pontederia_dilatata_royal_pickerel_PXL_20230720_190006661__91530.1712974974.jpg
190 ms
Puttaraska_Fragrance_and_Fortune_PXL_20231012_212654078__08510.1712966503.jpg
190 ms
Izia_PXL_20230701_171821149__53229.1712900214.jpg
191 ms
Moon_Dance_PXL_20240403_183721128__79699.1712636154.jpg
193 ms
Asclepias_curassavica_20220830_111042__88808.1709096336.jpg
190 ms
ProductDefault.gif
192 ms
Canna_Chiquita_Punch__07879.1703649713.jpg
191 ms
Anemopsis_californica__03308.1703644869.jpg
190 ms
index.php
147 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
147 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
148 ms
fa-solid-900.woff
125 ms
fa-regular-400.woff
147 ms
nobot
61 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-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
Image elements do not have [alt] attributes
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
Browser errors were logged to the console
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
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
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: