moonwlkr.com website review

About 599 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

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

A phone's processor spends 4.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Yotpo, Klaviyo and reamaze.com and others), adding 4.5 MB and 586 ms of main-thread time.

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

6 images could be 175 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

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

Shopify costs a phone 46 ms of main-thread work and 3.3 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Yotpo costs a phone 187 ms of main-thread work and 375 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Klaviyo costs a phone 127 ms of main-thread work and 312 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

19 KiB could be saved by minifying JavaScript.

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

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

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

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.

Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THC, Delta 8 & Delta 9 Gummies for Sleep, Relaxation & More…”.

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

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

The first text or image appears after 4.2 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 171 ms to 233 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Scripts block taps and scrolling for 243 ms in total while the page loads. Good is under 200 ms.

2 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 7.3 MB in 535 requests on a phone: media 2.9 MB (2), scripts 1.9 MB (124) and other files 1.6 MB (312). Under 2 MB keeps phones on slow connections fast.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

6 buttons have no accessible name, so screen readers announce just “button”.

3 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

There are 2 <h1> headlines (“THC, Delta 8 & Delta 9 Gummies for Sleep, Relaxat…” and “THC, Delta 8 & Delta 9 Gummies for Sleep, Relaxat…”). One clear main headline is easier for people and search engines.

The homepage links to 115 pages on moonwlkr.com and 13 external pages.

/collections/delta-8 and /collections/cbd-cbg-cbn have no <title>, so Google invents the link text in results.

/pages/thc-ban-blackout, /collections/delta-8 and /collections/cbd-cbg-cbn have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/delta-8, /collections/delta-9 and /collections/cbd-cbg-cbn have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/delta-9 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

1 image is served at too low a resolution for sharp phone screens.

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://moonwlkr.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.

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

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: 4 trust badges. 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.

The homepage has only about 55 words of visible text; thin pages give Google and first-time buyers little to go on.

DMARC is set to p=none, so mail pretending to be moonwlkr.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Klaviyo (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 17 cookies, 13 of them by other companies (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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.