thepremierstore.com website review

Signyfyd costs a phone 1.1 s of main-thread work and 259 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (Signyfyd, Klaviyo and Yotpo and others), adding 1.3 MB and 1.6 s of main-thread time.

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

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

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

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

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

Klaviyo costs a phone 170 ms of main-thread work and 359 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 images could be 149 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

9 KiB could be saved by minifying JavaScript.

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 page becomes fully interactive after 13.0 s. Good is under 3.8 s.

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

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

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

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

2 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' tap response (inp) went from 72 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.8 MB in 278 requests on a phone: scripts 1.2 MB (92), other files 1,018 KiB (135) and images 350 KiB (22). Under 2 MB keeps phones on slow connections fast.

11-2-26-ParraBlog-6_360x.jpg 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).

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

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

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

Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

Your title is only 7 characters: “Premier”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 214 pages on thepremierstore.com and 3 external pages.

/ and https://thepremierstore.com/collections/premier all use the title “Premier”. Search engines can't tell which page to show for a search, so each competes with the others.

https://thepremierstore.com/collections/new-releases, https://thepremierstore.com/collections/premier, https://thepremierstore.com/collections/footwear-1, https://thepremierstore.com/collections/mens-footwear, https://thepremierstore.com/collections/womens-footwear and https://thepremierstore.com/collections/new-arrivals-apparel and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://thepremierstore.com/collections/new-releases, https://thepremierstore.com/collections/premier, https://thepremierstore.com/collections/footwear-1, https://thepremierstore.com/collections/mens-footwear, https://thepremierstore.com/collections/womens-footwear and https://thepremierstore.com/collections/new-arrivals-apparel and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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

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 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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 70 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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