Website review, no card needed
suncorp.com.au website review
Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 89 checks
This review found 45 issues worth fixing on suncorp.com.au, 16 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.3 s |
| Nov 7, 2026 | 2.4 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 150 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 142 ms |
| Oct 17, 2026 | 144 ms |
| Oct 24, 2026 | 144 ms |
| Oct 31, 2026 | 145 ms |
| Nov 7, 2026 | 146 ms |
| Nov 14, 2026 | 145 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
1.1 s
2.1 s
3.2 s
4.3 s
5.3 s
6.4 s
7.4 s
8.5 s
Speed
Use efficient cache lifetimes
4.5 s · 855 KiB13 files are served with short cache lifetimes, so returning visitors download them again (855 KiB).
Reduce unused JavaScript
3.3 s · 806 KiBAbout 806 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
2.0 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Improve image delivery
1.3 s · 154 KiB4 images could be 154 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 4.3 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 (Google Tag Manager, Facebook and raptor.digital and others), adding 1,009 KiB and 1.2 s of main-thread time.
Reduce unused CSS
750 ms · 163 KiBAbout 163 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 735 ms
735 msGoogle Tag Manager costs a phone 735 ms of main-thread work and 605 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
300 ms · 63 KiB63 KiB could be saved by minifying JavaScript.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 358 ms. During a long task the page ignores taps.
Legacy JavaScript
300 ms · 52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Facebook adds 316 ms
316 msFacebook costs a phone 316 ms of main-thread work and 214 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
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: 25 ms
25 msYour server sent the HTML in 25 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.8 s
15.8 sYour largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 18.0 s
18.0 sThe page becomes fully interactive after 18.0 s. Good is under 3.8 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 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.
Cumulative Layout Shift: 0.129
0.129The layout shifts by 0.129 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 147 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 163 ms
163 msReal visitors wait 163 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
Page weight: 2.5 MB in 134 requests
2.5 MBYour homepage downloads 2.5 MB in 134 requests on a phone: scripts 1.9 MB (31), images 258 KiB (49) and stylesheets 171 KiB (1). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
49 KiB1 image is downloaded at several times the size a phone draws it, for example GooglePlayBadge.jpg at 1,666 px wide, shown at 150 px. Resized copies would save about 49 KiB.
1 image in older formats
1 image (53 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.
1 image below the first screen load straight away
1 image further down the page (53 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 85.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
26 text elements with low contrast
26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
42 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: 42 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (29 characters)
Your title is only 29 characters: “Suncorp Australia | Insurance”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 2 problems
Structured data found ((untyped) and Organization) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.
14 links crawlers can't follow
14 links have no real href, so search engines can't follow them.
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.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
149 internal links, 12 external
The homepage links to 149 pages on suncorp.com.au and 12 external pages.
5 checks passed
Meta description: 106 characters
Your meta description is 106 characters: “Suncorp Insurance is One of Australia's Leading Insurers Offering Home, Contents, Motor and Life Insurance”.
One H1 headline
Your main headline reads: “Suncorp Insurance”.
Canonical URL set
The canonical URL is https://www.suncorp.com.au/.
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.suncorp.com.au/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.suncorp.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.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,497 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.suncorp.com.au/insurance/home.html and https://www.suncorp.com.au/insurance/home all use the title “Home Insurance | Get $100 Off Quoting & Buying Online | Suncorp”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.suncorp.com.au/insurance/home.html and https://www.suncorp.com.au/insurance/home use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.suncorp.com.au/insurance/home, whose canonical is https://www.suncorp.com.au/insurance/home.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_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
83 of 94 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,161 words of copy
The homepage carries about 1,161 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: “Get my documents” and “Contact & Support”.
10 calls to action
The homepage has 10 calls to action, for example “Get my documents”, “Contact & Support” and “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
45 cookies set on arrival
45Opening the homepage sets 45 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.
24 other companies contacted
Loading the homepage contacts 24 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 suncorp.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
- Framework
- Bootstrap
- Hosting
- Imperva
Company
- Founded
- 1996
- Headquarters
- Brisbane
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on suncorp.com.au, including 24 speed issues, 4 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.