Website review, no card needed
shiels.com.au website review
Visit site (opens in a new tab)Reviewed 3 November 202650 issues · 100 checks
This review found 50 issues worth fixing on shiels.com.au, 17 of them high impact, across 100 checks. The most urgent: main-thread work: 13.7 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71C- #100,899 of 125,330 reviewed websitesbeats 17%
- #61,451 of 70,159 online storesbeats 10%
- #56,976 of 63,749 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 261 ms |
| May 23, 2026 | 256 ms |
| May 30, 2026 | 255 ms |
| Jun 6, 2026 | 255 ms |
| Jun 13, 2026 | 255 ms |
| Jun 20, 2026 | 260 ms |
| Jun 27, 2026 | 263 ms |
| Jul 4, 2026 | 264 ms |
| Jul 11, 2026 | 265 ms |
| Jul 18, 2026 | 263 ms |
| Jul 25, 2026 | 266 ms |
| Aug 1, 2026 | 268 ms |
| Aug 8, 2026 | 270 ms |
| Aug 15, 2026 | 269 ms |
| Aug 22, 2026 | 269 ms |
| Aug 29, 2026 | 269 ms |
| Sep 5, 2026 | 268 ms |
| Sep 12, 2026 | 273 ms |
| Sep 19, 2026 | 274 ms |
| Sep 26, 2026 | 279 ms |
| Oct 3, 2026 | 287 ms |
| Oct 10, 2026 | 296 ms |
| Oct 17, 2026 | 306 ms |
| Oct 24, 2026 | 312 ms |
| Oct 31, 2026 | 316 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.4 s
2.8 s
4.2 s
5.6 s
7.0 s
8.4 s
9.7 s
11.1 s
Speed
Main-thread work: 13.7 s
A phone's processor spends 13.7 s on main-thread work while loading, 5.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,584 HTML elements
The page has 5,584 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Signyfyd and Google Tag Manager and others), adding 3.2 MB and 2.5 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
1.9 MB50 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 891 ms
891 msShopify costs a phone 891 ms of main-thread work and 1.7 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.
Signyfyd adds 721 ms
721 msSignyfyd costs a phone 721 ms of main-thread work and 259 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.
Use efficient cache lifetimes
449 KiB32 files are served with short cache lifetimes, so returning visitors download them again (449 KiB).
Reduce unused CSS
300 ms · 73 KiBAbout 73 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.
Render-blocking requests
350 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 312 ms. During a long task the page ignores taps.
Google Tag Manager adds 274 ms
274 msGoogle Tag Manager costs a phone 274 ms of main-thread work and 328 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.
shopassistant-ai.com adds 174 ms
174 msshopassistant-ai.com costs a phone 174 ms of main-thread work and 313 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
14 KiB14 KiB JavaScript is shipped twice across bundles.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user LCP: 4.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Speed Index: 16.0 s
16.0 sVisually, the page fills in at 16.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 44.2 s
44.2 sThe page becomes fully interactive after 44.2 s. Good is under 3.8 s.
Largest Contentful Paint: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 928 ms
928 msScripts block taps and scrolling for 928 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 226 ms
226 msReal visitors wait 226 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 261 ms to 316 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 784 ms
784 msReal visitors wait 784 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 11.2 MB in 549 requests
11.2 MBYour homepage downloads 11.2 MB in 549 requests on a phone: images 5.1 MB (231), scripts 3.3 MB (136) and media 1.5 MB (2). Under 2 MB keeps phones on slow connections fast.
13 images far larger than shown
1.1 MB13 images are downloaded at several times the size a phone draws them, for example Catalogue_-_Black.jpg at 2,800 px wide, shown at 360 px. Resized copies would save about 1.1 MB.
An image on the first screen is lazy-loaded
60271677-w.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).
3 images in older formats
3 images (132 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.
1 image below the first screen load straight away
1 image further down the page (187 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.2 g of CO₂ per visit
3.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.18 g of CO₂e: 381.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (20 elements)
Alternative text of images should not be repeated as text: 20 elements on the page fail this check, rated minor by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
775 internal links, 18 external
The homepage links to 775 pages on shiels.com.au and 18 external pages.
6 checks passed
One H1 headline
Your main headline reads: “SHIELS AUSTRALIAN JEWELLERY STORE”.
Title: 60 characters
Your title is a healthy 60 characters: “Engagement Rings, Diamonds, Watches, Gold Jewellery | Shiels”.
Canonical URL set
The canonical URL is https://www.shiels.com.au/.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.shiels.com.au/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,827 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.shiels.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.shiels.com.au/collections/diamonds and https://www.shiels.com.au/collections/natural-diamond-jewellery all use the title “Diamond Jewellery - Earrings, Necklaces, Rings & More | Shiels”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://www.shiels.com.au/collections/hot-deal, https://www.shiels.com.au/collections/lab-grown-diamond-bangles, https://www.shiels.com.au/collections/natural-diamond-rings, https://www.shiels.com.au/collections/natural-diamond-earrings, https://www.shiels.com.au/collections/natural-diamond-bracelets and https://www.shiels.com.au/collections/natural-diamond-bangles use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.shiels.com.au/collections/sale-jewellery, https://www.shiels.com.au/collections/hot-deal, https://www.shiels.com.au/collections/sale-watches, https://www.shiels.com.au/collections/diamonds, https://www.shiels.com.au/collections/brands-luminesce-lab-grown-diamonds and https://www.shiels.com.au/collections/jewellery-rings-lab-grown-diamond and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 118 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
16 distorted images
16 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 599 words of copy
The homepage carries about 599 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW »” and “Start Shopping”.
35 calls to action
The homepage has 35 calls to action, for example “SHOP NOW »”, “shop by category” and “shop by gemstone”.
4 short forms
4 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 10 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 4 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.
32 cookies set on arrival
32Opening the homepage sets 32 cookies (measured from a US location before any click).
No consent tool detected
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.
64 other companies contacted
Loading the homepage contacts 64 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at shiels.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify Hosted
Company
- Founded
- 1945
- Headquarters
- Australia
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on shiels.com.au, including 24 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.