stickygreenbuds.com website review

42 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

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

About 321 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).

43 KiB could be saved by minifying JavaScript.

21 KiB could be saved by minifying CSS.

1 image could be 107 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.

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

1 third-party service load with your homepage (Google Fonts), adding 90 KiB and 0 ms of main-thread time.

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

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Direct from the farm to you”. Most of its time is element render delay (2.2 s).

Visually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 image (199 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (199 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Headings skip levels (h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Sticky Green”, “Direct from the farm to you” and “Sticky Green”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 24 pages on stickygreenbuds.com and 1 external page.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://stickygreenbuds.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://stickygreenbuds.com/our-flowers, https://stickygreenbuds.com/about-us, https://stickygreenbuds.com/community, https://stickygreenbuds.com/news, https://stickygreenbuds.com/comprehensive-guide-101-basics-on-growing-cannabis-indoor-for-strength-and-happiness and https://stickygreenbuds.com/comprehensive-guide-102-basics-on-growing-cannabis-indoor-organic-soil-requirements and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://stickygreenbuds.com/page/2, whose canonical is https://stickygreenbuds.com/2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://stickygreenbuds.com/' was loaded over HTTPS, but requested an insecure image 'http:…”.

Chrome logged issues while loading the page (“Mixed content”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 421 words of visible text.

Opening the homepage sets 7 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.