123ink.ie website review

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

25 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

About 125 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 720 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Sentry and Google CDN and others), adding 1.4 MB and 650 ms of main-thread time.

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

Google Tag Manager costs a phone 285 ms of main-thread work and 843 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 CDN costs a phone 71 ms of main-thread work and 352 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.

10 long tasks block the main thread while loading, the longest for 103 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.

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

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

Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To make shopping at 123ink.ie as easy as possible for you, …”. Most of its time is element render delay (2.4 s).

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

5 images 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 133 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

what's_hot_october_home_banner.png weighs 494 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.7 MB in 94 requests on a phone: scripts 1.8 MB (23), images 1.7 MB (54) and stylesheets 146 KiB (3). Under 2 MB keeps phones on slow connections fast.

14 images (1.4 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.

1 image is downloaded at several times the size a phone draws it, for example what's_hot_october_home_banner.png at 1,600 px wide, shown at 390 px. Resized copies would save about 230 KiB.

5 images further down the page (268 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 1.04 g of CO₂e: 125.1 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”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

No XML sitemap at https://www.123ink.ie/sitemapxml/index-sitemap.xml, so Google discovers your pages only by following links.

3 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 129 pages on 123ink.ie and 9 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 https://www.123ink.ie/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 85 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=5089743&Ver=2&mid=ea79d2b2-a2fb-431b-9806-6cf4496bf0d3&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Cheap%20Printer%20Ink%20Cartridges%20and%20Toner%20Suppl.

27 of 97 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 “Cannot read properties of undefined (reading 'getRegistrations')”.

1 image is served at too low a resolution for sharp phone screens.

The homepage carries about 728 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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