primestyle.com website review

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

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

8 third-party services load with your homepage (Klaviyo, Google Tag Manager and clixtell.com and others), adding 1.6 MB and 3.2 s of main-thread time.

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

Klaviyo costs a phone 747 ms of main-thread work and 618 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.

Google Tag Manager costs a phone 687 ms of main-thread work and 174 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 609 ms. During a long task the page ignores taps.

clixtell.com costs a phone 589 ms of main-thread work and 33 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.

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

Hotjar costs a phone 269 ms of main-thread work and 262 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.

Accessibe Accessibility Overlay costs a phone 259 ms of main-thread work and 250 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.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 50 ms.

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.6 MB in 167 requests on a phone: scripts 1.7 MB (94), images 583 KiB (33) and fonts 175 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example f41f65e5-b0e8-4978-8c7e-ac5019022901.png at 900 px wide, shown at 108 px. Resized copies would save about 47 KiB.

6 images (349 KiB) are 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 0.74 g of CO₂e: 88.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements must only use permitted ARIA attributes: 9 elements on the page fail this check, rated serious by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 482 pages on primestyle.com and 9 external pages.

There is no /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.

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

3 images failed to load on a phone, for example data:image/gif;base64,R0lGODlhAQABAAAAACw=.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

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