iguanasell.com.au website review

Signyfyd costs a phone 1.3 s of main-thread work and 282 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Signyfyd, Shopify and Google Tag Manager and others), adding 1.9 MB and 2.3 s of main-thread time.

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

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

Shopify costs a phone 466 ms of main-thread work and 824 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 74 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.

Google Tag Manager costs a phone 324 ms of main-thread work and 331 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 291 KiB of JavaScript is downloaded but never used on this page.

Klaviyo costs a phone 204 ms of main-thread work and 357 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.

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

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

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

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

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 page becomes fully interactive after 20.3 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 3.6 MB in 410 requests on a phone: scripts 1.8 MB (219), other files 819 KiB (124) and images 362 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

64 elements use ARIA attributes their role does not allow, which confuses screen readers.

4 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("www.linkedin.com/company/iguana-sell")”.

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

The homepage links to 323 pages on iguanasell.com.au and 14 external pages.

Your homepage links to https://www.iguanasell.com.au/www.linkedin.com/company/iguana-sell, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.iguanasell.com.au/collections/pens, https://www.iguanasell.com.au/collections/watches, https://www.iguanasell.com.au/collections/accessories and https://www.iguanasell.com.au/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.iguanasell.com.au/collections/pens, https://www.iguanasell.com.au/collections/watches, https://www.iguanasell.com.au/collections/accessories, https://www.iguanasell.com.au/pages/about-us, https://www.iguanasell.com.au/collections/aurora and https://www.iguanasell.com.au/collections/caran-dache and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 134 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 429 ()”.

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 has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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