primalqueen.com website review

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

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (alia-prod.com, Clarity and Google Tag Manager and others), adding 1.2 MB and 2.1 s of main-thread time.

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

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

alia-prod.com costs a phone 846 ms of main-thread work and 335 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.

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

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

Clarity costs a phone 424 ms of main-thread work and 28 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.

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

Shopify costs a phone 118 ms of main-thread work and 301 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.

44 KiB could be saved by minifying JavaScript.

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

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

29 KiB could be saved by minifying CSS.

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 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 20.1 MB in 577 requests on a phone: media 13.6 MB (1), scripts 1.8 MB (108) and images 1.8 MB (96). Under 2 MB keeps phones on slow connections fast.

image_29_1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

5 images further down the page (369 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (51 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.

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

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

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

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

The homepage links to 34 pages on primalqueen.com and 7 external pages.

https://primalqueen.com/a/loop_subscriptions/get-subscription-link, https://primalqueen.com/collections/hsa-fsa, https://primalqueen.com/pages/tiktok, https://primalqueen.com/products/colostrum, https://primalqueen.com/pages/build-your-bundle and https://primalqueen.com/pages/retail are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://primalqueen.com/a/loop_subscriptions/get-subscription-link, https://primalqueen.com/pages/tiktok, https://primalqueen.com/pages/goddess-bites and https://primalqueen.com/pages/retail all use the title “Primal Queen”. Search engines can't tell which page to show for a search, so each competes with the others.

https://primalqueen.com/a/loop_subscriptions/get-subscription-link, https://primalqueen.com/pages/tiktok, https://primalqueen.com/policies/terms-of-service and https://primalqueen.com/pages/retail have no meta description, so Google writes the search snippet from whatever text it finds.

https://primalqueen.com/collections/shop-all, https://primalqueen.com/pages/contact, https://primalqueen.com/a/loop_subscriptions/get-subscription-link, https://primalqueen.com/collections/hsa-fsa, https://primalqueen.com/pages/tiktok and https://primalqueen.com/pages/pq7 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'hidden')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

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

The homepage carries about 2,723 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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