tulio.com.au website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and omnisnippet1.com and others), adding 1.2 MB and 519 ms of main-thread time.

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

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

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

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

1 long task block the main thread while loading, the longest for 193 ms. During a long task the page ignores taps.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

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 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.6 s).

The page becomes fully interactive after 8.5 s. Good is under 3.8 s.

Visually, the page fills in at 6.2 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.

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

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

Your homepage downloads 3.3 MB in 350 requests on a phone: scripts 1.2 MB (127), other files 968 KiB (139) and images 947 KiB (36). Under 2 MB keeps phones on slow connections fast.

week-45-mob-banner_ddb313a3-6dda-46a3-822f-bbbe3879d197.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 0.94 g of CO₂e: 112.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

61 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Elements with visible text labels do not have matching accessible names. (53 elements).

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//tulio.com.au/cdn/shop/files/Tulio-Logo-Black-Text_868…”.

1 link has no real href, so search engines can't follow it.

The homepage links to 389 pages on tulio.com.au and 16 external pages.

Your homepage links to https://tulio.com.au/pages/price-guarantee, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

https://tulio.com.au/collections/all and https://tulio.com.au/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://tulio.com.au/collections/all, https://tulio.com.au/customer_authentication/redirect, https://tulio.com.au/collections/back-in-stock, https://tulio.com.au/collections/just-landed-the-newest-arrivals-in-womens-fashion, https://tulio.com.au/collections/new-skirts-dresses-for-mature-women and https://tulio.com.au/collections/new-tops-for-mature-women and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://tulio.com.au/customer_authentication/redirect, https://tulio.com.au/collections/new-pants-for-mature-women, https://tulio.com.au/collections/new-knitwear and https://tulio.com.au/collections/staceys-style-selection took over 3 s to send their HTML from our server.

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

24 of 51 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'background'”.

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.

The homepage carries about 587 words of visible text.

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