Website review, no card needed
aroma360.com website review
Visit site (opens in a new tab)Reviewed 19 November 202639 issues · 87 checks
This review found 39 issues worth fixing on aroma360.com, 17 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Aroma360
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73C- #88,742 of 119,740 reviewed websitesbeats 22%
- #55,621 of 67,889 online storesbeats 15%
- #52,107 of 61,876 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.5 s |
| Nov 14, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 163 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 171 ms |
| Jun 20, 2026 | 171 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 168 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 165 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 167 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 172 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 171 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 172 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 182 ms |
| Oct 31, 2026 | 180 ms |
| Nov 7, 2026 | 178 ms |
| Nov 14, 2026 | 171 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
Reduce unused JavaScript
1.4 s · 2.9 MBAbout 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Improve image delivery
2.8 s · 1.2 MB13 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.
Main-thread work: 26.9 s
A phone's processor spends 26.9 s on main-thread work while loading, 11.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
2.6 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Use efficient cache lifetimes
1.6 s · 896 KiB52 files are served with short cache lifetimes, so returning visitors download them again (896 KiB).
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,563 HTML elements
The page has 7,563 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, alia-prod.com and Clarity and others), adding 6.0 MB and 3.6 s of main-thread time.
Google Tag Manager adds 961 ms
961 msGoogle Tag Manager costs a phone 961 ms of main-thread work and 1.7 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.
alia-prod.com adds 664 ms
664 msalia-prod.com costs a phone 664 ms of main-thread work and 279 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.
Clarity adds 466 ms
466 msClarity costs a phone 466 ms of main-thread work and 30 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 459 ms. During a long task the page ignores taps.
Klaviyo adds 394 ms
394 msKlaviyo costs a phone 394 ms of main-thread work and 546 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.
minmaxify.com adds 426 ms
426 msminmaxify.com costs a phone 426 ms of main-thread work and 10 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 · 198 KiBAbout 198 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.
Legacy JavaScript
77 KiBPolyfills for old browsers add 77 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
54 KiB54 KiB JavaScript is shipped twice across bundles.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
30 KiB30 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: 41 ms
41 msYour server sent the HTML in 41 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: 15.7 s
15.7 sYour largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Aroma360”.
Speed Index: 19.2 s
19.2 sVisually, the page fills in at 19.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 64.3 s
64.3 sThe page becomes fully interactive after 64.3 s. Good is under 3.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 163 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 197 ms
197 msReal visitors wait 197 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 TTFB: 528 ms
528 msReal visitors wait 528 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.074
0.074The layout barely moves while loading (CLS 0.074, good is under 0.1).
Images and page weight
Page weight: 12.3 MB in 686 requests
12.3 MBYour homepage downloads 12.3 MB in 686 requests on a phone: scripts 6.6 MB (239), images 3.3 MB (71) and other files 1.4 MB (315). Under 2 MB keeps phones on slow connections fast.
About 3.5 g of CO₂ per visit
3.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.50 g of CO₂e: 419.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (8 elements).
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.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("aroma360.com")”.
315 internal links, 0 external
The homepage links to 315 pages on aroma360.com and 0 external pages.
7 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “As the leading scent company in marketing and branding, Aroma360 prides itself on providing the perfect scenting soluti…”.
One H1 headline
Your main headline reads: “Aroma360”.
Title: 51 characters
Your title is a healthy 51 characters: “Scent Company | Home & Business Scenting | Aroma360”.
Canonical URL set
The canonical URL is https://aroma360.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://aroma360.com/sitemap.xml.
AI search readiness
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.
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.
llms.txt published
The site publishes https://aroma360.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://aroma360.com/products/free-diffuser, https://aroma360.com/pages/business-scenting, https://aroma360.com/pages/showrooms, https://aroma360.com/products/free-large-diffuser, https://aroma360.com/collections/diffuser-oil and https://aroma360.com/collections/scent-diffusers and 9 others 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.
6 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.
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
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
Requests the notification permission on page load
Requests the notification permission on page load.
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.
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.
Only about 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Cancel Order”, “Request Samples” and “GET STARTED”.
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 38 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and LinkedIn Insight.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 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 aroma360.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify Plus
- Hosting
- Shopify
Company
- Employees
- 350
- Headquarters
- Dearborn
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on aroma360.com, including 23 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.