Website review, no card needed
sussan.com.au website review
Visit site (opens in a new tab)Reviewed 17 November 202654 issues · 94 checks
This review found 54 issues worth fixing on sussan.com.au, 19 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
67D- #104,124 of 115,802 reviewed websitesbeats 8%
- #63,011 of 66,600 online storesbeats 4%
- #514 of 704 Magento storesbeats 25%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.0 s |
| Nov 7, 2026 | 3.0 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 144 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 151 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 170 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 173 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 173 ms |
| Sep 19, 2026 | 175 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 175 ms |
| Oct 17, 2026 | 175 ms |
| Oct 24, 2026 | 174 ms |
| Oct 31, 2026 | 177 ms |
| Nov 7, 2026 | 178 ms |
| Nov 14, 2026 | 177 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
2.2 s
4.3 s
6.5 s
8.6 s
10.8 s
12.9 s
15.1 s
17.3 s
Speed
Reduce unused JavaScript
3.8 s · 2.4 MBAbout 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 2.6 MB73 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Main-thread work: 14.5 s
A phone's processor spends 14.5 s on main-thread work while loading, 9.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
11,000 HTML elements
The page has 11,000 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Insider, ZenDesk and Facebook and others), adding 3.9 MB and 1.8 s of main-thread time.
Reduce unused CSS
890 ms · 269 KiBAbout 269 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 890 ms faster on a phone.
Improve image delivery
930 KiB16 images could be 930 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Insider adds 438 ms
438 msInsider costs a phone 438 ms of main-thread work and 600 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 adds 196 ms
196 msKaltura Video Platform costs a phone 196 ms of main-thread work and 2.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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 366 ms. During a long task the page ignores taps.
ZenDesk adds 322 ms
322 msZenDesk costs a phone 322 ms of main-thread work and 395 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.
Facebook adds 292 ms
292 msFacebook costs a phone 292 ms of main-thread work and 222 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.
Yotpo adds 238 ms
238 msYotpo costs a phone 238 ms of main-thread work and 340 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.
Minify JavaScript
140 ms · 8 KiB8 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
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: 48 ms
48 msYour server sent the HTML in 48 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 CLS: 0.28
0.28For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 21.6 s
21.6 sYour largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 21.1 s
21.1 sVisually, the page fills in at 21.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 57.8 s
57.8 sThe page becomes fully interactive after 57.8 s. Good is under 3.8 s.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 145 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 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) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 143 ms
143 msReal visitors wait 143 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.046
0.046The layout barely moves while loading (CLS 0.046, good is under 0.1).
Images and page weight
Page weight: 11.7 MB in 397 requests
11.7 MBYour homepage downloads 11.7 MB in 397 requests on a phone: images 5.8 MB (89), scripts 4.4 MB (86) and other files 775 KiB (189). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BFVIP-30-Off-Storewide-HP-M.gif 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 far larger than shown
116 KiB2 images are downloaded at several times the size a phone draws them, for example Drop_1-Launch-Website-Campaign-Assets14.jpg at 1,563 px wide, shown at 390 px. Resized copies would save about 116 KiB.
1 image below the first screen load straight away
1 image further down the page (150 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (37 KiB) 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.
About 3.3 g of CO₂ per visit
3.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.32 g of CO₂e: 398.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
59 form fields without a label
59 form fields have no label, so screen readers announce an empty box and autofill guesses.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
499 internal links, 4 external
The homepage links to 499 pages on sussan.com.au and 4 external pages.
3 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “Sussan Black Friday Sale – 30% Off* Storewide for VIPs”.
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.sussan.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.sussan.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,309 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.sussan.com.au/clothing/leisurewear, whose canonical is https://www.sussan.com.au/clothing/loungewear. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.sussan.com.au/store-locator has no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.sussan.com.au/store-locator, https://www.sussan.com.au/new-in/accessories-gift, https://www.sussan.com.au/clothing/pants, https://www.sussan.com.au/clothing/denim, https://www.sussan.com.au/clothing/leisurewear and https://www.sussan.com.au/clothing/sets took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 168 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 13 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
172 small tap targets
172 of 231 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 648 words of copy
The homepage carries about 648 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: “Join / Sign In” and “SHOP THE EDIT”.
27 calls to action
The homepage has 27 calls to action, for example “Join / Sign In”, “Shop The Edit” and “Shop By Price”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads The Trade Desk (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
31 other companies contacted
Loading the homepage contacts 31 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 sussan.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
- E-commerce
- Magento
- Analytics
- Google Tag Manager
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on sussan.com.au, including 27 speed issues, 6 SEO issues and 2 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.