Website review, no card needed
olfactorynyc.com website review
Visit site (opens in a new tab)Reviewed 20 November 202645 issues · 92 checks
This review found 45 issues worth fixing on olfactorynyc.com, 14 of them high impact, across 92 checks. The most urgent: page weight: 18.4 MB in 416 requests. 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
77C- #68,944 of 124,235 reviewed websitesbeats 39%
- #44,599 of 69,824 online storesbeats 31%
- #42,407 of 63,500 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 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 | 275 ms |
| Jun 6, 2026 | 261 ms |
| Jun 13, 2026 | 361 ms |
| Jun 20, 2026 | 387 ms |
| Jun 27, 2026 | 311 ms |
| Jul 4, 2026 | 296 ms |
| Jul 11, 2026 | 479 ms |
| Jul 18, 2026 | 446 ms |
| Jul 25, 2026 | 396 ms |
| Aug 1, 2026 | 437 ms |
| Aug 8, 2026 | 426 ms |
| Aug 15, 2026 | 430 ms |
| Aug 22, 2026 | 383 ms |
| Aug 29, 2026 | 299 ms |
| Sep 5, 2026 | 296 ms |
| Sep 12, 2026 | 453 ms |
| Sep 19, 2026 | 471 ms |
| Sep 26, 2026 | 380 ms |
| Oct 3, 2026 | 358 ms |
| Oct 10, 2026 | 408 ms |
| Oct 17, 2026 | 452 ms |
| Oct 24, 2026 | 385 ms |
| Oct 31, 2026 | 389 ms |
| Nov 7, 2026 | 393 ms |
| Nov 14, 2026 | 410 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.8 s
1.7 s
2.5 s
3.4 s
4.2 s
5.1 s
5.9 s
6.8 s
Speed
Render-blocking requests
1.4 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 2.8 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 (Shopify, zotabox.com and Klaviyo and others), adding 2.4 MB and 1.3 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
50 ms · 860 KiB6 images could be 860 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Shopify adds 346 ms
346 msShopify costs a phone 346 ms of main-thread work and 678 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.
zotabox.com adds 294 ms
294 mszotabox.com costs a phone 294 ms of main-thread work and 576 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
338 KiB36 files are served with short cache lifetimes, so returning visitors download them again (338 KiB).
Klaviyo adds 257 ms
257 msKlaviyo costs a phone 257 ms of main-thread work and 644 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 320 ms. During a long task the page ignores taps.
2,748 HTML elements
The page has 2,748 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
azurefd.net adds 68 ms
68 msazurefd.net costs a phone 68 ms of main-thread work and 315 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
142 KiBAbout 142 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
86 KiBPolyfills for old browsers add 86 KiB JavaScript that modern phones do not need.
Minify JavaScript
20 KiB20 KiB could be saved by minifying JavaScript.
Minify CSS
7 KiB7 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: 28 ms
28 msYour server sent the HTML in 28 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.
Time to Interactive: 33.7 s
33.7 sThe page becomes fully interactive after 33.7 s. Good is under 3.8 s.
Largest Contentful Paint: 8.4 s
8.4 sYour largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video Cover”.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user INP: 279 ms
279 msReal visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 50% slower for real visitors
+50%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 275 ms to 410 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 317 ms
317 msScripts block taps and scrolling for 317 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 592 ms
592 msReal visitors wait 592 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 18.4 MB in 416 requests
18.4 MBYour homepage downloads 18.4 MB in 416 requests on a phone: media 11.5 MB (1), scripts 3.1 MB (197) and images 2.1 MB (27). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
prescent_hub_5x4_zoom_small_360f47a9-dc3a-4eef-ba77-172570df weighs 1.9 MB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (1.9 MB) 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.
1 image below the first screen load straight away
1 image further down the page (1.9 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 5.2 g of CO₂ per visit
5.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.20 g of CO₂e: 624.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
41 text elements with low contrast
41 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
35 tap targets too small
35 tap targets are too small or too close together to hit reliably with a finger.
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 (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Fragrance shouldbe personal” and “Want to gift a truly personalized gift?”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
141 internal links, 9 external
The homepage links to 141 pages on olfactorynyc.com and 9 external pages.
6 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Olfactory NYC represents a revolutionary step in custom perfume. We specialize in crafting custom fragrances while ensu…”.
Title: 62 characters
Your title is a healthy 62 characters: “Olfactory NYC: A New Custom Fragrance Concept | Custom Perfume”.
Canonical URL set
The canonical URL is https://www.olfactorynyc.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.olfactorynyc.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,465 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.olfactorynyc.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.olfactorynyc.com/products/custom-scent-15ml-travel-size-test-only, whose canonical is https://www.olfactorynyc.com/products/custom-scent-15ml-travel-size. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www.olfactorynyc.com/pages/tinkerer2, https://www.olfactorynyc.com/products/custom-scent-50ml-wizard, https://www.olfactorynyc.com/pages/customizer, https://www.olfactorynyc.com/products/custom-scent-15ml-travel-size-test-only, https://www.olfactorynyc.com/products/custom-body-oil-1 and https://www.olfactorynyc.com/products/custom-body-lotion-test-only and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://www.olfactorynyc.com/products/custom-scent-15ml-travel-size-test-only, https://www.olfactorynyc.com/products/custom-body-oil-1, https://www.olfactorynyc.com/products/custom-body-lotion-test-only, https://www.olfactorynyc.com/products/custom-body-wash-test-only, https://www.olfactorynyc.com/products/custom-hair-body-mist and https://www.olfactorynyc.com/products/solid-pallete-custom 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 71 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.
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.
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
1 broken image
1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=bb6aba74-b14e-4e33-8485-259438088bbe&referrer=&landingpage=https%3A%2F%2Fwww.olfactorynyc.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20O.
48 small tap targets
48 of 78 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 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
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 1,423 words of copy
The homepage carries about 1,423 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: “BOOK” and “BOOK IN STUDIO”.
37 calls to action
The homepage has 37 calls to action, for example “Shop”, “Start” and “BOOK IN STUDIO”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 4 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Microsoft Clarity and TikTok Pixel.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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.
42 cookies set on arrival
42Opening the homepage sets 42 cookies, 3 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.
69 other companies contacted
Loading the homepage contacts 69 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 olfactorynyc.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 23 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Hotjar Install · Judge Me Reviews · Klaviyo Email Marketing Sms · Triplewhale · Gsc Instagram Feed · Eg Auto Add To Cart · Microsoft Clarity · Hulk Form Builder · Checkmate · Sesami · Reputon Google Reviews Widget · Tek Labs Gifts Upsell · Selleasy · Aftersell · cloudfront.net · zotabox.com · powr.io · luckyorange.com · gorgias.chat · b-cdn.net · hextom.com · 9gtb.com · amazonaws.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 10 open roles
- Teams
- Retail (10)
- Job board
- rippling
Company
- 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 45 issues on olfactorynyc.com, including 21 speed issues, 3 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.