SEO report for www.westernsydney.edu.au
https://www.westernsydney.edu.au/ · checked Sun, 01 Nov 2026 18:23 GMT
Fix these first
- LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
Also fixes: Entity clarity
- Server response (TTFB)high
2209 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
- Render-blocking resourceshigh
0 blocking script(s) and 6 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- H1 headingcritical
2 H1 headings – one clear H1 is best practice.
Fix: Use one H1 that states the page topic with its main keyword.
- Heading structuremedium
37 headings for 420 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Anchor text qualitymedium
Same text used for different pages: “contact us”, “learn more”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- Imagesmedium
114 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to westernsydney.edu.au…
Indexing & crawling 94%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- !
XML sitemaphigh
Sitemap found at https://www.westernsydney.edu.au/sitemap.xml with over 5,232 URLs (we read the first 1 MB).
Not declared in robots.txt.
Most recent lastmod: 2026-10-30T02:26:10+00:00.
Fix: Add a 'Sitemap:' line to robots.txt, list every indexable page and include accurate lastmod dates.
- ✓
Canonical URLhigh
Canonical: https://www.westernsydney.edu.au
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://westernsydney.edu.au/ → https://www.westernsydney.edu.au/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
westernsydney.edu.au redirects to www.westernsydney.edu.au.
Search snippet & sharing 79%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Home | Western Sydney University”
About 310px of Google's ~580px desktop width.
- !
Meta descriptionhigh
158 characters, ~1019px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-AU"
Content quality 57%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
420 words of main content (menus and footer excluded).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- !
Readabilitymedium
Flesch reading ease 42 (fairly difficult), about 16 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
4 of 4 title keywords appear in the main content.
- !
H1 headingcritical
2 H1 headings – one clear H1 is best practice.
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- ✗
Heading structuremedium
37 headings for 420 words – a lot for the amount of text.
1 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
3% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 56%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- !
Question-led contentmedium
2 heading(s) phrased as questions, e.g. “Where would you like to start?”.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✓
Trust pages (E-E-A-T)medium
Links found to all three: about, contact and privacy.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): CollegeOrUniversity, PropertyValue, ImageObject, ContactPoint, PostalAddress, WebSite, SearchAction, EntryPoint, WebPage.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 75%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
122 internal and 11 external links.
- ✗
Anchor text qualitymedium
Same text used for different pages: “contact us”, “learn more”.
4 vague link(s) like “click here” or “read more”.
4 link(s) with no text at all.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
1 link(s) point to a redirect – link to the final address instead.
Performance 23%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✗
Server response (TTFB)high
2209 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
- !
HTML sizemedium
199 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- ✗
Render-blocking resourceshigh
0 blocking script(s) and 6 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- !
Scripts & third partiesmedium
25 script tag(s); files loaded from 5 other domain(s): rum.hlx.page, assets.adobedtm.com, youtube.com, ajax.googleapis.com, cdnjs.cloudflare.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
114 image(s).
112 without width/height – can cause layout shift (CLS).
111 image(s) after the first three aren't lazy-loaded.
10 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✓
Cachinglow
Cache-Control: public, max-age=1800, must-revalidate
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 96%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=63072000; includeSubDomains
- !
Security headerslow
Present: nosniff, Referrer-Policy, clickjacking protection.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 70%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1, user-scalable=yes
- ✗
Image alt textmedium
12 of 114 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✗
Link nameslow
4 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✓
Tap-to-contactmedium
One-tap contact: phone.
Local SEO 33%
Signals that help you appear in Google Maps and 'near me' searches.
- ✗
LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- ✓
Contact details on pagemedium
A UK phone number is shown.
No postcode found (fine for service-area businesses).
- ✗
Map & directionslow
No map or directions link.
Fix: Add a Google Maps directions link so customers can find you.