Website review, no card needed
birdandbe.com website review
Visit site (opens in a new tab)Reviewed 6 November 202639 issues · 91 checks
This review found 39 issues worth fixing on birdandbe.com, 16 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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
73C- #86,721 of 116,725 reviewed websitesbeats 22%
- #54,818 of 66,810 online storesbeats 15%
- #51,396 of 60,951 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 159 ms |
| May 23, 2026 | 160 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 163 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 175 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 170 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 175 ms |
| Sep 19, 2026 | 175 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 174 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 169 ms |
| Oct 24, 2026 | 169 ms |
| Oct 31, 2026 | 170 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.6 s
3.1 s
4.7 s
6.3 s
7.8 s
9.4 s
11.0 s
12.5 s
Speed
Reduce unused JavaScript
6.2 s · 2.5 MBAbout 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 1.9 MB47 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Main-thread work: 24.2 s
A phone's processor spends 24.2 s on main-thread work while loading, 9.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Avoid multiple page redirects
2.4 sThe page goes through 2 redirects before it starts loading, costing about 2.4 s. Link and advertise the final URL directly.
Mobile performance score: 26
26/100Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,812 HTML elements
The page has 4,812 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 (Google Tag Manager, route.com and alia-prod.com and others), adding 5.1 MB and 3.4 s of main-thread time.
Google Tag Manager adds 973 ms
973 msGoogle Tag Manager costs a phone 973 ms of main-thread work and 1.2 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.
route.com adds 623 ms
623 msroute.com costs a phone 623 ms of main-thread work and 1.1 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.
Render-blocking requests
700 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Shopify adds 442 ms
442 msShopify costs a phone 442 ms of main-thread work and 651 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.
alia-prod.com adds 456 ms
456 msalia-prod.com costs a phone 456 ms of main-thread work and 468 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.
Duplicated JavaScript
486 KiB486 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
300 ms · 137 KiBPolyfills for old browsers add 137 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
300 ms · 91 KiBAbout 91 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 330 ms. During a long task the page ignores taps.
Clarity adds 283 ms
283 msClarity costs a phone 283 ms of main-thread work and 29 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.
Document request latency
100 msThe HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Improve image delivery
45 KiB7 images could be 45 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
6 KiB6 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 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.
Largest Contentful Paint: 27.3 s
27.3 sYour largest element takes 27.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 26.5 s
26.5 sVisually, the page fills in at 26.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 58.1 s
58.1 sThe page becomes fully interactive after 58.1 s. Good is under 3.8 s.
Total Blocking Time: 2.6 s
2.6 sScripts block taps and scrolling for 2.6 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Cumulative Layout Shift: 0.125
0.125The layout shifts by 0.125 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 159 ms to 170 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-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 167 ms
167 msReal visitors wait 167 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 654 ms
654 msReal visitors wait 654 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 10.8 MB in 939 requests
10.8 MBYour homepage downloads 10.8 MB in 939 requests on a phone: scripts 6.5 MB (249), other files 2.0 MB (457) and images 801 KiB (113). Under 2 MB keeps phones on slow connections fast.
About 3.1 g of CO₂ per visit
3.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.06 g of CO₂e: 366.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA attributes must conform to valid values (4 elements)
ARIA attributes must conform to valid values: 4 elements on the page fail this check, rated critical by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 178 images in the HTML carry an alt attribute.
54 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: 54 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Bird&Be - Doctor-Formulated Prenatals, Fertility Supplements & Tests”.
Meta description is long (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
242 internal links, 30 external
The homepage links to 242 pages on birdandbe.com and 30 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Start now to be 2027 ready”.
Canonical URL set
The canonical URL is https://birdandbe.com/.
Structured data in place
Structured data found: Organization 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://birdandbe.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,363 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://birdandbe.com/llms.txt (68 KiB, 332 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://birdandbe.com/pages/when-to-take-a-pregnancy-test is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.
6 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 meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 broken images
5 images failed to load on a phone, for example https://files.alia-prod.com/14752/e0897b842cb53931.webp.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
110 of 132 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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,572 words of copy
The homepage carries about 1,572 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”.
61 calls to action
The homepage has 61 calls to action, for example “Shop”, “Ovarian Reserve Screening Test” and “Shop By Phase”.
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: 147 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
15 trackers load before any consent
15Before a visitor clicks anything, the page loads Amplitude, Criteo, Google Ads, Google Analytics and Google Tag Manager and 10 mores (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
38 cookies set on arrival
38Opening the homepage sets 38 cookies, 1 of them by other companies (measured from a US location before any click).
78 other companies contacted
Loading the homepage contacts 78 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Termly
A consent management tool (Termly) loads with the page.
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 birdandbe.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 22 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Microsoft Clarity · Sami Product Labels · Elevar Conversion Tracking · Instant Ai Page Builder · Triplewhale · Judge Me Reviews · Popsixle · Creatorcommerce Co Branding · Route Protection Tracking · Cc Cc Shopify App · Quick Announcement Bar Prod · Freegifts · Restockrocket · bogos.io · hextom.com · ecardwidget.com · huracdn.com · socialsnowball.io · amazonaws.com · goaffpro.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
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 3 open roles
- Teams
- Customer Experience (1)
- Job board
- breezy
- Careers page
- bird-be.breezy.hr (opens in a new tab)
Company
- Headquarters
- Toronto
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 birdandbe.com, including 26 speed issues, 2 SEO issues and 1 conversion gap. 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.