3.4 sec in total
659 ms
2.7 sec
69 ms
Click here to check amazing Wholesalewaterlilies content. Otherwise, check out these important facts you probably never knew about wholesalewaterlilies.com
Visit wholesalewaterlilies.comWe analyzed Wholesalewaterlilies.com page load time and found that the first response time was 659 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
wholesalewaterlilies.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value3.9 s
51/100
25%
Value2.1 s
99/100
10%
Value700 ms
42/100
30%
Value0.002
100/100
15%
Value8.3 s
40/100
10%
659 ms
38 ms
35 ms
30 ms
175 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wholesalewaterlilies.com, 48% (34 requests) were made to Static.wixstatic.com and 30% (21 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 429.7 kB (49%)
875.6 kB
445.9 kB
In fact, the total size of Wholesalewaterlilies.com main page is 875.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. 55% of websites need less resources to load. HTML takes 524.4 kB which makes up the majority of the site volume.
Potential reduce by 414.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 414.4 kB or 79% of the original size.
Potential reduce by 12.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. Wholesalewaterlilies images are well optimized though.
Potential reduce by 2.7 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 10 (16%)
61
51
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wholesalewaterlilies. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.wholesalewaterlilies.com
659 ms
minified.js
38 ms
focus-within-polyfill.js
35 ms
polyfill.min.js
30 ms
thunderbolt-commons.67e14581.bundle.min.js
175 ms
main.5ab8d530.bundle.min.js
181 ms
lodash.min.js
202 ms
react.production.min.js
175 ms
react-dom.production.min.js
183 ms
siteTags.bundle.min.js
181 ms
wix-perf-measure.umd.min.js
182 ms
frog.png
365 ms
bundle.min.js
250 ms
nsplsh_7636562d6866786a626f49~mv2_d_6000_4000_s_4_2.jpg
329 ms
3f968e_b5c5eb0a4bb4431a9a9ac628227760c4~mv2.jpg
374 ms
11062b_64647d2fcdaf44b98061f088b5abe16b~mv2.jpeg
277 ms
3f968e_0aa89b11d16e4e1689f24ca38911133f~mv2.jpg
338 ms
nsplsh_636d6262776e2d32496c77~mv2.jpg
596 ms
11062b_84f6f06ea3454032af62423573e0af2c~mv2.jpeg
366 ms
3f968e_351b2c31ec3e4d6392745c35850c5f30~mv2.png
434 ms
3f968e_15fed8a569fd4c82b2696948b7249d85~mv2.jpg
547 ms
nsplsh_784d4f5757704d49713734~mv2_d_3888_2592_s_4_2.jpg
650 ms
3f968e_a64637ce4ea840e9a7b2bed35feba261~mv2.png
580 ms
nsplsh_65414c65654b756d344f34~mv2.jpg
699 ms
nsplsh_66326b5161506d376d7563~mv2_d_6000_4000_s_4_2.jpg
753 ms
3f968e_3ed095cc1f294bbdb1b269f84a1edfa2~mv2.jpg
758 ms
11062b_f998c222e80f49b4a97170ce397ca4f3~mv2.jpeg
810 ms
3f968e_cc4af5247c9c429bb64ee2b37fcab96a~mv2.jpg
855 ms
nsplsh_3b8fddaa91e448af91f4aaa46335b8bc~mv2.jpg
795 ms
nsplsh_c9b0b493cb2a42a79c0314440b98516d~mv2.jpg
981 ms
3f968e_2f100991bed54d24b58ae22cd6faad61~mv2.jpg
1033 ms
nsplsh_11e3a9fef1504edcad9948ab2caa5405~mv2.jpg
1191 ms
3f968e_881b974d8c3941cfb3203f7f13c6465a~mv2.png
1032 ms
nsplsh_667a5a344e4d482d4b544d~mv2_d_3888_2187_s_2.jpg
1035 ms
3f968e_270a54f4cca143cbbe4ed15c49816d2d~mv2.png
1022 ms
nsplsh_d9a2aaa0ba984e148e0be0830ed6ea58~mv2.jpg
1173 ms
3f968e_e6c2e59b55aa4b7a9b2c2557823b1253~mv2.png
1307 ms
nsplsh_21d2db533393434e849b702af26c69d0~mv2.jpg
1330 ms
3f968e_60b83dd839a445a49a9978ac1db68ff9~mv2.jpg
1317 ms
nsplsh_52c16be84b5e4d78a6e6d8226923fe0c~mv2.jpg
1246 ms
nsplsh_6339694a495944706d7967~mv2_d_2448_3264_s_4_2.jpg
1531 ms
3f968e_aee91423d48d487d99e4b4cdc2aa4211~mv2.jpg
1428 ms
32245c07ba3eeb54f3fcaedd3a1c5344.jpg
1377 ms
3f968e_8bbac54bc390421c9a833f7b69ca3b40~mv2.png
1668 ms
nsplsh_415256494a4a47464b6d73~mv2_d_2816_2120_s_2.jpg
1703 ms
frog.png
1504 ms
80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff
36 ms
LuloCleanW05-OneBold.woff
38 ms
aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff
9 ms
9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff
36 ms
e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff
40 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
37 ms
192dac76-a6d9-413d-bb74-22308f2e0cc5.woff
38 ms
0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff
38 ms
cca525a8-ad89-43ae-aced-bcb49fb271dc.woff
38 ms
126 ms
132 ms
128 ms
125 ms
121 ms
125 ms
158 ms
167 ms
168 ms
162 ms
161 ms
166 ms
deprecation-en.v5.html
8 ms
bolt-performance
27 ms
deprecation-style.v5.css
10 ms
right-arrow.svg
7 ms
wholesalewaterlilies.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
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
wholesalewaterlilies.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
Page has valid source maps
wholesalewaterlilies.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wholesalewaterlilies.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 Wholesalewaterlilies.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.
wholesalewaterlilies.com
Open Graph description is not detected on the main page of Wholesalewaterlilies. 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: