2.9 sec in total
54 ms
2.5 sec
378 ms
Welcome to lilypons.com homepage info - get ready to check Lilypons best content for United States right away, or after learning these important things about lilypons.com
the source for water gardening since 1917
Visit lilypons.comWe analyzed Lilypons.com page load time and found that the first response time was 54 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.
lilypons.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value11.1 s
0/100
25%
Value7.1 s
31/100
10%
Value690 ms
43/100
30%
Value0.633
9/100
15%
Value17.4 s
4/100
10%
54 ms
1247 ms
55 ms
114 ms
143 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 27% of them (12 requests) were addressed to the original Lilypons.com, 48% (21 requests) were made to Cdn.lilypons.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Lilypons.com.
Page size can be reduced by 746.0 kB (41%)
1.8 MB
1.1 MB
In fact, the total size of Lilypons.com main page is 1.8 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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 13.6 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 2.2 kB, which is 11% 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 13.6 kB or 70% of the original size.
Potential reduce by 400.4 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. Obviously, Lilypons needs image optimization as it can save up to 400.4 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 255.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 255.7 kB or 68% of the original size.
Potential reduce by 76.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. Lilypons.com needs all CSS files to be minified and compressed as it can save up to 76.2 kB or 83% of the original size.
Number of requests can be reduced by 17 (45%)
38
21
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lilypons. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lilypons.com
54 ms
www.lilypons.com
1247 ms
core.css
55 ms
styles_live.css
114 ms
base-jquery-ui.css
143 ms
head.js
174 ms
n
598 ms
classic-081711.css
8 ms
jquery-17-min.js
223 ms
jquerycycleallmin.js
77 ms
cookie.js
71 ms
all.js
105 ms
aj.js
124 ms
ga.js
32 ms
bg.png
185 ms
dragonfly.png
161 ms
flowers.png
174 ms
btm_flower.png
128 ms
hero5.png
145 ms
hero1.jpg
95 ms
Plum_Crazy_-_Lylipons.JPG
191 ms
promo1.png
210 ms
promo2.png
197 ms
promo3.png
247 ms
1016_700_thumb.jpg
218 ms
1033_730_thumb.jpg
270 ms
970_653_thumb.jpg
270 ms
social_01.png
239 ms
social_02.png
248 ms
social_03.png
338 ms
social_04.png
266 ms
about_logo.png
301 ms
merchant.js
63 ms
arrow.png
260 ms
__utm.gif
16 ms
active_nav_slide.png
226 ms
nav_slide.png
252 ms
pixel
32 ms
ads
231 ms
collect
54 ms
pixel
15 ms
match-result
4 ms
66c39a40007c013264457a163e74bed5.gif
33 ms
ts
154 ms
lilypons.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
[role]s do not have all required [aria-*] attributes
ARIA IDs are not unique
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
[id] attributes on active, focusable elements are not unique
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
No form fields have multiple labels
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>).
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.
lilypons.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lilypons.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilypons.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 Lilypons.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.
lilypons.com
Open Graph description is not detected on the main page of Lilypons. 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: