ink.ie website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 859 KiB and 637 ms of main-thread time.

Google Tag Manager costs a phone 500 ms of main-thread work and 496 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.

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

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

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

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

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

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

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

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

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.

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

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

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

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

The layout shifts by 0.144 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Visually, the page fills in at 3.6 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 120 ms to 120 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.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.8 MB in 231 requests on a phone: scripts 1,010 KiB (63), other files 878 KiB (102) and images 844 KiB (48). Under 2 MB keeps phones on slow connections fast.

newgreen.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).

1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

3 dropdowns have no label.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 129 pages on ink.ie and 1 external page.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://ink.ie/pages/brother-ink-cartridges, https://ink.ie/pages/canon-ink-cartridges, https://ink.ie/pages/epson-ink-cartridges and https://ink.ie/pages/hp-ink-cartridges have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://ink.ie/collections/best-selling-epson-ink-cartridges/products/compatible-epson-603xl-ink-cartridges-multipack-t03a6, whose canonical is https://ink.ie/products/compatible-epson-603xl-ink-cartridges-multipack-t03a6. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ink.ie/pages/brother-ink-cartridges, https://ink.ie/pages/canon-ink-cartridges, https://ink.ie/pages/epson-ink-cartridges and https://ink.ie/pages/hp-ink-cartridges have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

The homepage carries about 884 words of visible text.

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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.