Website review, no card needed

birdinhand.com.au logo

birdinhand.com.au website review

Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 92 checks

This review found 43 issues worth fixing on birdinhand.com.au, 12 of them high impact, across 92 checks. The most urgent: 9 images over 500 KB. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.4 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.8 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
105 ms87 msMay 16Oct 31103 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202691 ms
May 23, 202691 ms
May 30, 202689 ms
Jun 6, 202689 ms
Jun 13, 202689 ms
Jun 20, 202689 ms
Jun 27, 202691 ms
Jul 4, 202691 ms
Jul 11, 202692 ms
Jul 18, 202690 ms
Jul 25, 202693 ms
Aug 1, 202694 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202696 ms
Aug 29, 202696 ms
Sep 5, 202695 ms
Sep 12, 202696 ms
Sep 19, 202695 ms
Sep 26, 202695 ms
Oct 3, 202695 ms
Oct 10, 202694 ms
Oct 17, 202699 ms
Oct 24, 2026103 ms
Oct 31, 2026103 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

Full-page screenshot of birdinhand.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. birdinhand.com.au at 1.3 s1.3 s
  2. birdinhand.com.au at 2.5 s2.5 s
  3. birdinhand.com.au at 3.8 s3.8 s
  4. birdinhand.com.au at 5.0 s5.0 s
  5. birdinhand.com.au at 6.3 s6.3 s
  6. birdinhand.com.au at 7.6 s7.6 s
  7. birdinhand.com.au at 8.8 s8.8 s
  8. birdinhand.com.au at 10.1 s10.1 s

Speed

11 to fix73
  • Render-blocking requests

    3.3 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

  • Improve image delivery

    14.4 MB

    7 images could be 14.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.8 MB and 1.1 s of main-thread time.

  • Mobile performance score: 73

    73/100

    Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.

  • Font display

    900 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).

  • Reduce unused JavaScript

    761 KiB

    About 761 KiB of JavaScript is downloaded but never used on this page.

  • Google CDN adds 451 ms

    451 ms

    Google CDN costs a phone 451 ms of main-thread work and 736 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.

  • Main-thread work: 3.4 s

    A phone's processor spends 3.4 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Tag Manager adds 237 ms

    237 ms

    Google Tag Manager costs a phone 237 ms of main-thread work and 460 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.

  • Use efficient cache lifetimes

    255 KiB

    23 files are served with short cache lifetimes, so returning visitors download them again (255 KiB).

  • Klaviyo adds 157 ms

    157 ms

    Klaviyo costs a phone 157 ms of main-thread work and 310 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.

  • 15 long tasks on the main thread

    15 long tasks block the main thread while loading, the longest for 155 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    49 KiB

    Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • 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.

  • Speed Index: 18.0 s

    18.0 s

    Visually, the page fills in at 18.0 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 48.8 s

    48.8 s

    The page becomes fully interactive after 48.8 s. Good is under 3.8 s.

  • Real-user TTFB: 860 ms

    860 ms

    Real visitors wait 860 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 479 ms

    479 ms

    Scripts block taps and scrolling for 479 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.4 s

    2.4 s

    The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

  • 18 images without width and height

    18 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 13% slower for real visitors

    +13%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 91 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 102 ms

    102 ms

    Real visitors wait 102 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • Cumulative Layout Shift: 0.003

    0.003

    The layout barely moves while loading (CLS 0.003, good is under 0.1).

Images and page weight

5 to fix18
  • 9 images over 500 KB

    9 images weigh 104.9 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    101.1 MB

    9 images are downloaded at several times the size a phone draws them, for example Bird-in-Hand-Autumn-2024-11.jpg at 8,192 px wide, shown at 390 px. Resized copies would save about 101.1 MB.

  • Page weight: 17.3 MB in 159 requests

    17.3 MB

    Your homepage downloads 17.3 MB in 159 requests on a phone: images 14.7 MB (26), scripts 1.9 MB (60) and other files 398 KiB (50). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (104.9 MB) 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.

  • 9 images below the first screen load straight away

    9 images further down the page (104.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.9 g of CO₂ per visit

    4.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.90 g of CO₂e: 587.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

8 to fixGoogle 8188
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • 11 images without alt text

    11 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9280
  • Title is short (19 characters)

    Your title is only 19 characters: “Home - Bird in Hand”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Bird in Hand”, “Bird in Hand” and “Contact”). One clear main headline is easier for people and search engines.

  • Meta description is long (165 characters)

    Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 19 internal links, 38 external

    The homepage links to 19 pages on birdinhand.com.au and 38 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://birdinhand.com.au/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://birdinhand.com.au/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://birdinhand.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 (1,131 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 12 pages without a meta description

    https://birdinhand.com.au/visit-adelaide-hills, https://birdinhand.com.au/bird-in-hand-tasmania, https://birdinhand.com.au/adelaide-hills, https://birdinhand.com.au/royal-tasmanian-botanic-gardens, https://birdinhand.com.au/tamar-valley and https://birdinhand.com.au/about and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://birdinhand.com.au/bird-in-hand-tasmania has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://birdinhand.com.au/terms-conditions took over 3 s to send its HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 12 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 5491
  • 3 third-party cookies

    3 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 (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

    39 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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,094 words of copy

    The homepage carries about 1,094 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 Wine” and “Subscribe”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”, “Contact Info” and “Shop Wine”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 4 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

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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 birdinhand.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 | Google Tag Manager
Hosting
Google Cloud

Company

Headquarters
Woodside

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on birdinhand.com.au, including 18 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25