shoyoroll.com.au website review

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Google CDN and squarecdn.com and others), adding 441 KiB and 337 ms of main-thread time.

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

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

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

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

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

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.

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 text “SHOP NOW”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.1 MB in 151 requests on a phone: images 780 KiB (10), other files 677 KiB (77) and scripts 518 KiB (54). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example A15I0861_1024x1024.jpg at 1,024 px wide, shown at 328 px. Resized copies would save about 5 KiB.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 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.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 19 characters: “Shoyoroll Australia”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 21 pages on shoyoroll.com.au and 2 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://shoyoroll.com.au/collections/all/products/syr-kimono-v1-white and https://shoyoroll.com.au/products/syr-kimono-v1-white all use the title “SYR BRAZIL Kimono V1 (White) – Shoyoroll Australia”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

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

https://shoyoroll.com.au/collections/all/products/syr-kimono-v1-white, https://shoyoroll.com.au/products/syr-kimono-v1-white, https://shoyoroll.com.au/collections/all/products/syr-kimono-v1-black and https://shoyoroll.com.au/products/syr-kimono-v1-black use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://shoyoroll.com.au/collections/all/products/syr-kimono-v1-white, whose canonical is https://shoyoroll.com.au/products/syr-kimono-v1-white. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shoyoroll.com.au/collections/all, https://shoyoroll.com.au/pages/contact, https://shoyoroll.com.au/pages/faq, https://shoyoroll.com.au/pages/terms-conditions and https://shoyoroll.com.au/pages/privacy have no <h1> headline, so visitors and search engines get no clear main topic.

https://shoyoroll.com.au/collections/all, https://shoyoroll.com.au/blogs/syr/train-anywhere, https://shoyoroll.com.au/blogs/syr/lcfc and https://shoyoroll.com.au/pages/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 74 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.

Before a visitor clicks anything, the page loads Klaviyo (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 9 cookies, 1 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.