Website review, no card needed
honeybirdette.com website review
Visit site (opens in a new tab)Reviewed 19 November 202640 issues · 96 checks
This review found 40 issues worth fixing on honeybirdette.com, 13 of them high impact, across 96 checks. The most urgent: avoid multiple page redirects. 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
81B- #41,961 of 125,955 reviewed websitesbeats 61%
- #27,616 of 70,316 online storesbeats 54%
- #26,594 of 63,864 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.5 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 174 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 229 ms |
| Jun 27, 2026 | 224 ms |
| Jul 4, 2026 | 212 ms |
| Jul 11, 2026 | 186 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 148 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 165 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 168 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 157 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 162 ms |
| Oct 31, 2026 | 164 ms |
| Nov 7, 2026 | 165 ms |
| Nov 14, 2026 | 164 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
2.3 s
4.5 s
6.8 s
9.1 s
11.4 s
13.6 s
15.9 s
18.2 s
Speed
Avoid multiple page redirects
16.7 sThe page goes through 1 redirect before it starts loading, costing about 16.7 s. Link and advertise the final URL directly.
audioeye.com adds 5.5 s
5.5 saudioeye.com costs a phone 5.5 s of main-thread work and 632 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.
Reduce unused JavaScript
2.3 s · 1.5 MBAbout 1.5 MB 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.
Improve image delivery
2.0 s · 773 KiB25 images could be 773 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Main-thread work: 16.7 s
A phone's processor spends 16.7 s on main-thread work while loading, 10.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, ZenDesk and Forter and others), adding 26.4 MB and 6.2 s of main-thread time.
Shopify adds 69 ms
69 msShopify costs a phone 69 ms of main-thread work and 24.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.
Use efficient cache lifetimes
450 ms · 628 KiB28 files are served with short cache lifetimes, so returning visitors download them again (628 KiB).
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
ZenDesk adds 271 ms
271 msZenDesk costs a phone 271 ms of main-thread work and 481 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,317 HTML elements
The page has 2,317 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Forter adds 101 ms
101 msForter costs a phone 101 ms of main-thread work and 362 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.
Attentive adds 72 ms
72 msAttentive costs a phone 72 ms of main-thread work and 630 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.
Minify JavaScript
150 ms · 10 KiB10 KiB could be saved by minifying JavaScript.
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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
14 KiB14 KiB JavaScript is shipped twice across bundles.
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 25.1 s
25.1 sYour largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 16.5 s
16.5 sVisually, the page fills in at 16.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.4 s
40.4 sThe page becomes fully interactive after 40.4 s. Good is under 3.8 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 358 ms
358 msScripts block taps and scrolling for 358 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 174 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (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: 501 ms
501 msReal visitors wait 501 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 33.1 MB in 644 requests
33.1 MBYour homepage downloads 33.1 MB in 644 requests on a phone: media 23.8 MB (3), scripts 3.7 MB (184) and images 2.8 MB (45). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Jules-Emerald-VIDEO-BUFFER_MOBILE-38-2026-11-13.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).
1 image far larger than shown
65 KiB1 image is downloaded at several times the size a phone draws it, for example Piccolo_Black_2.jpg at 2,480 px wide, shown at 127 px. Resized copies would save about 65 KiB.
2 images below the first screen load straight away
2 images further down the page (186 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 9.4 g of CO₂ per visit
9.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.38 g of CO₂e: 1125.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (6 elements).
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Store and WebSite) but with 2 problems, for example “WebSite: missing name”.
82 internal links, 18 external
The homepage links to 82 pages on honeybirdette.com and 18 external pages.
7 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Shop luxury Honey Birdette lingerie online. Shop Push up bras, lace bras, briefs, thongs, loungewear, bridal lingerie a…”.
One H1 headline
Your main headline reads: “Honey Birdette AU”.
Title: 55 characters
Your title is a healthy 55 characters: “Honey Birdette | Luxury Lingerie, Bras, Thongs & Briefs”.
Canonical URL set
The canonical URL is https://www.honeybirdette.com/.
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://www.honeybirdette.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, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (404 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.honeybirdette.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://www.honeybirdette.com/pages/christmas-gifting, https://www.honeybirdette.com/collections/apres, https://www.honeybirdette.com/pages/the-honey-club and https://www.honeybirdette.com/pages/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.honeybirdette.com/pages/the-honey-club and https://www.honeybirdette.com/pages/wishlist have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.honeybirdette.com/collections/apres 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 33 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.
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 15 pages that loaded have a <title>.
Best practices
48 small tap targets
48 of 139 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.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to execute 'appendChild' on 'Node': Unexpected token '}'”.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 383 words of copy
The homepage carries about 383 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop now on {store}”, “Icon of plus outline Shop this look” and “Contact Us”.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 1 more (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.
51 cookies set on arrival
51Opening the homepage sets 51 cookies, 2 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.
51 other companies contacted
Loading the homepage contacts 51 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 honeybirdette.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Youpay Cart Sharing · Attentive · Okendo · Amd Sale Scheduler · Youpay App · Loop Returns · Gdpr Backpack · Back In Stock · cloudfront.net
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
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Sydney
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on honeybirdette.com, including 18 speed issues, 1 SEO issue and 5 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.