Tools & Wizards About Us
luvinlife.com.au screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

luvinlife.com.au

Luvin Life – Opening Soon

Page Load Speed

3.6 sec in total

First Response

531 ms

Resources Loaded

2.3 sec

Page Rendered

762 ms

luvinlife.com.au screenshot

About Website

Visit luvinlife.com.au now to see the best up-to-date Luvin Life content and also check out these interesting facts you probably never knew about luvinlife.com.au

Luvin Life | Products with Purpose

Visit luvinlife.com.au

Key Findings

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

Performance Metrics

luvinlife.com.au performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

www.luvinlife.com.au

531 ms

theme.css

38 ms

jquery.min.js

67 ms

vendor.min.js

66 ms

s3340b1d9cf54.js

47 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 78% of them (31 requests) were addressed to the original Luvinlife.com.au, 15% (6 requests) were made to Cdn.shopify.com and 5% (2 requests) were made to Cdn.judge.me. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Luvinlife.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.7 kB (13%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 273.4 kB

  • Original 329.3 kB
  • After minification 324.2 kB
  • After compression 55.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 273.4 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 38.1 kB

  • Original 1.9 MB
  • After minification 1.9 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. Luvin Life images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 149 B

  • Original 166.8 kB
  • After minification 166.8 kB
  • After compression 166.6 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 89 B

  • Original 25.1 kB
  • After minification 25.1 kB
  • After compression 25.0 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. Luvinlife.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (58%)

Requests Now

31

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.luvinlife.com.au

www.luvinlife.com.au

531 ms

theme.css

theme.css

38 ms

jquery.min.js

jquery.min.js

67 ms

vendor.min.js

vendor.min.js

66 ms

s3340b1d9cf54.js

s3340b1d9cf54.js

47 ms

ccf2dff1a1a65.css

ccf2dff1a1a65.css

89 ms

font.js

font.js

71 ms

font.css

font.css

74 ms

avada-aem-popup.js

avada-aem-popup.js

72 ms

avada-aem-push.js

avada-aem-push.js

75 ms

shopify-perf-kit-1.0.0.min.js

shopify-perf-kit-1.0.0.min.js

47 ms

option_selection-86cdd286ddf3be7e25d68b9fc5965d7798a3ff6228ff79af67b3f4e41d6a34be.js

option_selection-86cdd286ddf3be7e25d68b9fc5965d7798a3ff6228ff79af67b3f4e41d6a34be.js

45 ms

stellar.js

stellar.js

45 ms

wow.min.js

wow.min.js

61 ms

theme.min.js

theme.min.js

68 ms

script-loader.js

script-loader.js

76 ms

trekkie.storefront.191ee957437379e11b4b5a983ae36024546a469d.min.js

trekkie.storefront.191ee957437379e11b4b5a983ae36024546a469d.min.js

386 ms

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

385 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

384 ms

loader.js

loader.js

221 ms

WEB-LL-logo-est-2003-EUCALYPTUS_200x.png

WEB-LL-logo-est-2003-EUCALYPTUS_200x.png

86 ms

spacer.png

spacer.png

318 ms

Artboard_8_0.5x-50_100x.jpg

Artboard_8_0.5x-50_100x.jpg

163 ms

Artboard_3_0.5x-50_100x.jpg

Artboard_3_0.5x-50_100x.jpg

163 ms

LLArtboard_2_100x.png

LLArtboard_2_100x.png

531 ms

0B8A2646_100x.jpg

0B8A2646_100x.jpg

161 ms

roboto_n4.a512c7b68cd7f12c72e1a5fd58e7f7315c552e93.woff

roboto_n4.a512c7b68cd7f12c72e1a5fd58e7f7315c552e93.woff

59 ms

roboto_n3.fa321b1ddee0338f7cf3bfb01c364bbc1b6a419a.woff

roboto_n3.fa321b1ddee0338f7cf3bfb01c364bbc1b6a419a.woff

150 ms

roboto_n7.1babbb6a27f91b14216bafa40bf222e08f6999f4.woff

roboto_n7.1babbb6a27f91b14216bafa40bf222e08f6999f4.woff

59 ms

adorn-icons.woff

adorn-icons.woff

58 ms

oswald_n7.2767cc6e7cfc91284caa2c06eb07eca21a27681e.woff

oswald_n7.2767cc6e7cfc91284caa2c06eb07eca21a27681e.woff

151 ms

oswald_n6.1f460fc9ad98670d0370772496961d620bdca9f0.woff

oswald_n6.1f460fc9ad98670d0370772496961d620bdca9f0.woff

153 ms

oswald_n3.9274b221a436d59cfed6e5cac51271ed4d148199.woff

oswald_n3.9274b221a436d59cfed6e5cac51271ed4d148199.woff

150 ms

8AAngBY2BkYGDgA2IJBhBgAvKZGViBJAuYxwAABJsAOgAAeAFjYGBgZACCk535hiD60tn0azAaAEqpB6wAAA==

8AAngBY2BkYGDgA2IJBhBgAvKZGViBJAuYxwAABJsAOgAAeAFjYGBgZACCk535hiD60tn0azAaAEqpB6wAAA==

14 ms

base.css

base.css

92 ms

LLArtboard_3_1728x.png

LLArtboard_3_1728x.png

877 ms

Artboard_1_0.5x-50.jpg

Artboard_1_0.5x-50.jpg

1067 ms

Artboard_2_0.5x-50_550x.jpg

Artboard_2_0.5x-50_550x.jpg

1004 ms

Peppermint_web_550x.jpg

Peppermint_web_550x.jpg

360 ms

Lifestyle4_550x.png

Lifestyle4_550x.png

758 ms

Accessibility Review

luvinlife.com.au accessibility score

81

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

High

Links do not have a discernible name

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

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

luvinlife.com.au SEO score

75

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

luvinlife.com.au

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