Tools & Wizards About Us
flowerhq.com.au screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

flowerhq.com.au

Flower HQ | Wholesale Flower Market

Page Load Speed

3.9 sec in total

First Response

669 ms

Resources Loaded

2.6 sec

Page Rendered

629 ms

flowerhq.com.au screenshot

About Website

Click here to check amazing Flower HQ content. Otherwise, check out these important facts you probably never knew about flowerhq.com.au

Your smarter wholesale flowers supplier. The best value fresh wholesale flowers for florists.

Visit flowerhq.com.au

Key Findings

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

Performance Metrics

flowerhq.com.au performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

flowerhq.com.au

669 ms

theme.scss.css

633 ms

fhq-landing.min.css

1030 ms

font-awesome.min.css

47 ms

teal-flower-graphic.png

628 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 82% of them (18 requests) were addressed to the original Flowerhq.com.au, 9% (2 requests) were made to Cdn.shopify.com and 5% (1 request) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Flowerhq.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.2 kB (29%)

Content Size

1.1 MB

After Optimization

776.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 22.1 kB

  • Original 27.1 kB
  • After minification 22.8 kB
  • After compression 5.0 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 4.3 kB, which is 16% 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 22.1 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 21.9 kB

  • Original 675.3 kB
  • After minification 653.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. Flower HQ images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 123.4 kB

  • Original 215.2 kB
  • After minification 215.2 kB
  • After compression 91.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 123.4 kB or 57% of the original size.

CSS Optimization

-85%

Potential reduce by 151.9 kB

  • Original 178.1 kB
  • After minification 177.9 kB
  • After compression 26.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. Flowerhq.com.au needs all CSS files to be minified and compressed as it can save up to 151.9 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flower HQ. According to our analytics all requests are already optimized.

Network Requests Diagram

flowerhq.com.au

flowerhq.com.au

669 ms

theme.scss.css

theme.scss.css

633 ms

fhq-landing.min.css

fhq-landing.min.css

1030 ms

font-awesome.min.css

font-awesome.min.css

47 ms

teal-flower-graphic.png

teal-flower-graphic.png

628 ms

sydney-map.jpg

sydney-map.jpg

635 ms

newcastle-map.jpg

newcastle-map.jpg

627 ms

vendor.min.js

vendor.min.js

937 ms

theme.min.js

theme.min.js

651 ms

canberra-map.jpg

canberra-map.jpg

656 ms

brisbane-map.jpg

brisbane-map.jpg

686 ms

adelaide-map.jpg

adelaide-map.jpg

664 ms

jquery.min.js

jquery.min.js

85 ms

menu-icon.png

menu-icon.png

234 ms

flower-hq-logo.png

flower-hq-logo.png

222 ms

hero-shot.jpg

hero-shot.jpg

1047 ms

BreakersSlab-Bold.woff

BreakersSlab-Bold.woff

235 ms

BreakersSlab-Regular.woff

BreakersSlab-Regular.woff

230 ms

BreakersSlab-Light.woff

BreakersSlab-Light.woff

215 ms

BreakersSlab-Thin.woff

BreakersSlab-Thin.woff

376 ms

ajax-loader.gif

ajax-loader.gif

17 ms

ajax-loader.gif

ajax-loader.gif

215 ms

Accessibility Review

flowerhq.com.au accessibility score

90

Accessibility Issues

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

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

Image elements do not have [alt] attributes

Best Practices

flowerhq.com.au best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

flowerhq.com.au SEO score

89

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

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

flowerhq.com.au

Open Graph description is not detected on the main page of Flower HQ. 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: