Tools & Wizards About Us
thriveweddingflowers.com.au screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

thriveweddingflowers.com.au

Buy Beautiful Wedding Flowers in Melbourne | Thrive Flowers

Page Load Speed

9.9 sec in total

First Response

733 ms

Resources Loaded

7.7 sec

Page Rendered

1.6 sec

thriveweddingflowers.com.au screenshot

About Website

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

Find the perfect wedding flowers in Melbourne at Thrive Flowers. Our talented florists specialise in creating stunning floral arrangements.

Visit thriveweddingflowers.com.au

Key Findings

We analyzed Thriveweddingflowers.com.au page load time and found that the first response time was 733 ms and then it took 9.2 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

thriveweddingflowers.com.au performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,320 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

thriveweddingflowers.com.au

733 ms

thriveflowers.com.au

1776 ms

address-form.css

176 ms

style.css

96 ms

woocommerce-layout.css

75 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Thriveweddingflowers.com.au, 86% (124 requests) were made to Thriveflowers.com.au and 6% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Thriveflowers.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 691.4 kB (12%)

Content Size

5.7 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Thriveweddingflowers.com.au main page is 5.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 477.6 kB

  • Original 530.5 kB
  • After minification 524.1 kB
  • After compression 52.9 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 477.6 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 213.7 kB

  • Original 5.2 MB
  • After minification 5.0 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. Thrive Wedding Flowers images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 77 B

  • Original 25.9 kB
  • After minification 25.9 kB
  • After compression 25.8 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.

Requests Breakdown

Number of requests can be reduced by 101 (79%)

Requests Now

128

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thriveweddingflowers.com.au

thriveweddingflowers.com.au

733 ms

thriveflowers.com.au

thriveflowers.com.au

1776 ms

address-form.css

address-form.css

176 ms

style.css

style.css

96 ms

woocommerce-layout.css

woocommerce-layout.css

75 ms

woocommerce.css

woocommerce.css

158 ms

style.css

style.css

161 ms

gateway.css

gateway.css

127 ms

style.min.css

style.min.css

144 ms

theme.min.css

theme.min.css

160 ms

header-footer.min.css

header-footer.min.css

243 ms

elementor-icons.min.css

elementor-icons.min.css

208 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

203 ms

swiper.min.css

swiper.min.css

60 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

51 ms

all.min.css

all.min.css

43 ms

v4-shims.min.css

v4-shims.min.css

51 ms

style.min.css

style.min.css

40 ms

font-awesome.min.css

font-awesome.min.css

90 ms

general.min.css

general.min.css

89 ms

css

css

36 ms

fontawesome.min.css

fontawesome.min.css

93 ms

solid.min.css

solid.min.css

107 ms

brands.min.css

brands.min.css

129 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1696 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

142 ms

wp-polyfill.min.js

wp-polyfill.min.js

1316 ms

hooks.min.js

hooks.min.js

162 ms

w.js

w.js

421 ms

thriveflowers.com.au

thriveflowers.com.au

984 ms

jquery.min.js

jquery.min.js

157 ms

jquery-migrate.min.js

jquery-migrate.min.js

182 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

235 ms

add-to-cart.min.js

add-to-cart.min.js

219 ms

js.cookie.min.js

js.cookie.min.js

246 ms

woocommerce.min.js

woocommerce.min.js

253 ms

v4-shims.min.js

v4-shims.min.js

300 ms

js

js

100 ms

js

js

180 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

305 ms

widget-woocommerce.min.css

widget-woocommerce.min.css

321 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

379 ms

wc-blocks.css

wc-blocks.css

349 ms

photoswipe.min.css

photoswipe.min.css

366 ms

default-skin.min.css

default-skin.min.css

406 ms

sourcebuster.min.js

sourcebuster.min.js

412 ms

order-attribution.min.js

order-attribution.min.js

432 ms

react.min.js

react.min.js

478 ms

deprecated.min.js

deprecated.min.js

453 ms

dom.min.js

dom.min.js

481 ms

react-dom.min.js

react-dom.min.js

516 ms

api.js

api.js

39 ms

escape-html.min.js

escape-html.min.js

541 ms

element.min.js

element.min.js

535 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

555 ms

i18n.min.js

i18n.min.js

1607 ms

keycodes.min.js

keycodes.min.js

553 ms

priority-queue.min.js

priority-queue.min.js

585 ms

compose.min.js

compose.min.js

618 ms

private-apis.min.js

private-apis.min.js

590 ms

redux-routine.min.js

redux-routine.min.js

684 ms

data.min.js

data.min.js

662 ms

lodash.min.js

lodash.min.js

697 ms

wc-blocks-registry.js

wc-blocks-registry.js

713 ms

url.min.js

url.min.js

729 ms

api-fetch.min.js

api-fetch.min.js

740 ms

wc-settings.js

wc-settings.js

773 ms

data-controls.min.js

data-controls.min.js

749 ms

html-entities.min.js

html-entities.min.js

767 ms

notices.min.js

notices.min.js

732 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

757 ms

wc-blocks-data.js

wc-blocks-data.js

778 ms

dom-ready.min.js

dom-ready.min.js

726 ms

a11y.min.js

a11y.min.js

723 ms

primitives.min.js

primitives.min.js

745 ms

warning.min.js

warning.min.js

725 ms

blocks-components.js

blocks-components.js

737 ms

blocks-checkout.js

blocks-checkout.js

724 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

696 ms

button.js

button.js

755 ms

hello-frontend.min.js

hello-frontend.min.js

768 ms

happy-addons.min.js

happy-addons.min.js

714 ms

general.min.js

general.min.js

780 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

778 ms

cart-fragments.min.js

cart-fragments.min.js

771 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

802 ms

webpack.runtime.min.js

webpack.runtime.min.js

749 ms

frontend-modules.min.js

frontend-modules.min.js

841 ms

frontend.min.js

frontend.min.js

778 ms

waypoints.min.js

waypoints.min.js

746 ms

core.min.js

core.min.js

732 ms

frontend.min.js

frontend.min.js

764 ms

elements-handlers.min.js

elements-handlers.min.js

681 ms

jquery.sticky.min.js

jquery.sticky.min.js

688 ms

jquery.zoom.min.js

jquery.zoom.min.js

669 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

675 ms

photoswipe.min.js

photoswipe.min.js

654 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

644 ms

underscore.min.js

underscore.min.js

609 ms

wp-util.min.js

wp-util.min.js

673 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

598 ms

single-product.min.js

single-product.min.js

622 ms

g.gif

g.gif

542 ms

hotjar-2831297.js

hotjar-2831297.js

275 ms

cropped-thrive-1024x292.png

cropped-thrive-1024x292.png

130 ms

thrive-1024x512.png

thrive-1024x512.png

1234 ms

cropped-thrive.png

cropped-thrive.png

212 ms

home-banner-1200x600px-1.png

home-banner-1200x600px-1.png

214 ms

thrive-alyssa-and-rosie.png

thrive-alyssa-and-rosie.png

216 ms

flowers-for-weddings-400x400px.png

flowers-for-weddings-400x400px.png

247 ms

flowers-for-corporate-400x400px.png

flowers-for-corporate-400x400px.png

244 ms

flowers-for-events-400x400px.png

flowers-for-events-400x400px.png

246 ms

Untitled-design-51.png

Untitled-design-51.png

243 ms

Header-Flower-School-1.jpg

Header-Flower-School-1.jpg

429 ms

workshop-3-1-1536x1437-1.jpg

workshop-3-1-1536x1437-1.jpg

423 ms

Women-fixing-flowers.jpg

Women-fixing-flowers.jpg

426 ms

workshop-1.jpg

workshop-1.jpg

425 ms

workshops-2-400x400px.png

workshops-2-400x400px.png

3070 ms

workshop-5-scaled-1.jpg

workshop-5-scaled-1.jpg

2845 ms

3f427c2d-8347-479b-8b3e-f779dfdcfb51.png

3f427c2d-8347-479b-8b3e-f779dfdcfb51.png

462 ms

car.jpg

car.jpg

499 ms

2-1.png

2-1.png

550 ms

1.png

1.png

576 ms

analytics.js

analytics.js

95 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

209 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

211 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

245 ms

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

282 ms

pxiGyp8kv8JHgFVrLPTucHtG.woff

pxiGyp8kv8JHgFVrLPTucHtG.woff

282 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

283 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

282 ms

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

281 ms

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

310 ms

Optima-Pro-Bold.ttf

Optima-Pro-Bold.ttf

1487 ms

Optima-Pro-Medium.ttf

Optima-Pro-Medium.ttf

415 ms

fa-solid-900.woff

fa-solid-900.woff

2248 ms

fa-regular-400.woff

fa-regular-400.woff

646 ms

eicons.woff

eicons.woff

1337 ms

preview-review

preview-review

922 ms

modules.1a47c22b299bcc38a2e7.js

modules.1a47c22b299bcc38a2e7.js

187 ms

fa-brands-400.woff

fa-brands-400.woff

2901 ms

collect

collect

142 ms

admin-ajax.php

admin-ajax.php

2803 ms

thriveflowers.com.au

thriveflowers.com.au

2811 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

99 ms

Accessibility Review

thriveweddingflowers.com.au accessibility score

79

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

<frame> or <iframe> elements do not have a title

Best Practices

thriveweddingflowers.com.au best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

thriveweddingflowers.com.au SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

thriveweddingflowers.com.au

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