Website review, no card needed
secrets-shhh.com.au website review
Visit site (opens in a new tab)Reviewed 9 November 202647 issues · 83 checks
This review found 47 issues worth fixing on secrets-shhh.com.au, 17 of them high impact, across 83 checks. The most urgent: improve image delivery. 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
74C- #86,601 of 123,940 reviewed websitesbeats 26%
- #54,452 of 69,719 online storesbeats 18%
- #51,163 of 63,424 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 129 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 133 ms |
| Jun 13, 2026 | 140 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 152 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 155 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 157 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 159 ms |
| Sep 5, 2026 | 160 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 172 ms |
| Sep 26, 2026 | 184 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 185 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 175 ms |
| Oct 31, 2026 | 171 ms |
| Nov 7, 2026 | 168 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
2.1 s · 1.5 MB20 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Reduce unused JavaScript
1.2 s · 789 KiBAbout 789 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.7 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Use efficient cache lifetimes
1.1 s · 374 KiB23 files are served with short cache lifetimes, so returning visitors download them again (374 KiB).
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (wingify.net, Google Tag Manager and Hotjar and others), adding 1.6 MB and 1.7 s of main-thread time.
wingify.net adds 499 ms
499 mswingify.net costs a phone 499 ms of main-thread work and 226 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 334 ms. During a long task the page ignores taps.
Google Tag Manager adds 296 ms
296 msGoogle Tag Manager costs a phone 296 ms of main-thread work and 333 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.
Klaviyo adds 223 ms
223 msKlaviyo costs a phone 223 ms of main-thread work and 538 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.
Hotjar adds 267 ms
267 msHotjar costs a phone 267 ms of main-thread work and 66 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.
2,209 HTML elements
The page has 2,209 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
290 ms · 55 KiBAbout 55 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
Legacy JavaScript
150 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 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.
Largest Contentful Paint: 16.4 s
16.4 sYour largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 27.8 s
27.8 sThe page becomes fully interactive after 27.8 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 129 ms to 168 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 586 ms
586 msScripts block taps and scrolling for 586 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.179
0.179The layout shifts by 0.179 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Images and page weight
1 image over 500 KB
BF_Unlocked_The_Final_Edit_650x485_navy_650x.gif weighs 5.9 MB. On a phone connection a single image that size takes seconds.
Page weight: 6.0 MB in 322 requests
6.0 MBYour homepage downloads 6.0 MB in 322 requests on a phone: images 2.6 MB (34), scripts 1.9 MB (129) and other files 877 KiB (135). Under 2 MB keeps phones on slow connections fast.
9 images below the first screen load straight away
9 images further down the page (6.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (5.9 MB) is 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.
2 images far larger than shown
177 KiB2 images are downloaded at several times the size a phone draws them, for example Hmpg_HERO_Bnnr_Slider_Live-Lab-Sale_PerCarat_01_1000_x_1120_ at 1,829 px wide, shown at 390 px. Resized copies would save about 177 KiB.
About 1.7 g of CO₂ per visit
1.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 202.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
108 elements hidden from screen readers can still receive keyboard focus.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (16 characters)
Your title is only 16 characters: “Secrets by Amaar”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 3 problems
Structured data found (JewelryStore and WebSite) but with 3 problems, for example “WebSite: missing name”.
287 internal links, 12 external
The homepage links to 287 pages on secrets-shhh.com.au and 12 external pages.
5 checks passed
One H1 headline
Your main headline reads: “.s0 { fill: #172f54 }”.
Canonical URL set
The canonical URL is https://www.secretsbyamaar.com.au/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.secretsbyamaar.com.au/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.secretsbyamaar.com.au/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,261 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 158 found) and read each the way a search engine does.
1 checks passed
Linked pages load
3 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “apiKey is missing, please provide it so we can authenticate the application x.<anonymous> (https://www.secretsbyamaar.c…”.
2 checks passed
Tap targets are thumb-sized
154 of 162 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 608 words of copy
The homepage carries about 608 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP 60% OFF CLEARANCE” and “Shop by Stone Type”.
42 calls to action
The homepage has 42 calls to action, for example “SHOP 60% OFF CLEARANCE”, “Shop by Stone Type” and “Shop by Style”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Microsoft Clarity and Hotjar.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo 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.
30 cookies set on arrival
30Opening the homepage sets 30 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.
46 other companies contacted
Loading the homepage contacts 46 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 secrets-shhh.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Lookfy Gallery · Klaviyo Email Marketing Sms · Wingify · Okendo · Pagefly Ai Page Builder · Simprosys Google Shopping Feed · Elevar Conversion Tracking · Pop Convert · 56071677a62720b5cde4241477474f626e61c35a · webmarked.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Hotjar | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Noosaville
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on secrets-shhh.com.au, including 25 speed issues, 3 SEO issues and 4 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.