Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

lavenderhouse.com.au

Specialty Lavender Products | Lavender House - Tasmania

Page Load Speed

18.9 sec in total

First Response

1.1 sec

Resources Loaded

17.3 sec

Page Rendered

509 ms

lavenderhouse.com.au screenshot

About Website

Welcome to lavenderhouse.com.au homepage info - get ready to check Lavender House best content right away, or after learning these important things about lavenderhouse.com.au

best sellers Stimulate your senses Visit Lavender House today! About Uslavender houseLavender House is nestled in the beautiful Tamar River Valley at Rowella, 38 kilometres from Launceston on the Tama...

Visit lavenderhouse.com.au

Key Findings

We analyzed Lavenderhouse.com.au page load time and found that the first response time was 1.1 sec and then it took 17.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

lavenderhouse.com.au performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

lavenderhouse.com.au

1101 ms

1e49dc5814dec760df7f1247f52e81c2.css

1017 ms

iyn4kwi.css

71 ms

pinit.js

27 ms

p.css

21 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 44% of them (20 requests) were addressed to the original Lavenderhouse.com.au, 49% (22 requests) were made to Use.typekit.net and 4% (2 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Lavenderhouse.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.6 kB (8%)

Content Size

3.6 MB

After Optimization

3.3 MB

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

HTML Optimization

-82%

Potential reduce by 135.8 kB

  • Original 165.9 kB
  • After minification 165.6 kB
  • After compression 30.1 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 135.8 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 162.3 kB

  • Original 3.3 MB
  • After minification 3.2 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. Lavender House images are well optimized though.

CSS Optimization

-1%

Potential reduce by 1.5 kB

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

Requests Breakdown

We found no issues to fix!

Requests Now

21

After Optimization

21

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

Accessibility Review

lavenderhouse.com.au accessibility score

97

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

Links do not have a discernible name

Best Practices

lavenderhouse.com.au best practices score

92

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

Page has valid source maps

SEO Factors

lavenderhouse.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 Lavenderhouse.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 Lavenderhouse.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 Lavender House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: