iguanasell.com website review

Signyfyd costs a phone 2.8 s of main-thread work and 538 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.

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

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

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

The page has 5,862 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 2.3 MB and 4.4 s of main-thread time.

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

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

Google Tag Manager costs a phone 497 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.

About 407 KiB of JavaScript is downloaded but never used on this page.

About 75 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.

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

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

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

Polyfills for old browsers add 57 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 24.1 s. Good is under 3.8 s.

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

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

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.

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

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

Your homepage downloads 4.1 MB in 466 requests on a phone: scripts 2.2 MB (237), other files 907 KiB (153) and images 375 KiB (22). Under 2 MB keeps phones on slow connections fast.

B_U-BOAT_ef979397-2137-4f18-865f-d4f314e87e25_400x.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).

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

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

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

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

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

Document should not have more than one banner landmark: 1 element on the page fails 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.

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

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

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.

Your meta description is 198 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization, WebPage and WebSite) but with 4 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 352 pages on iguanasell.com and 14 external pages.

Your homepage links to https://www.iguanasell.com/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/collections/pens, https://www.iguanasell.com/collections/watches, https://www.iguanasell.com/collections/accessories and https://www.iguanasell.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.iguanasell.com/pages/contact, https://www.iguanasell.com/collections/pens, https://www.iguanasell.com/collections/watches, https://www.iguanasell.com/collections/accessories, https://www.iguanasell.com/pages/about-us and https://www.iguanasell.com/collections/aurora 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 145 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343211321&Ver=2&mid=5254bdb0-1571-4359-baf8-b58fc2a02478&bo=5&sid=11e737d0deb511f1866bcbe92520e1af&vid=11e75ad0deb511f1b76fc34967282cb6&vids=1&msclkid=N&pi=918639831&l.

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

6 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'IntersectionObserver': parameter 1 is not of type 'Element'.”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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