Website review, no card needed
threebirdnest.com website review
Visit site (opens in a new tab)Reviewed 3 November 202641 issues · 86 checks
This review found 41 issues worth fixing on threebirdnest.com, 14 of them high impact, across 86 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- #81,247 of 109,201 reviewed websitesbeats 22%
- #50,721 of 61,819 online storesbeats 15%
- #47,552 of 56,389 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 944 ms |
| May 23, 2026 | 927 ms |
| May 30, 2026 | 916 ms |
| Jun 6, 2026 | 928 ms |
| Jun 13, 2026 | 978 ms |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 179 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 176 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 174 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 186 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 184 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 187 ms |
| Oct 24, 2026 | 188 ms |
| Oct 31, 2026 | 184 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.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.7 s
8.7 s
Speed
Reduce unused JavaScript
1.1 s · 990 KiBAbout 990 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.
audioeye.com adds 1.6 s
1.6 saudioeye.com costs a phone 1.6 s of main-thread work and 316 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 5.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
4.1 MB90 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
3.8 MB163 files are served with short cache lifetimes, so returning visitors download them again (3.8 MB).
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, ZenDesk and Google Tag Manager and others), adding 1.8 MB and 2.9 s of main-thread time.
Reduce initial server response time
621 msReduce initial server response time. Google estimates savings of 621 ms on a phone.
Document request latency
600 msThe HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.
ZenDesk adds 402 ms
402 msZenDesk costs a phone 402 ms of main-thread work and 476 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 304 ms
304 msGoogle Tag Manager costs a phone 304 ms of main-thread work and 203 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,310 HTML elements
The page has 2,310 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Optanon adds 122 ms
122 msOptanon costs a phone 122 ms of main-thread work and 322 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.
Server response: 721 ms
721 msYour server takes 721 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 214 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
79 KiBPolyfills for old browsers add 79 KiB JavaScript that modern phones do not need.
Reduce unused CSS
78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
6 KiB6 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 KiB2 KiB could be saved by minifying CSS.
Core Web Vitals
Largest Contentful Paint: 10.3 s
10.3 sYour largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Season to Gather”.
Speed Index: 15.8 s
15.8 sVisually, the page fills in at 15.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 28.0 s
28.0 sThe page becomes fully interactive after 28.0 s. Good is under 3.8 s.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 179 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 183 ms
183 msReal visitors wait 183 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 460 ms
460 msReal visitors wait 460 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.093
0.093The layout barely moves while loading (CLS 0.093, good is under 0.1).
Images and page weight
Page weight: 12.9 MB in 447 requests
12.9 MBYour homepage downloads 12.9 MB in 447 requests on a phone: images 8.6 MB (233), scripts 2.4 MB (100) and fonts 1.1 MB (37). Under 2 MB keeps phones on slow connections fast.
18 images far larger than shown
1,002 KiB18 images are downloaded at several times the size a phone draws them, for example HP_Hero_2x1_Left_720x550_65726e92-c3c8-4575-bf1e-42ce6560ccd at 1,440 px wide, shown at 390 px. Resized copies would save about 1,002 KiB.
An image on the first screen is lazy-loaded
HP_Hero_2x1_Left_720x550_65726e92-c3c8-4575-bf1e-42ce6560ccd 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).
1 image in older formats
1 image (75 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 3.7 g of CO₂ per visit
3.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.66 g of CO₂e: 439.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 81 images in the HTML carry an alt attribute.
17 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 0 failed. 4 mores 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.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.threebirdnest.com/fast-image/fl_progressive:steep/shopify/1/0179/2309/fi…”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.threebirdnest.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at threebirdnest.com/robots.txt, the first file search crawlers ask for.
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.
264 internal links, 16 external
The homepage links to 264 pages on threebirdnest.com and 16 external pages.
3 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Express you free spirit with affordable boho outfits from 3BN! We offer a huge selection of comfy, flattering bohemian …”.
Title: 62 characters
Your title is a healthy 62 characters: “Women's Clothing, Free-Spirited Boho Outfits, Bohemian Clothes”.
Canonical URL set
The canonical URL is https://www.threebirdnest.com/.
AI search readiness
3 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,143 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.threebirdnest.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
/ and https://www.threebirdnest.com/content/gift-guide all use the title “Women's Clothing, Free-Spirited Boho Outfits, Bohemian Clothes”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://www.threebirdnest.com/content/gift-guide, https://www.threebirdnest.com/collections/winter, https://www.threebirdnest.com/collections/seasonal-classics, https://www.threebirdnest.com/collections/fall-occasions and https://www.threebirdnest.com/collections/moto-boho use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://www.threebirdnest.com/collections/clothing, https://www.threebirdnest.com/content/gift-guide, https://www.threebirdnest.com/collections/whats-new, https://www.threebirdnest.com/collections/back-in-stock, https://www.threebirdnest.com/collections/best-sellers and https://www.threebirdnest.com/collections/sleepwear and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.threebirdnest.com/collections/fall-occasions, https://www.threebirdnest.com/collections/boho, https://www.threebirdnest.com/collections/moto-boho and https://www.threebirdnest.com/collections/teacher-approved-styles took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 178 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/instagram/22/18067116200711622/standard_resolution.jpg?format=webp&fit=crop&height=352&width=352.
37 small tap targets
37 of 89 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.”).
1 third-party cookie
1 third-party cookie is 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 (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 842 words of copy
The homepage carries about 842 words of visible text.
2 checks passed
81 calls to action
The homepage has 81 calls to action, for example “Shop This Week's Drop >”, “Shop OOTW >” and “Shop New”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and TikTok Pixel.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (OneTrust) 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 (measured from a US location before any click).
58 other companies contacted
Loading the homepage contacts 58 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 threebirdnest.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on threebirdnest.com, including 20 speed issues, 6 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.