1.9 sec in total
350 ms
1.5 sec
96 ms
Click here to check amazing Waterlily Pond content. Otherwise, check out these important facts you probably never knew about waterlilypond.com
Waterlily Pond is among the best florists in the San Francisco Bay Area and Napa and Carmel, creating floral art installations and event design for weddings and corporate events.
Visit waterlilypond.comWe analyzed Waterlilypond.com page load time and found that the first response time was 350 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
waterlilypond.com performance score
name
value
score
weighting
Value10.6 s
0/100
10%
Value20.2 s
0/100
25%
Value14.8 s
1/100
10%
Value4,270 ms
1/100
30%
Value0.131
81/100
15%
Value16.6 s
5/100
10%
350 ms
69 ms
269 ms
99 ms
149 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 67% of them (40 requests) were addressed to the original Waterlilypond.com, 18% (11 requests) were made to Use.typekit.net and 5% (3 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (610 ms) belongs to the original domain Waterlilypond.com.
Page size can be reduced by 604.6 kB (31%)
2.0 MB
1.4 MB
In fact, the total size of Waterlilypond.com main page is 2.0 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 13.0 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 13.0 kB or 76% of the original size.
Potential reduce by 33.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. Waterlily Pond images are well optimized though.
Potential reduce by 478.3 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 478.3 kB or 72% of the original size.
Potential reduce by 80.2 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. Waterlilypond.com needs all CSS files to be minified and compressed as it can save up to 80.2 kB or 86% of the original size.
Number of requests can be reduced by 24 (48%)
50
26
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waterlily Pond. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
waterlilypond.com
350 ms
normalize.css
69 ms
style.css
269 ms
jquery.jscrollpane.css
99 ms
mrz1fvt.js
149 ms
sb-instagram.css
98 ms
font-awesome.min.css
9 ms
jquery.js
240 ms
jquery-migrate.min.js
159 ms
js
21 ms
froogaloop2.min.js
17 ms
jquery.easing.1.3.js
161 ms
velocity.min.js
209 ms
imagesloaded.pkgd.min.js
159 ms
jquery.cycle.js
303 ms
jquery.placeholder.js
216 ms
jquery.mousewheel.js
215 ms
jquery.jscrollpane.min.js
278 ms
jQueryRotateCompressed.js
277 ms
custom.js
362 ms
sb-instagram.js
309 ms
count.js
289 ms
waterlilypond.com
183 ms
wp-emoji-release.min.js
98 ms
ajax-loader.gif
80 ms
facebook.png
78 ms
facebook-over.png
79 ms
instagram.png
79 ms
instagram-over.png
78 ms
arrow-left.png
107 ms
arrow-left-over.png
106 ms
arrow-right.png
106 ms
arrow-right-over.png
187 ms
expand-arrow.png
109 ms
expand-arrow-over.png
187 ms
collapse-arrow.png
169 ms
collapse-arrow-over.png
169 ms
home-logo-shadow.png
171 ms
home-logo-top.png
344 ms
home-logo-bottom.png
290 ms
ripples-pink-outer.png
249 ms
ripples-pink-inner.png
248 ms
home-down-pink.png
237 ms
home-down-blue.png
235 ms
ripples-cream.png
330 ms
home-slide-01.jpg
610 ms
ctin.php
158 ms
wOKGbZrT_gctZ9_QuriDc5EtXjSzRHY0zeZy6oIl9j6ff4kNgsMZeMJ6Mk6f5Mw.woff
251 ms
ItZ4gQc4rGWcCK3GvHNcHGUkKszzAdWwVsBXwtREYi3ffHfNgsMZeMJ6Mk6f5MI.woff
338 ms
q8V9r0axSlQFeyHm7YtKNvKBA5SOQDaS0q2FQpnDSkCff4ENgsMZeMJ6Mk6f5Mj.woff
319 ms
fyg5936leW4IHbt9kFBRCeqYcOuaZphUBYWZZqfJRBMff47NgsMZeMJ6Mk6f5MS.woff
265 ms
6px-Lxeu-zkGyxxLmDhtQ-1hcdehTMUe6F53G-PKDCjffOH9gsMZeMJ6Mk6f5MJ.woff
138 ms
5La4S7P1_tVkC9tzs-NTZmsOSQUWoIcC-pFaljqjdgCffwRrggMZeMJ6Mk6f5Mw.woff
164 ms
yCKB3AsOprR7BbvX35U7Nbf67COI_Ma2PUNsPWBC4mSff4hNgsMZeMJ6Mk6f5MX.woff
317 ms
TsTUyC-h-qB1nlQbaFKCoDwpRh0uUG9zX2bK0i3o_xtff4rNgsMZeMJ6Mk6f5gM.woff
323 ms
8_3Rq1lqlU8EjDvAoilvzUuUohkCG4MltNaATZW89Fwff40NgsMZeMJ6Mk6f5gI.woff
419 ms
common.js
20 ms
util.js
44 ms
infowindow.js
41 ms
p.gif
120 ms
waterlilypond.com accessibility score
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
waterlilypond.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
waterlilypond.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 Waterlilypond.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 Waterlilypond.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.
waterlilypond.com
Open Graph description is not detected on the main page of Waterlily Pond. 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: