niodor.com website review

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

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

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

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

Shopify costs a phone 193 ms of main-thread work and 319 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 106 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 210 ms faster on a phone.

7 third-party services load with your homepage (Shopify, stockist.co and Cloudflare CDN and others), adding 470 KiB and 255 ms of main-thread time.

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

About 21 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 60 ms faster on a phone.

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

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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.

Your largest element takes 5.1 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 6.7 s. Good is under 3.8 s.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.8 MB in 203 requests on a phone: images 1.2 MB (33), other files 728 KiB (80) and scripts 617 KiB (61). Under 2 MB keeps phones on slow connections fast.

1 image (36 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.

1 image further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

ARIA commands must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

3 tap targets are too small or too close together to hit reliably with a finger.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

2 images have no alt text, which hurts accessibility and image search.

Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 7 characters: “Niodor®”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 41 characters: “NIODOR® is the solution to odor nuisance.”. 70 to 160 characters is enough to sell the click.

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

Your <h1> is empty.

The homepage links to 39 pages on niodor.com and 4 external pages.

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.

/en/collections/products, /en/pages/where-to-buy, /en/pages/contact, /en/pages/growtent, /en/pages/grow-room and /en/pages/drying-room and 3 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /en/pages/faq, whose canonical is /en/pages/faq-how-do-i-get-rid-of-cannabis-smell. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en/collections/products, /en/pages/where-to-buy, /en/pages/contact, /en/pages/growtent, /en/pages/grow-room and /en/pages/drying-room and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

9 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 1 trust badge. 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.

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 743 words of visible text.

Before a visitor clicks anything, the page loads 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 7 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.