arnotts.ie website review

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

About 1.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.3 s faster on a phone.

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

45 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

852 KiB could be saved by minifying CSS.

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

239 KiB could be saved by minifying JavaScript.

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

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

8 third-party services load with your homepage (Stripe, Google Tag Manager and Optanon and others), adding 778 KiB and 702 ms of main-thread time.

Polyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

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

Stripe costs a phone 254 ms of main-thread work and 278 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

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

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.

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.

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

Your largest element takes 29.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Warehouse sale advertisement with text 'Up to 70% off' on a…”.

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

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

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

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

25 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 204 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.0 MB in 85 requests on a phone: images 4.7 MB (25), scripts 1.9 MB (31) and stylesheets 1.1 MB (4). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

13 images are downloaded at several times the size a phone draws them, for example ARN26-WK43-SHOES-HP-mob.jpg at 1,400 px wide, shown at 371 px. Resized copies would save about 2.3 MB.

17 images (4.7 MB) 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.

15 images further down the page (4.1 MB) 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 2.27 g of CO₂e: 272.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 tap target is too small or too close together to hit reliably with a finger.

Contentinfo 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 contentinfo 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.

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Structured data found ((untyped) and WebSite) but with 8 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

No Open Graph image (also missing: og:title, og:description), 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 701 pages on arnotts.ie and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

/up-to-70-off-home/home-offers/dining-1 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/the-warehouse-sale/home, /up-to-70-off-home/home-offers/bedroom-1, /up-to-70-off-home/home-offers/kitchen-1, /up-to-70-off-home/home-offers/dining-1, /up-to-70-off-home/home-offers/bathroom-1 and /up-to-70-off-home/home-offers/candles-diffusers all use the title “Home Offers”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/customer-service/dispatch-and-delivery.html, /encore-loyalty.html, /beauty/virtual-services, /the-warehouse-sale/home, /up-to-70-off-home/home-offers/bedroom-1 and /up-to-70-off-home/home-offers/kitchen-1 and 6 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example /customer-service/dispatch-and-delivery.html, whose canonical is /shopping-online/dispatch-and-delivery. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.arnotts.ie/new-in/toys/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

arnotts.ie has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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

The homepage carries about 575 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 21 cookies, 1 of them by other companies (measured from a US location before any click).

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