Tools & Wizards About Us
m3.life screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

m3.life

Botanical Skincare CBD | Organic Wellness | Terpene Rich Skincare Products - M3

Page Load Speed

2 sec in total

First Response

80 ms

Resources Loaded

1.9 sec

Page Rendered

58 ms

m3.life screenshot

About Website

Visit m3.life now to see the best up-to-date M3 content and also check out these interesting facts you probably never knew about m3.life

You can count on our cbd range for botanical skin care and organic wellness products which terpine rich. Check out now.

Visit m3.life

Key Findings

We analyzed M3.life page load time and found that the first response time was 80 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

m3.life performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value3,280 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value29.5 s

0/100

10%

Network Requests Diagram

www.m3.life

80 ms

minified.js

46 ms

focus-within-polyfill.js

43 ms

polyfill.min.js

1019 ms

mobile-app-invite-banner.css

43 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original M3.life, 43% (17 requests) were made to Static.parastorage.com and 30% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (67%)

Content Size

1.7 MB

After Optimization

564.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M3.life main page is 1.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. 30% of websites need less resources to load. HTML takes 973.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 789.2 kB

  • Original 973.4 kB
  • After minification 971.6 kB
  • After compression 184.2 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 789.2 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 3.3 kB

  • Original 85.0 kB
  • After minification 81.7 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. M3 images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 329.7 kB

  • Original 626.5 kB
  • After minification 626.5 kB
  • After compression 296.7 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 329.7 kB or 53% of the original size.

CSS Optimization

-4%

Potential reduce by 56 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 1.3 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. M3.life has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (46%)

Requests Now

24

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.m3.life

www.m3.life

80 ms

minified.js

minified.js

46 ms

focus-within-polyfill.js

focus-within-polyfill.js

43 ms

polyfill.min.js

polyfill.min.js

1019 ms

mobile-app-invite-banner.css

mobile-app-invite-banner.css

43 ms

mobile-app-invite-banner.umd.min.js

mobile-app-invite-banner.umd.min.js

75 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

thunderbolt-commons.c1d8ed1c.bundle.min.js

49 ms

main.4a2d1e74.bundle.min.js

main.4a2d1e74.bundle.min.js

50 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

47 ms

lodash.min.js

lodash.min.js

50 ms

react.production.min.js

react.production.min.js

51 ms

react-dom.production.min.js

react-dom.production.min.js

51 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

51 ms

4a5117_44b7f23f38e14b5ca921d6c31cb54450~mv2.png

4a5117_44b7f23f38e14b5ca921d6c31cb54450~mv2.png

225 ms

4a5117_aa63cc6a1e564098b17261740ffdde29~mv2.png

4a5117_aa63cc6a1e564098b17261740ffdde29~mv2.png

428 ms

Herbalist.jpg

Herbalist.jpg

539 ms

Puressence%20face%20serum-4_v2_edited_edited.jpg

Puressence%20face%20serum-4_v2_edited_edited.jpg

437 ms

4a5117_33eb58bfd529465195c3220f635f9dfe~mv2.png

4a5117_33eb58bfd529465195c3220f635f9dfe~mv2.png

384 ms

4a5117_3bc9cffab1564b88a06aeab1cca4ad8a~mv2.jpg

4a5117_3bc9cffab1564b88a06aeab1cca4ad8a~mv2.jpg

405 ms

4a5117_39527ef5266142719bc2558f9120a61f~mv2.png

4a5117_39527ef5266142719bc2558f9120a61f~mv2.png

516 ms

bundle.min.js

bundle.min.js

61 ms

FD_Udbezj8EHXbdsqLUplxa1RVmPjeKy21_GQJaLlJI.woff

FD_Udbezj8EHXbdsqLUplxa1RVmPjeKy21_GQJaLlJI.woff

36 ms

u_mYNr_qYP37m7vgvmIYZxa1RVmPjeKy21_GQJaLlJI.woff

u_mYNr_qYP37m7vgvmIYZxa1RVmPjeKy21_GQJaLlJI.woff

36 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

35 ms

104 ms

99 ms

102 ms

101 ms

102 ms

102 ms

141 ms

135 ms

135 ms

135 ms

137 ms

135 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

12 ms

deprecation-style.v5.css

deprecation-style.v5.css

11 ms

right-arrow.svg

right-arrow.svg

7 ms

Accessibility Review

m3.life accessibility score

88

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

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.

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

m3.life best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

m3.life SEO score

90

Search Engine Optimization Advices

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 doesn't use 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 M3.life 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 M3.life 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

m3.life

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