pringledeconstructed.com website review

Signyfyd costs a phone 2.2 s of main-thread work and 536 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.

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

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

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

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

8 third-party services load with your homepage (Signyfyd, Shopify and Google Tag Manager and others), adding 2.3 MB and 3.6 s of main-thread time.

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

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

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

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

49 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

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

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

Your homepage downloads 20.1 MB in 421 requests on a phone: media 15.8 MB (2), scripts 2.2 MB (119) and other files 1.3 MB (227). Under 2 MB keeps phones on slow connections fast.

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

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is 69 characters, so Google will cut it off around 60: “Pringle of Scotland® Official | Iconic Knitwear & Cashmere since 1815”.

Structured data found (ClothingStore, Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("pringlescotland.com")”.

Your <h1> is empty.

The homepage links to 275 pages on pringledeconstructed.com and 7 external pages.

https://pringlescotland.com/collections/chinos has no meta description, so Google writes the search snippet from whatever text it finds.

https://pringlescotland.com/collections/mens-new-arrivals, https://pringlescotland.com/collections/mens-gifts, https://pringlescotland.com/collections/chinos, https://pringlescotland.com/collections/mens-sweats-collection, https://pringlescotland.com/collections/silk-blend and https://pringlescotland.com/collections/mens-golf-edit 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 111 found) and read each the way a search engine does.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 569 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 16 cookies (measured from a US location before any click).

Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.