Website review, no card needed
snif.co website review
Visit site (opens in a new tab)Reviewed 9 November 202646 issues · 89 checks
This review found 46 issues worth fixing on snif.co, 17 of them high impact, across 89 checks. The most urgent: page weight: 34.1 MB in 264 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
74C- #76,973 of 109,350 reviewed websitesbeats 26%
- #48,456 of 61,859 online storesbeats 18%
- #45,606 of 56,401 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
| Nov 7, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 159 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 167 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 173 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 188 ms |
| Jul 18, 2026 | 189 ms |
| Jul 25, 2026 | 193 ms |
| Aug 1, 2026 | 192 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 197 ms |
| Aug 22, 2026 | 200 ms |
| Aug 29, 2026 | 200 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 197 ms |
| Oct 10, 2026 | 197 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 196 ms |
| Oct 31, 2026 | 195 ms |
| Nov 7, 2026 | 194 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
Speed
Render-blocking requests
1.9 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
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.
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,683 HTML elements
The page has 3,683 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, Accessibe Accessibility Overlay and TikTok and others), adding 29.4 MB and 1.2 s of main-thread time.
Shopify adds 75 ms
75 msShopify costs a phone 75 ms of main-thread work and 28.3 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.
Reduce unused JavaScript
900 ms · 660 KiBAbout 660 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Improve image delivery
1.1 MB19 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 316 ms. During a long task the page ignores taps.
Google Tag Manager adds 266 ms
266 msGoogle Tag Manager costs a phone 266 ms of main-thread work and 384 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
150 ms · 23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 8 KiB8 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
135 KiB16 files are served with short cache lifetimes, so returning visitors download them again (135 KiB).
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need.
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: 15 ms
15 msYour server sent the HTML in 15 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: 13.3 s
13.3 sYour largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 26.4 s
26.4 sThe page becomes fully interactive after 26.4 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 790 ms
790 msScripts block taps and scrolling for 790 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 213 ms
213 msReal visitors wait 213 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 159 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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 CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (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: 476 ms
476 msReal visitors wait 476 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.091
0.091The layout barely moves while loading (CLS 0.091, good is under 0.1).
Images and page weight
Page weight: 34.1 MB in 264 requests
34.1 MBYour homepage downloads 34.1 MB in 264 requests on a phone: media 27.6 MB (5), images 3.6 MB (70) and scripts 1.6 MB (74). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Snif_SM_ST_Blocks_Small-3_800x.gif weighs 844 KiB. On a phone connection a single image that size takes seconds.
5 images far larger than shown
587 KiB5 images are downloaded at several times the size a phone draws them, for example Snif_SM_ST_Blocks_Small-3_800x.gif at 800 px wide, shown at 195 px. Resized copies would save about 587 KiB.
8 images below the first screen load straight away
8 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (844 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 9.7 g of CO₂ per visit
9.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.65 g of CO₂e: 1158.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (4 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 4 elements on the page fail this check, rated moderate by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 140 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 7 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (64 characters)
Your meta description is only 64 characters: “We make it easy to find fragrances and scented candles you love.”. 70 to 160 characters is enough to sell the click.
247 internal links, 16 external
The homepage links to 247 pages on snif.co and 16 external pages.
5 checks passed
Title: 40 characters
Your title is a healthy 40 characters: “Fine Fragrances & Scented Candles | Snif”.
Canonical URL set
The canonical URL is https://snif.co/.
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://snif.co/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (2,895 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://snif.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://snif.co/pages/notewrks is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
8 pages without a meta description
https://snif.co/collections/holiday-gift-sets, https://snif.co/pages/holiday-scent-shop, https://snif.co/collections/snif-merch, https://snif.co/collections/surplus-sale, https://snif.co/pages/secret-menu-landing and https://snif.co/pages/notewrks and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://snif.co/pages/holiday-scent-shop, https://snif.co/pages/secret-menu-landing and https://snif.co/pages/notewrks 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 128 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.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 24 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”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
About 1,088 words of copy
The homepage carries about 1,088 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “shop now”.
49 calls to action
The homepage has 49 calls to action, for example “shop all”, “holiday scent shop” and “shop our most experimental scents”.
13 short forms
13 short forms (5 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 3 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
33 cookies set on arrival
33Opening the homepage sets 33 cookies, 1 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.
43 other companies contacted
Loading the homepage contacts 43 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 snif.co, 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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Postscript Sms Marketing · Savedby Package Protection · Bubblehouse For Snif · Test Sms · klaviyo.com · snapchat.com · gorgias.chat · 9gtb.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
- Google Analytics
- Hosting
- Shopify
Hiring
- Hiring
- 2 open roles
- Teams
- Operations (1), Product Development (1)
- Job board
- lever
- Careers page
- jobs.lever.co/Snif (opens in a new tab)
Company
- Founded
- 2020
- Headquarters
- Brooklyn
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on snif.co, including 18 speed issues, 3 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.