pavers.ie website review

18 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and cdn-cookieyes.com and others), adding 2.7 MB and 1.1 s of main-thread time.

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

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

Shopify costs a phone 721 ms of main-thread work and 997 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 326 ms of main-thread work and 504 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.

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

sanity.io costs a phone 0 ms of main-thread work and 1.1 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.

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

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

Polyfills for old browsers add 8 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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.

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

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

Real visitors wait 334 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

3b3699d73ffe4b32e59b94976497db75a6f91965-2438x3538.jpg weighs 601 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.9 MB in 129 requests on a phone: images 1.4 MB (34), scripts 1.0 MB (48) and fonts 193 KiB (4). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 3b3699d73ffe4b32e59b94976497db75a6f91965-2438x3538.jpg at 2,438 px wide, shown at 390 px. Resized copies would save about 462 KiB.

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

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

<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

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

Headings should not be empty: 10 elements on the page fail this check, rated minor by axe-core.

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

Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.pavers.co.uk)”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 79 pages on pavers.ie and 9 external pages.

Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

Your homepage links to https://pavers.ie/collections/rieker-shoes, which answers with an error. Visitors hit a dead end and search engines drop it.

https://pavers.ie/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://pavers.ie/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://pavers.ie/collections/womens-shoes-1, whose canonical is https://pavers.ie/collections/womens-shoes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pavers.ie/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

https://pavers.ie/collections/all, https://pavers.ie/pages/key-worker, https://pavers.ie/store, https://pavers.ie/wishlist, https://pavers.ie/collections/womens-shoes-1 and https://pavers.ie/collections/mens-boots and 3 others took over 3 s to send their HTML from our server.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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

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