Website review, no card needed
corysadvantage.co.nz website review
Visit site (opens in a new tab)Reviewed 30 October 202663 issues · 100 checks
This review found 63 issues worth fixing on corysadvantage.co.nz, 31 of them high impact, across 100 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.5 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 200 ms |
| May 16, 2026 | 184 ms |
| May 23, 2026 | 185 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 203 ms |
| Jun 13, 2026 | 204 ms |
| Jun 20, 2026 | 224 ms |
| Jun 27, 2026 | 226 ms |
| Jul 4, 2026 | 200 ms |
| Jul 11, 2026 | 209 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 195 ms |
| Aug 8, 2026 | 211 ms |
| Aug 15, 2026 | 234 ms |
| Aug 22, 2026 | 228 ms |
| Aug 29, 2026 | 247 ms |
| Sep 5, 2026 | 244 ms |
| Sep 12, 2026 | 244 ms |
| Sep 19, 2026 | 261 ms |
| Sep 26, 2026 | 245 ms |
| Oct 3, 2026 | 219 ms |
| Oct 10, 2026 | 211 ms |
| Oct 17, 2026 | 194 ms |
| Oct 24, 2026 | 190 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.3 s
2.5 s
3.8 s
5.0 s
6.3 s
7.5 s
8.8 s
10.0 s
Speed
Use efficient cache lifetimes
15.8 s · 3.0 MB48 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).
Render-blocking requests
11.6 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 11.6 s.
Reduce unused JavaScript
8.0 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.0 s faster on a phone.
Improve image delivery
2.5 s · 513 KiB5 images could be 513 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Reduce unused CSS
2.3 s · 434 KiBAbout 434 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.
19,150 HTML elements
The page has 19,150 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Document request latency
1.0 sThe HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce initial server response time
1.0 sReduce initial server response time. Google estimates savings of 1.0 s on a phone.
Minify JavaScript
600 ms · 60 KiB60 KiB could be saved by minifying JavaScript.
Server response: 1.1 s
1.1 sYour server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
pdl.co.nz adds 49 ms
49 mspdl.co.nz costs a phone 49 ms of main-thread work and 345 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, rlets.com and pdl.co.nz and others), adding 729 KiB and 450 ms of main-thread time.
Legacy JavaScript
150 ms · 43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.
Minify CSS
106 KiB106 KiB could be saved by minifying CSS.
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.
1 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 590 ms of it running JavaScript. That is comfortably low.
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 LCP: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.7 s
2.7 sReal visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 12.6 s
12.6 sThe first text or image appears after 12.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.2 s
24.2 sYour largest element takes 24.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 18.2 s
18.2 sVisually, the page fills in at 18.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.3 s
24.3 sThe page becomes fully interactive after 24.3 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.395
0.395The layout shifts by 0.395 while loading, so content jumps under the reader's thumb. Good is under 0.1.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 230 ms
230 msScripts block taps and scrolling for 230 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 200 ms to 190 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 186 ms
186 msReal visitors wait 186 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.
Images and page weight
1 image over 500 KB
233_mobile_Become a Corys Cust TODAY(600 x 843 mm).png weighs 503 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.7 MB in 66 requests
3.7 MBYour homepage downloads 3.7 MB in 66 requests on a phone: scripts 2.0 MB (18), images 834 KiB (27) and stylesheets 465 KiB (5). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (666 KiB) are 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 far larger than shown
369 KiB1 image is downloaded at several times the size a phone draws it, for example 233_mobile_Become a Corys Cust TODAY(600 x 843 mm).png at 2,267 px wide, shown at 390 px. Resized copies would save about 369 KiB.
About 1.0 g of CO₂ per visit
1.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 124.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
15 images without alt text
15 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
37 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: 37 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
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (15 characters)
Your title is only 15 characters: “Corys Advantage”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 (218 characters)
Your meta description is 218 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.
4 links crawlers can't follow
4 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.
762 internal links, 4 external
The homepage links to 762 pages on corysadvantage.co.nz and 4 external pages.
1 checks passed
XML sitemap found
Your XML sitemap is reachable at https://corysadvantage.co.nz/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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://corysadvantage.co.nz/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
Other pages
1 page without a title
https://corysadvantage.co.nz/ajax/changeBranch has no <title>, so Google invents the link text in results.
3 pages share a title
/, https://corysadvantage.co.nz/products/scan and https://corysadvantage.co.nz/products/scan_add all use the title “Corys Advantage”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://corysadvantage.co.nz/ajax/changeBranch has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://corysadvantage.co.nz/products/scan and https://corysadvantage.co.nz/products/scan_add use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://corysadvantage.co.nz/ajax/changeBranch, https://corysadvantage.co.nz/products/scan, https://corysadvantage.co.nz/products/scan_add, https://corysadvantage.co.nz/cms/page/slug:electrical, https://corysadvantage.co.nz/cms/page/slug:data and https://corysadvantage.co.nz/cms/page/slug:lighting and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://corysadvantage.co.nz/ajax/changeBranch has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
9 pages slow to respond
https://corysadvantage.co.nz/products/scan, https://corysadvantage.co.nz/products/scan_add, https://corysadvantage.co.nz/cms/page/slug:data, https://corysadvantage.co.nz/cms/page/slug:lighting, https://corysadvantage.co.nz/cms/page/slug:safety and https://corysadvantage.co.nz/cms/page/slug:Utilities-and-Infrastructure and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
3 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
9 third-party cookies
9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
7 small tap targets
7 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Only about 84 words
The homepage has only about 84 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
6 checks passed
11 calls to action
The homepage has 11 calls to action, for example “Register”, “Scan to add to order” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
12 other companies contacted
Loading the homepage contacts 12 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 corysadvantage.co.nz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cello As Ap Cello Group Limited
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 63 issues on corysadvantage.co.nz, including 23 speed issues, 9 SEO issues and 4 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.