Website review, no card needed
seedifferently.org.au website review
Visit site (opens in a new tab)Reviewed 21 October 202630 issues · 79 checks
This review found 30 issues worth fixing on seedifferently.org.au, 9 of them high impact, across 79 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
81B- #41,464 of 124,214 reviewed websitesbeats 61%
- #27,465 of 69,818 online storesbeats 54%
- #550 of 2,907 WooCommerce storesbeats 77%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.1 s |
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 148 ms |
| May 9, 2026 | 145 ms |
| May 16, 2026 | 171 ms |
| May 23, 2026 | 164 ms |
| May 30, 2026 | 163 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 134 ms |
| Sep 5, 2026 | 130 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 133 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 129 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
Reduce unused JavaScript
2.2 s · 403 KiBAbout 403 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Render-blocking requests
1.9 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 72). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
800 ms · 149 KiB10 files are served with short cache lifetimes, so returning visitors download them again (149 KiB).
Reduce unused CSS
450 ms · 161 KiBAbout 161 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and userway.org and others), adding 906 KiB and 507 ms of main-thread time.
Google Tag Manager adds 352 ms
352 msGoogle Tag Manager costs a phone 352 ms of main-thread work and 531 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
200 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 125 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 853 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 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: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Every Step Changes Lives Support Triple M Adelaide’s Hike f…”.
First Contentful Paint: 7.5 s
7.5 sThe first text or image appears after 7.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 15.6 s
15.6 sThe page becomes fully interactive after 15.6 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
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.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 148 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 160 ms
160 msScripts block the page for only 160 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 134 requests
2.2 MBYour homepage downloads 2.2 MB in 134 requests on a phone: scripts 1.1 MB (50), fonts 553 KiB (10) and images 227 KiB (32). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails 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.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Every Step Changes Lives” and “VOICE FOR VISION”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("www.instagram.com/seedifferentlysa/#")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://seedifferently.org.au/sitemap_index.xml, so Google discovers your pages only by following links.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
146 internal links, 9 external
The homepage links to 146 pages on seedifferently.org.au and 9 external pages.
4 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “See Differently is a low vision centre in Adelaide providing optometry, assistive tech and guide and assistance dogs. C…”.
Title: 52 characters
Your title is a healthy 52 characters: “See Differently with the Royal Society for the Blind”.
Canonical URL set
The canonical URL is https://seedifferently.org.au/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no https://seedifferently.org.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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (898 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages without a meta description
https://seedifferently.org.au/shop/category/magnification/electronic-magnifiers, https://seedifferently.org.au/shop/category/magnification/optical-magnifiers, https://seedifferently.org.au/contact-us, https://seedifferently.org.au/shop/category/assistive-technology/mobile-phones, https://seedifferently.org.au/shop/category/assistive-technology/software and https://seedifferently.org.au/shop/category/assistive-technology/text-to-speech-ocr and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 69 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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://seedifferently.org.au/wp-content/uploads/2025/10/Low-vision-service-support-400-m.webp.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'foundPosts')”.
2 checks passed
Tap targets are thumb-sized
29 of 31 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 476 words of copy
The homepage carries about 476 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “Contact Us”.
10 calls to action
The homepage has 10 calls to action, for example “Contact Us”, “Shop” and “Learn more about eye conditions”.
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: 1 customer or partner logo and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 14 phone links and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 1 more (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
17 other companies contacted
Loading the homepage contacts 17 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 seedifferently.org.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on seedifferently.org.au, including 14 speed issues and 5 SEO issues. 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.