Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

purebotanika.com

Pure Botanika - 96+ Hour Pain Patches, All Natural Relief

Page Load Speed

17.7 sec in total

First Response

282 ms

Resources Loaded

16.2 sec

Page Rendered

1.2 sec

purebotanika.com screenshot

About Website

Click here to check amazing Pure Botanika content. Otherwise, check out these important facts you probably never knew about purebotanika.com

Pure Botanika pain patches deliver natural and long-lasting relief. Just peel it off, stick it to the affected area and enjoy!

Visit purebotanika.com

Key Findings

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

Performance Metrics

purebotanika.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value54.8 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,370 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value32.5 s

0/100

10%

Network Requests Diagram

purebotanika.com

282 ms

purebotanika.com

423 ms

wp-emoji-release.min.js

362 ms

bottom-line.css

322 ms

style.min.css

143 ms

Our browser made a total of 189 requests to load all elements on the main page. We found that 83% of them (157 requests) were addressed to the original Purebotanika.com, 2% (4 requests) were made to Google.com and 2% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (8.8 sec) belongs to the original domain Purebotanika.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.6 MB (83%)

Content Size

10.4 MB

After Optimization

1.8 MB

In fact, the total size of Purebotanika.com main page is 10.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 10.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 299.5 kB

  • Original 339.3 kB
  • After minification 337.2 kB
  • After compression 39.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 299.5 kB or 88% of the original size.

Image Optimization

-83%

Potential reduce by 8.3 MB

  • Original 10.0 MB
  • After minification 1.7 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. Obviously, Pure Botanika needs image optimization as it can save up to 8.3 MB or 83% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 53.4 kB

  • Original 84.3 kB
  • After minification 77.1 kB
  • After compression 30.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 53.4 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 160 (87%)

Requests Now

183

After Optimization

23

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

Accessibility Review

purebotanika.com accessibility score

88

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

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

Browser errors were logged to the console

SEO Factors

purebotanika.com SEO score

79

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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