Tools & Wizards About Us
headytreasures.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

headytreasures.com

Online Smoke Shop | Glass Pipes, Dab Rigs | Heady Treasures

Page Load Speed

2.4 sec in total

First Response

58 ms

Resources Loaded

1.5 sec

Page Rendered

808 ms

headytreasures.com screenshot

About Website

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

At our online smoke shop, you will find a variety of heady glass treasures from Glass Pipes, to Dab Rigs and more. All made in the USA.

Visit headytreasures.com

Key Findings

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

Performance Metrics

headytreasures.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

68/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

headytreasures.com

58 ms

headytreasures.com

69 ms

forms.min.css

17 ms

sweetalert2.min.css

38 ms

sweetalert2.css

37 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 81% of them (63 requests) were addressed to the original Headytreasures.com, 5% (4 requests) were made to Use.fontawesome.com and 4% (3 requests) were made to Staticw2.yotpo.com. The less responsive or slowest element that took the longest time to load (547 ms) relates to the external source Staticw2.yotpo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.6 kB (21%)

Content Size

928.1 kB

After Optimization

735.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Headytreasures.com main page is 928.1 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. 60% of websites need less resources to load. Javascripts take 646.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 178.3 kB

  • Original 209.4 kB
  • After minification 199.9 kB
  • After compression 31.1 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 178.3 kB or 85% of the original size.

Image Optimization

-23%

Potential reduce by 338 B

  • Original 1.5 kB
  • After minification 1.1 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. Obviously, Heady Treasures needs image optimization as it can save up to 338 B or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 12.9 kB

  • Original 646.6 kB
  • After minification 646.6 kB
  • After compression 633.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 1.0 kB

  • Original 70.6 kB
  • After minification 70.6 kB
  • After compression 69.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. Headytreasures.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (93%)

Requests Now

67

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

headytreasures.com

headytreasures.com

58 ms

headytreasures.com

headytreasures.com

69 ms

forms.min.css

forms.min.css

17 ms

sweetalert2.min.css

sweetalert2.min.css

38 ms

sweetalert2.css

sweetalert2.css

37 ms

owl.carousel.min.css

owl.carousel.min.css

60 ms

owl.theme.default.min.css

owl.theme.default.min.css

58 ms

form-basic.css

form-basic.css

48 ms

ninjaforms.css

ninjaforms.css

60 ms

wishlist.css

wishlist.css

57 ms

style.css

style.css

59 ms

flatsome.css

flatsome.css

74 ms

flatsome-shop.css

flatsome-shop.css

87 ms

jetpack.css

jetpack.css

91 ms

jquery.min.js

jquery.min.js

102 ms

fp-rac-guest-checkout.js

fp-rac-guest-checkout.js

89 ms

sweetalert2.min.js

sweetalert2.min.js

90 ms

polyfill.min.js

polyfill.min.js

120 ms

826a7e3dce.js

826a7e3dce.js

100 ms

wt_owl_carousel.js

wt_owl_carousel.js

133 ms

jquery.cookie.min.js

jquery.cookie.min.js

138 ms

tracking.min.js

tracking.min.js

139 ms

headerScript.js

headerScript.js

140 ms

s-202434.js

s-202434.js

36 ms

wclsi-admin.min.js

wclsi-admin.min.js

320 ms

l.js

l.js

64 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

320 ms

wp-polyfill.min.js

wp-polyfill.min.js

320 ms

hoverIntent.min.js

hoverIntent.min.js

320 ms

flatsome.js

flatsome.js

321 ms

wishlist.js

wishlist.js

321 ms

flatsome-instant-page.js

flatsome-instant-page.js

321 ms

flatsome-live-search.js

flatsome-live-search.js

322 ms

index.js

index.js

322 ms

flatsome-lazy-load.js

flatsome-lazy-load.js

324 ms

woocommerce.js

woocommerce.js

322 ms

packery.pkgd.min.js

packery.pkgd.min.js

323 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

324 ms

e-202434.js

e-202434.js

28 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

488 ms

jquery.yith-wcwl.min.js

jquery.yith-wcwl.min.js

487 ms

underscore.min.js

underscore.min.js

466 ms

wp-util.min.js

wp-util.min.js

466 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

456 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

455 ms

forms.js

forms.js

457 ms

zxcvbn-async.min.js

zxcvbn-async.min.js

456 ms

hooks.min.js

hooks.min.js

456 ms

i18n.min.js

i18n.min.js

454 ms

password-strength-meter.min.js

password-strength-meter.min.js

454 ms

password-strength-meter.min.js

password-strength-meter.min.js

428 ms

webfontloader.js

webfontloader.js

385 ms

widget.js

widget.js

547 ms

gtm.js

gtm.js

518 ms

2stacks.png

2stacks.png

308 ms

Bitcoin-Accepted-Here.png

Bitcoin-Accepted-Here.png

306 ms

Litecoin-Logo.png

Litecoin-Logo.png

306 ms

Payment-Icons.png

Payment-Icons.png

307 ms

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

297 ms

pxiEyp8kv8JHgFVrJJnedHFHGPezSQ.woff

pxiEyp8kv8JHgFVrJJnedHFHGPezSQ.woff

296 ms

pxiByp8kv8JHgFVrLCz7Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLCz7Z1xlE92JQEk.woff

299 ms

pxiByp8kv8JHgFVrLCz7Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLCz7Z1JlE92JQEl8qw.woff

298 ms

fl-icons.ttf

fl-icons.ttf

126 ms

826a7e3dce.css

826a7e3dce.css

72 ms

font-awesome-css.min.css

font-awesome-css.min.css

30 ms

chunk.countup.js

chunk.countup.js

147 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

58 ms

chunk.sticky-sidebar.js

chunk.sticky-sidebar.js

58 ms

widget.css

widget.css

341 ms

chunk.tooltips.js

chunk.tooltips.js

73 ms

analytics.js

analytics.js

31 ms

i

i

21 ms

chunk.vendors-popups.js

chunk.vendors-popups.js

29 ms

collect

collect

15 ms

chunk.vendors-slider.js

chunk.vendors-slider.js

17 ms

js

js

49 ms

open_sans.css

open_sans.css

26 ms

zxcvbn.min.js

zxcvbn.min.js

84 ms

Accessibility Review

headytreasures.com accessibility score

87

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

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

headytreasures.com SEO score

100

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

headytreasures.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: