Website review, no card needed

bydeeaus.com logo

bydeeaus.com website review

Visit site (opens in a new tab)Reviewed 4 November 202639 issues · 91 checks

This review found 39 issues worth fixing on bydeeaus.com, 17 of them high impact, across 91 checks. The most urgent: page weight: 38.8 MB in 384 requests. 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
4.1 s3.6 sMay 16Oct 313.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.0 s
May 23, 20263.9 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20263.8 s
Jun 27, 20263.9 s
Jul 4, 20263.8 s
Jul 11, 20263.9 s
Jul 18, 20263.8 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20264.0 s
Oct 31, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
155 ms140 msMay 16Oct 31144 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026142 ms
May 23, 2026144 ms
May 30, 2026144 ms
Jun 6, 2026147 ms
Jun 13, 2026145 ms
Jun 20, 2026145 ms
Jun 27, 2026145 ms
Jul 4, 2026145 ms
Jul 11, 2026146 ms
Jul 18, 2026145 ms
Jul 25, 2026145 ms
Aug 1, 2026146 ms
Aug 8, 2026148 ms
Aug 15, 2026151 ms
Aug 22, 2026152 ms
Aug 29, 2026153 ms
Sep 5, 2026147 ms
Sep 12, 2026146 ms
Sep 19, 2026145 ms
Sep 26, 2026145 ms
Oct 3, 2026145 ms
Oct 10, 2026146 ms
Oct 17, 2026145 ms
Oct 24, 2026144 ms
Oct 31, 2026144 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 bydeeaus.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bydeeaus.com at 0.5 s0.5 s
  2. bydeeaus.com at 1.1 s1.1 s
  3. bydeeaus.com at 1.6 s1.6 s
  4. bydeeaus.com at 2.1 s2.1 s
  5. bydeeaus.com at 2.6 s2.6 s
  6. bydeeaus.com at 3.2 s3.2 s
  7. bydeeaus.com at 3.7 s3.7 s
  8. bydeeaus.com at 4.2 s4.2 s

Speed

12 to fix41
  • Reduce unused JavaScript

    2.3 s · 683 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 10.9 s

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

  • Mobile performance score: 41

    41/100

    Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,605 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Unpkg, Google Tag Manager and Yotpo and others), adding 1.7 MB and 1.7 s of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 1.2 MB

    37 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Improve image delivery

    150 ms · 701 KiB

    24 images could be 701 KiB 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.

  • Unpkg adds 489 ms

    489 ms

    Unpkg costs a phone 489 ms of main-thread work and 20 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.

  • Google Tag Manager adds 423 ms

    423 ms

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

  • Reduce unused CSS

    300 ms · 73 KiB

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

  • Shopify adds 182 ms

    182 ms

    Shopify costs a phone 182 ms of main-thread work and 383 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.

  • Legacy JavaScript

    250 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 17 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

9 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 LCP: 4.9 s

    4.9 s

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

  • Real-user FCP: 8.8 s

    8.8 s

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

  • Largest Contentful Paint: 27.6 s

    27.6 s

    Your largest element takes 27.6 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: 31.8 s

    31.8 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Total Blocking Time: 738 ms

    738 ms

    Scripts block taps and scrolling for 738 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

    +1%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user INP: 188 ms

    188 ms

    Real visitors wait 188 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 TTFB: 594 ms

    594 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix69
  • Page weight: 38.8 MB in 384 requests

    38.8 MB

    Your homepage downloads 38.8 MB in 384 requests on a phone: media 25.0 MB (3), images 10.3 MB (50) and scripts 1.9 MB (114). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1_FULLSIZED_CROPPED_c331bbda-c1ba-41d8-bd6a-43958232940d.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images below the first screen load straight away

    4 images further down the page (141 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 11.0 g of CO₂ per visit

    11.00 g

    By the Sustainable Web Design model, a visit to your homepage emits about 11.00 g of CO₂e: 1319.8 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

6 to fixGoogle 8492
  • Unlabelled dropdowns

    3 dropdowns have no label.

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

  • 12 images without alt text

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

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

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

  • 35 links without text

    35 visible links have no text or label, so screen readers cannot say where they go.

  • 3 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

Google 92100
  • 357 internal links, 7 external

    The homepage links to 357 pages on bydeeaus.com and 7 external pages.

8 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Bydee is an Australian swimwear brand, formed in 2013. Browse Australian swimwear, bikinis & one pieces online. Sign up…”.

  • One H1 headline

    Your main headline reads: “Bydee”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Bydee AU | Australian Swimwear & Bikinis”.

  • Canonical URL set

    The canonical URL is https://bydeeaus.com/.

  • Structured data in place

    Structured data found: BreadcrumbList and Organization.

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

AI search readiness

100
  • No llms.txt

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://bydeeaus.com/collections/cartolina is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://bydeeaus.com/collections/scorpio-edit has no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://bydeeaus.com/collections/cartolina, https://bydeeaus.com/collections/scorpio-edit, https://bydeeaus.com/collections/bikini-tops, https://bydeeaus.com/collections/triangle-bikini-tops, https://bydeeaus.com/collections/string-bikini-tops and https://bydeeaus.com/collections/bandeau-bikini-tops and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://bydeeaus.com/collections/scorpio-edit, https://bydeeaus.com/collections/bikini-tops, https://bydeeaus.com/collections/triangle-bikini-tops, https://bydeeaus.com/collections/string-bikini-tops, https://bydeeaus.com/collections/bandeau-bikini-tops and https://bydeeaus.com/collections/bottoms and 1 other have 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 118 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 20 small tap targets

    20 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 914 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 43 calls to action

    The homepage has 43 calls to action, for example “Shop All Bikini Tops”, “Shop All Bikini Bottoms” and “Shop All One Piece Swimwear”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks and 6 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 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.

  • 52 other companies contacted

    Loading the homepage contacts 52 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 bydeeaus.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Okendo · Yotpo Loyalty Rewards · Klaviyo Email Marketing Sms · Triplewhale · Simple Affiliate · Helium Customer Fields · Tolstoy · Swish Wishlist King · Veeper Stop Coupon Leaks · cloudfront.net · zonos.com · hiplee.com · gorgias.chat · 9gtb.com · cfjump.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Headquarters
Alexandria

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on bydeeaus.com, including 21 speed 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

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