Tools & Wizards About Us

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

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

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

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: