Tools & Wizards About Us
getsweetreleaf.com screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

getsweetreleaf.com

Get Sweet Releaf | Topicals for Pain

Page Load Speed

708 ms in total

First Response

23 ms

Resources Loaded

323 ms

Page Rendered

362 ms

getsweetreleaf.com screenshot

About Website

Visit getsweetreleaf.com now to see the best up-to-date Get Sweet Releaf content and also check out these interesting facts you probably never knew about getsweetreleaf.com

Visit getsweetreleaf.com

Key Findings

We analyzed Getsweetreleaf.com page load time and found that the first response time was 23 ms and then it took 685 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

getsweetreleaf.com performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.167

71/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

Network Requests Diagram

getsweetreleaf.com

23 ms

getsweetreleaf.com

45 ms

css

43 ms

jquery.min.js

18 ms

jquery-migrate.min.js

27 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 52% of them (11 requests) were addressed to the original Getsweetreleaf.com, 43% (9 requests) were made to Fonts.gstatic.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (183 ms) belongs to the original domain Getsweetreleaf.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.4 kB (43%)

Content Size

342.0 kB

After Optimization

196.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Getsweetreleaf.com main page is 342.0 kB. 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 137.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 87.8 kB

  • Original 107.7 kB
  • After minification 106.4 kB
  • After compression 19.8 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 87.8 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 137.9 kB
  • After minification 137.9 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. Get Sweet Releaf images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 57.6 kB

  • Original 96.5 kB
  • After minification 96.5 kB
  • After compression 38.9 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 57.6 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (44%)

Requests Now

9

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

getsweetreleaf.com

getsweetreleaf.com

23 ms

getsweetreleaf.com

getsweetreleaf.com

45 ms

css

css

43 ms

jquery.min.js

jquery.min.js

18 ms

jquery-migrate.min.js

jquery-migrate.min.js

27 ms

scripts.min.js

scripts.min.js

36 ms

jquery.mobile.js

jquery.mobile.js

32 ms

common.js

common.js

30 ms

SR_Lockup_L-Green.png

SR_Lockup_L-Green.png

183 ms

SweetReleaf-Jar-2oz-min.webp

SweetReleaf-Jar-2oz-min.webp

183 ms

Lifestyle_image.webp

Lifestyle_image.webp

73 ms

SR_Lockup_L-Green.png

SR_Lockup_L-Green.png

20 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

23 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

28 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

50 ms

Accessibility Review

getsweetreleaf.com accessibility score

68

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.

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

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

getsweetreleaf.com 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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

getsweetreleaf.com SEO score

86

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

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 Getsweetreleaf.com 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 Getsweetreleaf.com 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

getsweetreleaf.com

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