iltutto.com.au website review

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

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

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

8 third-party services load with your homepage (Shopify, Yotpo and Kaltura Video Platform and others), adding 3.9 MB and 2.4 s of main-thread time.

105 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

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

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

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

Yotpo costs a phone 374 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.

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

Kaltura Video Platform costs a phone 340 ms of main-thread work and 1.0 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 CDN costs a phone 303 ms of main-thread work and 361 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.

reddit costs a phone 293 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.

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

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

37 KiB could be saved by minifying JavaScript.

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

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

27 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

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

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

11 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 187 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.0 MB in 525 requests on a phone: media 4.8 MB (5), images 3.2 MB (127) and scripts 2.9 MB (156). Under 2 MB keeps phones on slow connections fast.

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

2 images (522 KiB) 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.

4 images further down the page (366 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 3.67 g of CO₂e: 440.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

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

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

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 269 pages on iltutto.com.au and 64 external pages.

https://www.iltutto.com.au/pages/contact and https://www.iltutto.com.au/pages/swym-wishlist have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.iltutto.com.au/collections/hot-offers, https://www.iltutto.com.au/pages/videos and https://www.iltutto.com.au/pages/swym-wishlist have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.iltutto.com.au/pages/trend-collection took over 3 s to send its HTML from our server.

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

10 images failed to load on a phone, for example https://www.iltutto.com.au/.

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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