imagimags.com website review

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

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

29 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Shopify and loox.io and others), adding 2.9 MB and 1.0 s of main-thread time.

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

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

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

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

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

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

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

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

seguno.com costs a phone 30 ms of main-thread work and 432 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.

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

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

35 KiB could be saved by minifying JavaScript.

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.

4 KiB could be saved by minifying CSS.

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 12.5 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 25.9 s. Good is under 3.8 s.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 128 ms to 166 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 802 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 7.3 MB in 323 requests on a phone: images 4.3 MB (54), scripts 1.5 MB (96) and other files 914 KiB (113). Under 2 MB keeps phones on slow connections fast.

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

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

11 images are downloaded at several times the size a phone draws them, for example COLOUR_NOVEMBER_2026_Instagram_Post_45.png at 1,215 px wide, shown at 390 px. Resized copies would save about 385 KiB.

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

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

1 element hidden from screen readers can still receive keyboard focus.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Your title is 92 characters, so Google will cut it off around 60: “Imagimags | Open-ended play | Magnetic building tiles | Shop Online – Imagimags South Afr…”.

Your <h1> is empty.

The homepage links to 160 pages on imagimags.com and 11 external pages.

https://imagimags.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://imagimags.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://imagimags.com/customer_authentication/redirect, https://imagimags.com/policies/shipping-policy, https://imagimags.com/collections/bestsellers, https://imagimags.com/collections/gift-bundles, https://imagimags.com/collections/younger-kids and https://imagimags.com/collections/older-kids and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://imagimags.com/collections/imagimags, https://imagimags.com/customer_authentication/redirect, https://imagimags.com/collections/bestsellers, https://imagimags.com/collections/gift-bundles, https://imagimags.com/collections/younger-kids and https://imagimags.com/collections/older-kids and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://imagimags.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

4 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 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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