montkhemp.com website review

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

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

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

4 third-party services load with your homepage (Yotpo, Shopify and shop.app and others), adding 146 KiB and 114 ms of main-thread time.

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

About 43 KiB of JavaScript is downloaded but never used on this page.

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

About 10 KiB of CSS is downloaded but never applied on this page.

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.

2 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying JavaScript.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 184 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.0 MB in 233 requests on a phone: images 816 KiB (40), other files 721 KiB (102) and scripts 243 KiB (49). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example mk-need-stress-support.jpg at 620 px wide, shown at 64 px. Resized copies would save about 171 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.1 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.

7 tap targets are too small or too close together to hit reliably with a finger.

6 elements hidden from screen readers can still receive keyboard focus.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 82 characters, so Google will cut it off around 60: “MONTKUSH | High Quality USDA Organic Hemp | Pure, Natural Wellness – MONTKUSH Hemp”.

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

The homepage links to 124 pages on montkhemp.com and 0 external pages.

Your Organization JSON-LD is missing logo, 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.

/pages/contact has no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all and /collections/all-products use the same meta description. A description written for each page earns more clicks.

/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://montkhemp.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

montkhemp.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Social proof on the homepage: 93 testimonial or review blocks. 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 815 words of visible text.

montkhemp.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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 15 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.