salcura.ie website review

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

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

8 third-party services load with your homepage (loox.io, rebuyengine.com and Klaviyo and others), adding 2.1 MB and 1.4 s of main-thread time.

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

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

rebuyengine.com costs a phone 323 ms of main-thread work and 651 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.

loox.io costs a phone 383 ms of main-thread work and 27 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.

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

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

rechargecdn.com costs a phone 169 ms of main-thread work and 296 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.

tidio.co costs a phone 145 ms of main-thread work and 515 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.

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

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

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

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

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

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

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.

Your largest element takes 9.7 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 18.2 s. Good is under 3.8 s.

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 96 ms to 138 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.8 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 4.2 MB in 309 requests on a phone: scripts 1.6 MB (109), images 1.1 MB (34) and other files 848 KiB (107). Under 2 MB keeps phones on slow connections fast.

website_content_4_f3e351c9-25d9-4e5d-a38e-991e02c10e15.png 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).

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

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

All page content should be contained by landmarks: 3 elements on the page fail 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.

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

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

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

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

Your <h1> is empty.

The homepage links to 166 pages on salcura.ie and 11 external pages.

https://salcura.ie/collections/bundles, https://salcura.ie/collections/all, https://salcura.ie/collections/individual-items, https://salcura.ie/collections/best-sellers, https://salcura.ie/collections/bioskin-junior-bundles and https://salcura.ie/collections/bioskin-bundles and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://salcura.ie/collections/bundles, https://salcura.ie/collections/all, https://salcura.ie/collections/individual-items, https://salcura.ie/collections/best-sellers, https://salcura.ie/collections/bioskin and https://salcura.ie/collections/bioskin-junior and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 74 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: net::ERR_FAILED”.

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

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 1,056 words of visible text.

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