hashstash.co website review

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.

About 289 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

10 files are served with short cache lifetimes, so returning visitors download them again (327 KiB).

About 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

The page has 2,330 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (alia-prod.com, Klaviyo and Cloudflare CDN and others), adding 849 KiB and 356 ms of main-thread time.

27 KiB could be saved by minifying JavaScript.

2 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need.

2 images could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

The page becomes fully interactive after 10.2 s. Good is under 3.8 s.

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

By the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

5 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 2 <h1> headlines (“HashStash” and “"Started as a gift. Ended up as mine."”). One clear main headline is easier for people and search engines.

Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, FAQPage, Organization and WebSite) but with 1 problem, for example “FAQPage: a question has no acceptedAnswer.text”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 48 pages on hashstash.co and 17 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://hashstash.co/en-ca and https://hashstash.co/en-uk declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://hashstash.co/en-ca and https://hashstash.co/en-uk all use the title “HashStash Co | Premium Stash Box & Accessories for Your Herbs”. Search engines can't tell which page to show for a search, so each competes with the others.

https://hashstash.co/blogs/the-stash-blog, https://hashstash.co/pages/contact and https://hashstash.co/pages/stashbox-gift have no meta description, so Google writes the search snippet from whatever text it finds.

https://hashstash.co/en-ca and https://hashstash.co/en-uk use the same meta description. A description written for each page earns more clicks.

https://hashstash.co/pages/contact, https://hashstash.co/pages/faqs, https://hashstash.co/pages/stashbox-gift, https://hashstash.co/products/hashstash, https://hashstash.co/pages/shipping-policies and https://hashstash.co/pages/refund-policy have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.

6 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,836 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 32 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.