Tools & Wizards About Us
kavabay.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

kavabay.com

Page Load Speed

1.8 sec in total

First Response

165 ms

Resources Loaded

1.3 sec

Page Rendered

339 ms

kavabay.com screenshot

About Website

Visit kavabay.com now to see the best up-to-date Kavabay content for United States and also check out these interesting facts you probably never knew about kavabay.com

Buy Kava. All orders ship from the USA. Buy kava wholesale. We are a USA supplier of premium quality kava root sourced from all across the pacific.

Visit kavabay.com

Key Findings

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

Performance Metrics

kavabay.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,690 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.104

89/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

kavabay.com

165 ms

shopify_stats.js

32 ms

trekkie.storefront.min.js

36 ms

shop_events_listener-4c5801cae3452eff0ededa0ac07d432c1240b78b7e11282cceb3c3213951104b.js

52 ms

express_buttons-f33a5a5303cf964bcde1d0d71bedd7908b6715d6b5c8de87f1da47331c4bbf34.js

55 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Kavabay.com, 54% (26 requests) were made to Cdn.shopify.com and 19% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (622 ms) relates to the external source Affiliatly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 786.1 kB (35%)

Content Size

2.3 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kavabay.com main page is 2.3 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 37.0 kB

  • Original 44.5 kB
  • After minification 32.5 kB
  • After compression 7.5 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. This page needs HTML code to be minified as it can gain 12.1 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.0 kB or 83% of the original size.

Image Optimization

-18%

Potential reduce by 288.7 kB

  • Original 1.6 MB
  • After minification 1.3 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, Kavabay needs image optimization as it can save up to 288.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 283.0 kB

  • Original 402.1 kB
  • After minification 373.7 kB
  • After compression 119.1 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 283.0 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 177.4 kB

  • Original 208.9 kB
  • After minification 207.4 kB
  • After compression 31.6 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. Kavabay.com needs all CSS files to be minified and compressed as it can save up to 177.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (57%)

Requests Now

35

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kavabay. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kavabay.com

kavabay.com

165 ms

shopify_stats.js

shopify_stats.js

32 ms

trekkie.storefront.min.js

trekkie.storefront.min.js

36 ms

shop_events_listener-4c5801cae3452eff0ededa0ac07d432c1240b78b7e11282cceb3c3213951104b.js

shop_events_listener-4c5801cae3452eff0ededa0ac07d432c1240b78b7e11282cceb3c3213951104b.js

52 ms

express_buttons-f33a5a5303cf964bcde1d0d71bedd7908b6715d6b5c8de87f1da47331c4bbf34.js

express_buttons-f33a5a5303cf964bcde1d0d71bedd7908b6715d6b5c8de87f1da47331c4bbf34.js

55 ms

theme.scss.css

theme.scss.css

68 ms

ionicons.min.css

ionicons.min.css

54 ms

css

css

60 ms

css

css

81 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

113 ms

api.jquery-0ea851da22ae87c0290f4eeb24bc8b513ca182f3eb721d147c009ae0f5ce14f9.js

api.jquery-0ea851da22ae87c0290f4eeb24bc8b513ca182f3eb721d147c009ae0f5ce14f9.js

48 ms

currencies.js

currencies.js

47 ms

jquery.currencies.js

jquery.currencies.js

127 ms

option_selection-ea4f4a242e299f2227b2b8038152223f741e90780c0c766883939e8902542bda.js

option_selection-ea4f4a242e299f2227b2b8038152223f741e90780c0c766883939e8902542bda.js

55 ms

modernizr-2.7.1.min.js

modernizr-2.7.1.min.js

122 ms

plugins.js

plugins.js

151 ms

site.js

site.js

178 ms

logo.png

logo.png

86 ms

slide-1-image.jpg

slide-1-image.jpg

185 ms

KAVABAY_VARIETY_PACK_1_grande.jpg

KAVABAY_VARIETY_PACK_1_grande.jpg

50 ms

20161212_104630_8fa68cff-0fe7-41f0-954b-463e8c83f86a_grande.jpg

20161212_104630_8fa68cff-0fe7-41f0-954b-463e8c83f86a_grande.jpg

177 ms

20161212_102859_grande.jpg

20161212_102859_grande.jpg

178 ms

20161212_103800_grande.jpg

20161212_103800_grande.jpg

177 ms

20161212_103448_grande.jpg

20161212_103448_grande.jpg

184 ms

20161212_104143_grande.jpg

20161212_104143_grande.jpg

308 ms

product-details-slideshow-image-1.png

product-details-slideshow-image-1.png

178 ms

session-attribution

session-attribution

42 ms

record.gif

record.gif

40 ms

page

page

26 ms

launch-icons.ttf

launch-icons.ttf

151 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

26 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

35 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

38 ms

dialog

dialog

76 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

17 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

17 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

33 ms

7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf

7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf

33 ms

W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf

W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf

42 ms

t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf

t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf

42 ms

ionicons.ttf

ionicons.ttf

40 ms

socicon-webfont.woff

socicon-webfont.woff

60 ms

main-4ea4e4bba9525db3cb2239f7dae6d8c0a09385ad5b6955b80862c68b894126e4.css

main-4ea4e4bba9525db3cb2239f7dae6d8c0a09385ad5b6955b80862c68b894126e4.css

30 ms

scripts-40d0e394a0e8b193c8d7139597d266dc7e584e1ef69e7552dc6be50aeeb96a82.js

scripts-40d0e394a0e8b193c8d7139597d266dc7e584e1ef69e7552dc6be50aeeb96a82.js

29 ms

storefront.js

storefront.js

30 ms

shopify.js

shopify.js

622 ms

storefront.css

storefront.css

5 ms

init

init

52 ms

Accessibility Review

kavabay.com accessibility score

86

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

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

kavabay.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kavabay.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Kavabay.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

kavabay.com

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