aromatools.com website review

The page has 3,946 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

20 images could be 319 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

About 669 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

8 third-party services load with your homepage (Shopify, vitals.app and tidio.co and others), adding 1.7 MB and 496 ms of main-thread time.

A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Shopify costs a phone 230 ms of main-thread work and 608 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.

vitals.app costs a phone 187 ms of main-thread work and 517 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.

tidio.co costs a phone 63 ms of main-thread work and 515 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.

About 59 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.

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

6 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.

120 KiB could be saved by minifying JavaScript.

10 files are served with short cache lifetimes, so returning visitors download them again (86 KiB).

28 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 16.5 s. Good is under 3.8 s.

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 802 ms for your server to start answering (75th percentile). Good is under 800 ms.

Visually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.

13 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 4.4 MB in 278 requests on a phone: scripts 1.8 MB (75), images 1.2 MB (55) and other files 858 KiB (130). Under 2 MB keeps phones on slow connections fast.

10 images further down the page (238 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (79 KiB) are 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 150.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

56 elements use ARIA attributes their role does not allow, which confuses screen readers.

6 dropdowns have no label.

3 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: 117 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

63 form fields have no label, so screen readers announce an empty box and autofill guesses.

46 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://aromatools.com/search?q={search_term_string}")”.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

2 links have no real href, so search engines can't follow them.

The homepage links to 361 pages on aromatools.com and 14 external pages.

https://aromatools.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://aromatools.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://aromatools.com/customer_authentication/redirect and https://aromatools.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://aromatools.com/customer_authentication/redirect, https://aromatools.com/collections/literature, https://aromatools.com/collections/books, https://aromatools.com/collections/booklets, https://aromatools.com/collections/brochures-handouts and https://aromatools.com/collections/charts and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 152 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 14 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,051 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

Opening the homepage sets 12 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.