Website review, no card needed

flyingbark.com.au logo

flyingbark.com.au website review

Visit site (opens in a new tab)Reviewed 20 November 202642 issues · 83 checks

This review found 42 issues worth fixing on flyingbark.com.au, 10 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
3.1 s2.6 sMay 30Nov 142.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.7 s
Jun 13, 20262.6 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20263.0 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Oct 31, 20262.9 s
Nov 7, 20263.0 s
Nov 14, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
105 ms89 msMay 30Nov 1494 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202691 ms
Jun 6, 202693 ms
Jun 13, 202691 ms
Jun 20, 202695 ms
Jun 27, 202696 ms
Jul 4, 202698 ms
Jul 11, 2026100 ms
Jul 18, 2026101 ms
Jul 25, 2026103 ms
Aug 1, 202698 ms
Aug 8, 202696 ms
Aug 15, 202694 ms
Aug 22, 202694 ms
Aug 29, 202695 ms
Sep 5, 202696 ms
Sep 12, 202696 ms
Sep 19, 202697 ms
Sep 26, 2026100 ms
Oct 3, 202696 ms
Oct 10, 202696 ms
Oct 17, 202694 ms
Oct 24, 202694 ms
Oct 31, 202693 ms
Nov 7, 202694 ms
Nov 14, 202694 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 flyingbark.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. flyingbark.com.au at 0.4 s0.4 s
  2. flyingbark.com.au at 0.8 s0.8 s
  3. flyingbark.com.au at 1.1 s1.1 s
  4. flyingbark.com.au at 1.5 s1.5 s
  5. flyingbark.com.au at 1.9 s1.9 s
  6. flyingbark.com.au at 2.3 s2.3 s
  7. flyingbark.com.au at 2.6 s2.6 s
  8. flyingbark.com.au at 3.0 s3.0 s

Speed

9 to fix60
  • Reduce unused JavaScript

    1.9 s · 418 KiB

    About 418 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Render-blocking requests

    1.8 s

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

  • Improve image delivery

    150 ms · 7.4 MB

    57 images could be 7.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Squarespace, weglot.com and sqspcdn.com and others), adding 9.6 MB and 493 ms of main-thread time.

  • Mobile performance score: 60

    60/100

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

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 8.4 MB 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.

  • Reduce unused CSS

    600 ms · 133 KiB

    About 133 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Squarespace adds 407 ms

    407 ms

    Squarespace costs a phone 407 ms of main-thread work and 1,019 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.

  • 2,470 HTML elements

    The page has 2,470 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    33 KiB

    Polyfills for old browsers add 33 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.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 673 ms of it running JavaScript. That is comfortably low.

  • Server response: 76 ms

    76 ms

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

Core Web Vitals

10 to fix67
  • 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 FCP: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 10.7 s

    10.7 s

    Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “TFOS_e106 1.png”.

  • Time to Interactive: 10.8 s

    10.8 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user TTFB: 887 ms

    887 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • Total Blocking Time: 302 ms

    302 ms

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

  • 1 image without width and height

    1 image 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 91 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

3 checks passed
  • Real-user INP: 106 ms

    106 ms

    Real visitors wait 106 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix48
  • Page weight: 9.7 MB in 121 requests

    9.7 MB

    Your homepage downloads 9.7 MB in 121 requests on a phone: images 8.3 MB (58), scripts 974 KiB (41) and stylesheets 173 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    TFOS_e106+1.png weighs 566 KiB. On a phone connection a single image that size takes seconds.

  • 24 images below the first screen load straight away

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

  • About 2.8 g of CO₂ per visit

    2.76 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 9498
  • 3 tap targets too small

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 61 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

5 to fixGoogle 8572
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (23 characters)

    Your title is only 23 characters: “Flying Bark Productions”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 H1 headlines

    There are 4 <h1> headlines (“We create the nostalgia of tomorrow.”, “Sydney - Los Angeles - Madrid -” and “Sydney - Los Angeles - Madrid - Sydney - Los Ange…”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/676f83f4f2908e531b2…”.

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

  • 461 internal links, 46 external

    The homepage links to 461 pages on flyingbark.com.au and 46 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.flyingbark.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.flyingbark.com.au/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, url, logo and description. 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://www.flyingbark.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 (3,513 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix69
  • 1 linked page hidden from search

    https://www.flyingbark.com.au/careers is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.flyingbark.com.au/released and https://www.flyingbark.com.au/PROJECTS all use the title “Released Projects — Flying Bark Productions”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages without a meta description

    https://www.flyingbark.com.au/coming-soon, https://www.flyingbark.com.au/services, https://www.flyingbark.com.au/team, https://www.flyingbark.com.au/lifeatflyingbark, https://www.flyingbark.com.au/animation-101 and https://www.flyingbark.com.au/careers and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.flyingbark.com.au/released and https://www.flyingbark.com.au/PROJECTS use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.flyingbark.com.au/PROJECTS, whose canonical is https://www.flyingbark.com.au/released. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://www.flyingbark.com.au/released, https://www.flyingbark.com.au/team, https://www.flyingbark.com.au/PROJECTS, https://www.flyingbark.com.au/careers, https://www.flyingbark.com.au/released/v/avatar-aang-the-last-airbender-2026 and https://www.flyingbark.com.au/released/animation-services and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.flyingbark.com.au/team 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 80 small tap targets

    80 of 145 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 “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/676f83f4f2908e531b249f63/57/5c5a…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 3 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 758 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: “Learn more >” and “100% Wolf: Book of Hath (2023)”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “How to Apply”, “Learn more >” and “100% Wolf: Book of Hath (2023)”.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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, 1 of them by other companies (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 flyingbark.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
Squarespace
Hosting
Squarespace

Hiring

Hiring
13 open roles
Teams
Animation 2D (3), Animation 3D (2), Lighting & Compositing (2), CFX (1)
Job board
bamboohr

Company

Founded
1967
Headquarters
Sydney

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on flyingbark.com.au, including 19 speed issues, 5 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

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