Website review, no card needed
hazeldenes.com.au website review
Visit site (opens in a new tab)Reviewed 30 October 202634 issues · 78 checks
This review found 34 issues worth fixing on hazeldenes.com.au, 16 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 99 ms |
| May 16, 2026 | 103 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 90 ms |
| Jul 11, 2026 | 92 ms |
| Jul 18, 2026 | 93 ms |
| Jul 25, 2026 | 97 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 105 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 95 ms |
| Sep 12, 2026 | 92 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 98 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 94 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.5 s
1.0 s
1.5 s
2.1 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
Improve image delivery
10.8 s · 2.1 MB5 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.8 s faster on a phone.
Use efficient cache lifetimes
2.7 s · 574 KiB25 files are served with short cache lifetimes, so returning visitors download them again (574 KiB).
Render-blocking requests
3.0 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Reduce unused JavaScript
1.1 s · 198 KiBAbout 198 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Reduce unused CSS
900 ms · 197 KiBAbout 197 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 160 KiB and 78 ms of main-thread time.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 250 ms of it running JavaScript. That is comfortably low.
Server response: 189 ms
189 msYour server sent the HTML in 189 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.
Real-user LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 20.0 s
20.0 sYour largest element takes 20.0 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: 20.0 s
20.0 sThe page becomes fully interactive after 20.0 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 99 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 99 ms
99 msReal visitors wait 99 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
Splash-page.jpg weighs 860 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
860 KiB1 image is downloaded at several times the size a phone draws it, for example Splash-page.jpg at 2,000 px wide, shown at 2 px. Resized copies would save about 860 KiB.
Page weight: 3.6 MB in 30 requests
3.6 MBYour homepage downloads 3.6 MB in 30 requests on a phone: images 2.9 MB (7), scripts 403 KiB (9) and stylesheets 217 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (860 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.
About 1.0 g of CO₂ per visit
1.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.8 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
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.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 3 failed. 1 more 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.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
51 internal links, 8 external
The homepage links to 51 pages on hazeldenes.com.au and 8 external pages.
7 checks passed
Meta description: 117 characters
Your meta description is 117 characters: “Premium quality chicken since 1938. We pride ourselves on providing the highest quality Australian chicken available.”.
Title: 57 characters
Your title is a healthy 57 characters: “Premium Quality Chicken | Australian Chicken | Since 1938”.
Canonical URL set
The canonical URL is https://hazeldenes.com.au/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://hazeldenes.com.au/sitemap_index.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://hazeldenes.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 (330 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://hazeldenes.com.au/author/karengodfrey_okv7wlz1 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://hazeldenes.com.au/range and https://hazeldenes.com.au/high-quality-chicken-products all use the title “High Quality Chicken | Australian Chicken | Since 1938”. 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://hazeldenes.com.au/author/karengodfrey_okv7wlz1 has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://hazeldenes.com.au/range, https://hazeldenes.com.au/stockists, https://hazeldenes.com.au/chicken-recipes, https://hazeldenes.com.au/high-quality-chicken-products, https://hazeldenes.com.au/animal-welfare and https://hazeldenes.com.au/join-our-team and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
3 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
14 small tap targets
14 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 165 words
The homepage has only about 165 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
6 calls to action
The homepage has 6 calls to action, for example “Where To Buy”, “Join Our Team” and “CONTACT”.
Analytics in place
Analytics detected: Google Analytics.
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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
2 other companies contacted
Loading the homepage contacts 2 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 hazeldenes.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
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on hazeldenes.com.au, including 14 speed issues, 2 SEO issues and 3 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.