Tools & Wizards About Us
lillypadweddings.com.au screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% 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

  • 83

    SEO

    Google-friendlier than
    46% of websites

lillypadweddings.com.au

Flower Delivery Melbourne | Same Day | Melbourne Wedding Florist

Page Load Speed

13 sec in total

First Response

16 ms

Resources Loaded

11 sec

Page Rendered

2 sec

lillypadweddings.com.au screenshot

About Website

Click here to check amazing Lillypad Wedding S content. Otherwise, check out these important facts you probably never knew about lillypadweddings.com.au

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

Visit lillypadweddings.com.au

Key Findings

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

Performance Metrics

lillypadweddings.com.au performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.349

31/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

lillypadweddings.com.au

16 ms

lillypad.com.au

721 ms

www.lillypad.com.au

716 ms

bootstrap.css

31 ms

screen.css

679 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lillypadweddings.com.au, 77% (61 requests) were made to Lillypad.com.au and 15% (12 requests) were made to Scontent-syd2-1.cdninstagram.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Scontent-syd2-1.cdninstagram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 699.1 kB (7%)

Content Size

10.6 MB

After Optimization

9.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lillypadweddings.com.au main page is 10.6 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. 60% of websites need less resources to load. Images take 10.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 114.0 kB

  • Original 141.8 kB
  • After minification 138.3 kB
  • After compression 27.8 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 114.0 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 585.0 kB

  • Original 10.3 MB
  • After minification 9.7 MB

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 Wedding S images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 80 B

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

Requests Breakdown

Number of requests can be reduced by 19 (27%)

Requests Now

70

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lillypad Wedding S. 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 as a result speed up the page load time.

Network Requests Diagram

lillypadweddings.com.au

lillypadweddings.com.au

16 ms

lillypad.com.au

lillypad.com.au

721 ms

www.lillypad.com.au

www.lillypad.com.au

716 ms

bootstrap.css

bootstrap.css

31 ms

screen.css

screen.css

679 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

39 ms

jquery-ui.min.js

jquery-ui.min.js

48 ms

js

js

72 ms

email-decode.min.js

email-decode.min.js

19 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

37 ms

bootstrap.min.js

bootstrap.min.js

48 ms

respond.min.js

respond.min.js

37 ms

jquery.validate.js

jquery.validate.js

43 ms

cart.min.js

cart.min.js

58 ms

gtm.js

gtm.js

74 ms

logo.png

logo.png

64 ms

logo-mobile-2023.jpg

logo-mobile-2023.jpg

64 ms

Expo%20banner.jpg

Expo%20banner.jpg

975 ms

2pio1l5ohf.jpg

2pio1l5ohf.jpg

343 ms

6p39wjsjfl.jpg

6p39wjsjfl.jpg

705 ms

3r4o90m7um.jpg

3r4o90m7um.jpg

268 ms

5ddu1dvex8.jpg

5ddu1dvex8.jpg

284 ms

9j6xnti0gw.jpg

9j6xnti0gw.jpg

317 ms

e1gogkn6hh.jpg

e1gogkn6hh.jpg

985 ms

ro0jnotx1x.jpg

ro0jnotx1x.jpg

547 ms

dgkuriyxbc.jpg

dgkuriyxbc.jpg

719 ms

t4dbte6w8a.jpg

t4dbte6w8a.jpg

1031 ms

c6w9hcj3dh.jpg

c6w9hcj3dh.jpg

1222 ms

itfwekcd6u.jpg

itfwekcd6u.jpg

1413 ms

uqk4ursgb6.jpg

uqk4ursgb6.jpg

1420 ms

cjsvloa4a8.jpg

cjsvloa4a8.jpg

1258 ms

9kmonnutoo.jpg

9kmonnutoo.jpg

1674 ms

tyyc2n4q84.jpg

tyyc2n4q84.jpg

1713 ms

ft022b5nd6.jpg

ft022b5nd6.jpg

1899 ms

86kk3vwred.jpg

86kk3vwred.jpg

1565 ms

5h0gp17vj3.jpg

5h0gp17vj3.jpg

1694 ms

9qrrabrim2.jpg

9qrrabrim2.jpg

2125 ms

zxkbzcgqvj.jpg

zxkbzcgqvj.jpg

1845 ms

1492kvzrop.jpg

1492kvzrop.jpg

2467 ms

tvdzol1lxj.jpg

tvdzol1lxj.jpg

2370 ms

cv56bz07hc.jpg

cv56bz07hc.jpg

2417 ms

2gh844vo8u.jpg

2gh844vo8u.jpg

2538 ms

xyhxp5w24o.jpg

xyhxp5w24o.jpg

2181 ms

dk16h7hw1q.jpg

dk16h7hw1q.jpg

2831 ms

ptumjf0jpv.jpg

ptumjf0jpv.jpg

2452 ms

3ho3qywwt0.jpg

3ho3qywwt0.jpg

3040 ms

rim0o0t7n2.jpg

rim0o0t7n2.jpg

3118 ms

z04cda7ufd.jpg

z04cda7ufd.jpg

3145 ms

qieme96bxs.jpg

qieme96bxs.jpg

2735 ms

xl5u9eomgp.jpg

xl5u9eomgp.jpg

3219 ms

soupv0wtbt.jpg

soupv0wtbt.jpg

2942 ms

ka5kkdq2zt.jpg

ka5kkdq2zt.jpg

3511 ms

vu8t3dd4sl.jpg

vu8t3dd4sl.jpg

3632 ms

ga.js

ga.js

18 ms

__utm.gif

__utm.gif

12 ms

Mulish-Light.woff

Mulish-Light.woff

2794 ms

Mulish-ExtraLight.woff

Mulish-ExtraLight.woff

3663 ms

Mulish-Regular.woff

Mulish-Regular.woff

3742 ms

Mulish-Medium.woff

Mulish-Medium.woff

3722 ms

Mulish-SemiBold.woff

Mulish-SemiBold.woff

2688 ms

PlayfairDisplay-Regular.woff

PlayfairDisplay-Regular.woff

3315 ms

instagram.txt

instagram.txt

3090 ms

gjhpttf8om.jpg

gjhpttf8om.jpg

3433 ms

722tu5e3h0.jpg

722tu5e3h0.jpg

3495 ms

Happy%20Wedding%20instagram%20post.png.jpg

Happy%20Wedding%20instagram%20post.png.jpg

2749 ms

main.js

main.js

272 ms

459325587_18455972269041141_5112150481138252929_n.jpg

459325587_18455972269041141_5112150481138252929_n.jpg

2487 ms

459432951_18455965216041141_8505413613884425366_n.jpg

459432951_18455965216041141_8505413613884425366_n.jpg

2868 ms

460093216_18455969446041141_4760254784666470308_n.jpg

460093216_18455969446041141_4760254784666470308_n.jpg

3477 ms

459320472_18455968633041141_7741773252860381644_n.jpg

459320472_18455968633041141_7741773252860381644_n.jpg

4673 ms

459453243_18455822839041141_8429803672136466739_n.jpg

459453243_18455822839041141_8429803672136466739_n.jpg

4967 ms

458733952_1033876645081478_4215810766766776599_n.jpg

458733952_1033876645081478_4215810766766776599_n.jpg

4859 ms

458709265_2292592641090241_3537178232357749453_n.jpg

458709265_2292592641090241_3537178232357749453_n.jpg

4668 ms

458504374_1640229403214894_5561015238419561215_n.jpg

458504374_1640229403214894_5561015238419561215_n.jpg

5031 ms

458500326_452986291056011_646421383445247694_n.jpg

458500326_452986291056011_646421383445247694_n.jpg

3764 ms

458403480_7682753625162817_3016597089237755349_n.jpg

458403480_7682753625162817_3016597089237755349_n.jpg

4072 ms

458522141_443643677991995_3662140186282564841_n.jpg

458522141_443643677991995_3662140186282564841_n.jpg

4485 ms

458185299_1254020509121071_3183944186350351409_n.jpg

458185299_1254020509121071_3183944186350351409_n.jpg

4892 ms

printcss.css

printcss.css

253 ms

Accessibility Review

lillypadweddings.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

lillypadweddings.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

lillypadweddings.com.au SEO score

83

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 Lillypadweddings.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 Lillypadweddings.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

lillypadweddings.com.au

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