Website review, no card needed
bondno9.com website review
Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 87 checks
This review found 38 issues worth fixing on bondno9.com, 16 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
80B- #47,084 of 120,066 reviewed websitesbeats 55%
- #31,285 of 68,040 online storesbeats 48%
- #30,089 of 62,009 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 105 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 118 ms |
| Jun 20, 2026 | 117 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 109 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 108 ms |
| Jul 25, 2026 | 108 ms |
| Aug 1, 2026 | 110 ms |
| Aug 8, 2026 | 110 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 105 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 104 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.5 s · 723 KiB17 images could be 723 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.
Signyfyd adds 1.4 s
1.4 sSignyfyd costs a phone 1.4 s of main-thread work and 265 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.
Main-thread work: 11.7 s
A phone's processor spends 11.7 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,263 HTML elements
The page has 5,263 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 (Signyfyd, ZenDesk and Shopify and others), adding 1.6 MB and 2.7 s of main-thread time.
Reduce unused JavaScript
150 ms · 499 KiBAbout 499 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
ZenDesk adds 538 ms
538 msZenDesk costs a phone 538 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 566 ms. During a long task the page ignores taps.
Render-blocking requests
400 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
Shopify adds 306 ms
306 msShopify costs a phone 306 ms of main-thread work and 425 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.
Accessibe Accessibility Overlay adds 272 ms
272 msAccessibe Accessibility Overlay costs a phone 272 ms of main-thread work and 254 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.
Use efficient cache lifetimes
129 KiB16 files are served with short cache lifetimes, so returning visitors download them again (129 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
10 KiB10 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.
Legacy JavaScript
4 KiBPolyfills for old browsers add 4 KiB JavaScript that modern phones do not need.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.7 s
20.7 sThe page becomes fully interactive after 20.7 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
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 105 ms to 104 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 537 ms
537 msReal visitors wait 537 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.4 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: 16.3 MB in 402 requests
16.3 MBYour homepage downloads 16.3 MB in 402 requests on a phone: media 11.0 MB (3), images 2.1 MB (42) and scripts 1.5 MB (83). Under 2 MB keeps phones on slow connections fast.
About 4.6 g of CO₂ per visit
4.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.63 g of CO₂e: 555.5 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
16 buttons without a name
16 buttons have no accessible name, so screen readers announce just “button”.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Links must have discernible text (3 elements)
Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.
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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 9 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “Bond No. 9 New York”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
353 internal links, 10 external
The homepage links to 353 pages on bondno9.com and 10 external pages.
6 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Shop Bond No 9. Making Scents of New York. Shop Luxury Fragrances, Lipsticks & Gifts. Complimentary Samples. Free Shipp…”.
Canonical URL set
The canonical URL is https://www.bondno9.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://www.bondno9.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 (1,981 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bondno9.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.bondno9.com/collections/a-collection-of-ouds and https://www.bondno9.com/pages/gift-services have no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.bondno9.com/pages/neighborhood/uptown, whose canonical is https://www.bondno9.com/collections/uptown. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://www.bondno9.com/pages/new-york-neighborhoods, https://www.bondno9.com/pages/neighborhood/uptown, https://www.bondno9.com/pages/neighborhood/downtown, https://www.bondno9.com/pages/neighborhood/new-york-parks, https://www.bondno9.com/pages/neighborhood/city-scent and https://www.bondno9.com/pages/neighborhood/beaches and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 94 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
44 small tap targets
44 of 82 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.”).
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”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 475 words of copy
The homepage carries about 475 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: “SHOP THE SCENT OF PEACE FOR ALL”.
9 calls to action
The homepage has 9 calls to action, for example “SHOP THE SCENT OF PEACE FOR ALL”, “Shop The Scent of Peace for All” and “CANDLES SHOP NOW”.
131 short forms
131 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
25 other companies contacted
Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 bondno9.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Gdpr Cookie Consent · Tms Prod V 71ff83e · Foursixty Shopify App · Freegifts · Bestpush · bogos.io · signifyd.com · shareasale.com · adroll.com · attn.tv · rakutenadvertising.io
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
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Hiring
- Hiring
- 2 open roles
- Job board
- careers page
Company
- Employees
- 190
- Founded
- 2003
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on bondno9.com, including 17 speed issues, 3 SEO issues and 2 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.