inaessentials.com website review

13 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and recart.com and others), adding 2.0 MB and 1.4 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page.

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

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

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

Google Tag Manager costs a phone 432 ms of main-thread work and 543 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 44 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

Klaviyo costs a phone 140 ms of main-thread work and 351 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.

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

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

18 KiB could be saved by minifying JavaScript.

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

5 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

Real visitors wait 463 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 239 ms to 307 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Scripts block taps and scrolling for 405 ms in total while the page loads. Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.8 MB in 503 requests on a phone: images 4.6 MB (68), scripts 2.2 MB (133) and other files 1.5 MB (271). Under 2 MB keeps phones on slow connections fast.

banner-2_mob_bg-opt.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example 1684047438forbes-logo-png.webp at 2,000 px wide, shown at 104 px. Resized copies would save about 48 KiB.

4 images (334 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.

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

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

218 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

9 buttons have no accessible name, so screen readers announce just “button”.

<svg> elements with an img or image role must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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.

ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

Your <h1> is empty.

The homepage links to 212 pages on inaessentials.com and 5 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/collections/hydrobiotics and /collections/naturalni-soli-za-vana have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/hydrobiotics and /collections/naturalni-soli-za-vana have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/produkti-za-kosa, /collections/naturalni-i-bio-hrani, /collections/hydrobiotics and /collections/naturalni-soli-za-vana 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.

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

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

Requests the notification permission on page load.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

inaessentials.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

inaessentials.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 29 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 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.