asutra.com website review

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

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

8 third-party services load with your homepage (gotolstoy.com, Yotpo and rebuyengine.com and others), adding 2.1 MB and 780 ms of main-thread time.

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

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

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

rebuyengine.com costs a phone 179 ms of main-thread work and 701 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.

Yotpo costs a phone 184 ms of main-thread work and 329 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.

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

14 images could be 228 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

About 62 KiB of CSS is downloaded but never applied on this page.

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

12 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.

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

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

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

The first text or image appears after 4.4 s on a phone. Good is under 1.8 s.

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners, including Shopify, use cookies and oth…”. Most of its time is element render delay (2.5 s).

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

3 images 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 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 234 requests on a phone: scripts 1.6 MB (65), images 748 KiB (39) and other files 735 KiB (101). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example melt-pain-away-magnesium-body-butter-lotion-capsaicin-front- at 400 px wide, shown at 107 px. Resized copies would save about 55 KiB.

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

3 images (340 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.19 g of CO₂e: 142.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Headings skip levels (h1 → h3), 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 meta description is 204 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 100 pages on asutra.com and 5 external pages.

/collections/eye-pillows, /collections/anti-aging-serums, /collections/aromatherapy-mists, /collections/yoga-mat-cleaners, /collections/bath-salts and /collections/body-scrubs 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 32 found) and read each the way a search engine does.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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

2 links go through two or more redirects, for example https://asutra.com/customer_authentication/redirect?locale=en&region_country=US.

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.

asutra.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.

asutra.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.

The homepage carries about 729 words of visible text.

asutra.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be asutra.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

Opening the homepage sets 10 cookies, 1 of them by other companies (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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.