Tools & Wizards About Us
lillypad.com.au screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

lillypad.com.au

Flower Delivery Melbourne | Same Day | Melbourne Wedding Florist

Page Load Speed

8.1 sec in total

First Response

247 ms

Resources Loaded

7.3 sec

Page Rendered

543 ms

lillypad.com.au screenshot

About Website

Visit lillypad.com.au now to see the best up-to-date Lillypad content and also check out these interesting facts you probably never knew about lillypad.com.au

Same day Flower Delivery Melbourne. Fun, fresh floral arrangements. Afterpay available. Trusted Melbourne wedding florist. Affordable to luxe Melbourne flowers.

Visit lillypad.com.au

Key Findings

We analyzed Lillypad.com.au page load time and found that the first response time was 247 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

lillypad.com.au performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

lillypad.com.au

247 ms

www.lillypad.com.au

744 ms

bootstrap.css

21 ms

screen.css

300 ms

jquery-1.10.2.min.js

376 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 78% of them (45 requests) were addressed to the original Lillypad.com.au, 5% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Lillypad.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.0 kB (9%)

Content Size

802.6 kB

After Optimization

727.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lillypad.com.au main page is 802.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. 50% of websites need less resources to load. Images take 496.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 73.7 kB

  • Original 97.3 kB
  • After minification 97.2 kB
  • After compression 23.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. 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 73.7 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 496.9 kB
  • After minification 496.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. Lillypad images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.3 kB

  • Original 176.3 kB
  • After minification 176.2 kB
  • After compression 175.0 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.

CSS Optimization

-0%

Potential reduce by 3 B

  • Original 32.1 kB
  • After minification 32.1 kB
  • After compression 32.1 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. Lillypad.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (30%)

Requests Now

50

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lillypad. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

lillypad.com.au

lillypad.com.au

247 ms

www.lillypad.com.au

www.lillypad.com.au

744 ms

bootstrap.css

bootstrap.css

21 ms

screen.css

screen.css

300 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

376 ms

jquery-ui.min.js

jquery-ui.min.js

1179 ms

js

js

86 ms

email-decode.min.js

email-decode.min.js

34 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

45 ms

bootstrap.min.js

bootstrap.min.js

939 ms

respond.min.js

respond.min.js

357 ms

jquery.validate.js

jquery.validate.js

944 ms

cart.min.js

cart.min.js

1199 ms

platform.js

platform.js

56 ms

gtm.js

gtm.js

67 ms

logo.png

logo.png

920 ms

logo-mobile-2023.jpg

logo-mobile-2023.jpg

56 ms

wedding-banner-2022.jpg

wedding-banner-2022.jpg

489 ms

2pio1l5ohf.jpg

2pio1l5ohf.jpg

1384 ms

6p39wjsjfl.jpg

6p39wjsjfl.jpg

1470 ms

3r4o90m7um.jpg

3r4o90m7um.jpg

918 ms

5ddu1dvex8.jpg

5ddu1dvex8.jpg

1676 ms

9j6xnti0gw.jpg

9j6xnti0gw.jpg

1741 ms

e1gogkn6hh.jpg

e1gogkn6hh.jpg

1127 ms

ro0jnotx1x.jpg

ro0jnotx1x.jpg

1774 ms

t4dbte6w8a.jpg

t4dbte6w8a.jpg

2029 ms

itfwekcd6u.jpg

itfwekcd6u.jpg

1400 ms

uqk4ursgb6.jpg

uqk4ursgb6.jpg

2296 ms

fluenp0ugy.jpg

fluenp0ugy.jpg

2371 ms

ft022b5nd6.jpg

ft022b5nd6.jpg

2575 ms

cjsvloa4a8.jpg

cjsvloa4a8.jpg

2638 ms

tyyc2n4q84.jpg

tyyc2n4q84.jpg

2693 ms

9kmonnutoo.jpg

9kmonnutoo.jpg

2928 ms

zxkbzcgqvj.jpg

zxkbzcgqvj.jpg

3196 ms

86kk3vwred.jpg

86kk3vwred.jpg

3284 ms

tvdzol1lxj.jpg

tvdzol1lxj.jpg

3481 ms

cv56bz07hc.jpg

cv56bz07hc.jpg

3544 ms

ptumjf0jpv.jpg

ptumjf0jpv.jpg

3577 ms

dk16h7hw1q.jpg

dk16h7hw1q.jpg

2941 ms

rim0o0t7n2.jpg

rim0o0t7n2.jpg

3915 ms

3ho3qywwt0.jpg

3ho3qywwt0.jpg

4103 ms

88 ms

Mulish-Light.woff

Mulish-Light.woff

3658 ms

Mulish-ExtraLight.woff

Mulish-ExtraLight.woff

4542 ms

Mulish-Regular.woff

Mulish-Regular.woff

4565 ms

Mulish-Medium.woff

Mulish-Medium.woff

3932 ms

Mulish-SemiBold.woff

Mulish-SemiBold.woff

4750 ms

PlayfairDisplay-Regular.woff

PlayfairDisplay-Regular.woff

5526 ms

js

js

53 ms

analytics.js

analytics.js

25 ms

80 ms

collect

collect

54 ms

collect

collect

30 ms

ga-audiences

ga-audiences

21 ms

ga.js

ga.js

21 ms

__utm.gif

__utm.gif

12 ms

main.js

main.js

8 ms

printcss.css

printcss.css

269 ms

Accessibility Review

lillypad.com.au accessibility score

80

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

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

High

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

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lillypad.com.au best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lillypad.com.au SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lillypad.com.au 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 Lillypad.com.au 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.

Social Sharing Optimization

lillypad.com.au

Open Graph data is detected on the main page of Lillypad. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: