Website review, no card needed
eands.com.au website review
Visit site (opens in a new tab)Reviewed 3 November 202646 issues · 95 checks
This review found 46 issues worth fixing on eands.com.au, 22 of them high impact, across 95 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
78C- #60,573 of 120,200 reviewed websitesbeats 44%
- #39,726 of 68,092 online storesbeats 36%
- #174 of 714 Magento storesbeats 71%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 133 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 134 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 132 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 132 ms |
| Aug 15, 2026 | 135 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 142 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 153 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 155 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 158 ms |
| Oct 31, 2026 | 161 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.7 s
1.3 s
2.0 s
2.7 s
3.3 s
4.0 s
4.6 s
5.3 s
Speed
Reduce unused JavaScript
5.7 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.
Improve image delivery
2.0 s · 3.3 MB21 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 652 KiB30 files are served with short cache lifetimes, so returning visitors download them again (652 KiB).
Render-blocking requests
1.8 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused CSS
1.2 s · 290 KiBAbout 290 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 3.1 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 (ZenDesk, Google CDN and Facebook and others), adding 1.6 MB and 966 ms of main-thread time.
ZenDesk adds 305 ms
305 msZenDesk costs a phone 305 ms of main-thread work and 456 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.
Google CDN adds 251 ms
251 msGoogle CDN costs a phone 251 ms of main-thread work and 760 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.
Legacy JavaScript
300 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 219 ms. During a long task the page ignores taps.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 43.4 s
43.4 sYour largest element takes 43.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “VISIT THE BLOCKKITCHEN REVEALSLAUNDRY REVEALS”.
Speed Index: 19.7 s
19.7 sVisually, the page fills in at 19.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 62.9 s
62.9 sThe page becomes fully interactive after 62.9 s. Good is under 3.8 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
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 133 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 546 ms
546 msScripts block taps and scrolling for 546 ms in total while the page loads. Good is under 200 ms.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 351 ms
351 msReal visitors wait 351 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 15.8 MB in 490 requests
15.8 MBYour homepage downloads 15.8 MB in 490 requests on a phone: images 9.2 MB (77), scripts 5.1 MB (304) and fonts 593 KiB (9). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 3.9 MB together. On a phone connection a single image that size takes seconds.
9 images below the first screen load straight away
9 images further down the page (695 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
135 KiB1 image is downloaded at several times the size a phone draws it, for example TB26_BestHouseOnTHEBLOCK_WebBanner_1920x960px_v1.png at 1,920 px wide, shown at 360 px. Resized copies would save about 135 KiB.
About 4.5 g of CO₂ per visit
4.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.48 g of CO₂e: 537.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Images must have alternative text (8 elements)
Images must have alternative text: 8 elements on the page fail this check, rated critical by axe-core.
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.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
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 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 11 failed. 3 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.
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.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
250 internal links, 11 external
The homepage links to 250 pages on eands.com.au and 11 external pages.
4 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “e&s make creating the perfect home easier with great prices, honest advice and exceptional service on kitchen, laundry …”.
Title: 39 characters
Your title is a healthy 39 characters: “Home | e&s - Kitchen, Laundry, Bathroom”.
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.eands.com.au/media/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.eands.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,490 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages without a meta description
https://www.eands.com.au/delivery-and-installation, https://www.eands.com.au/quote, https://www.eands.com.au/contact-us, https://www.eands.com.au/stores, https://www.eands.com.au/kitchen-and-cooking/fridges-and-freezers/bottom-mount-fridges and https://www.eands.com.au/kitchen-and-cooking/fridges-and-freezers/top-mount-fridges have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages slow to respond
https://www.eands.com.au/kitchen-and-cooking/fridges-and-freezers/side-by-side-fridges, https://www.eands.com.au/kitchen-and-cooking/fridges-and-freezers/bottom-mount-fridges and https://www.eands.com.au/kitchen-and-cooking/fridges-and-freezers/top-mount-fridges took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 192 found) and read each the way a search engine does.
6 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://scontent-syd2-1.cdninstagram.com/v/t51.82787-15/883374948_18641591950008607_3574252972237240083_n.jpg?stp=dst-jpg_e35_tt6&_nc_cat=103&_nc_map=urlgen_bucketless&ccb=7-5&_nc_sid=18de74&efg=eyJlZ.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
54 of 65 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
About 1,303 words of copy
The homepage carries about 1,303 words of visible text.
6 checks passed
16 calls to action
The homepage has 16 calls to action, for example “Get a quote”, “Register” and “Learn More”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 28 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar 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.
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.
48 other companies contacted
Loading the homepage contacts 48 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 eands.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
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on eands.com.au, including 18 speed issues, 5 SEO issues and 1 conversion gap. 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.