activintimates.com website review

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

Your mobile performance score is 60 (desktop: 50). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (amaicdn.com, Hotjar and Facebook and others), adding 790 KiB and 747 ms of main-thread time.

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

amaicdn.com costs a phone 348 ms of main-thread work and 412 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 files are served with short cache lifetimes, so returning visitors download them again (380 KiB).

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

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

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

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

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

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

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

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

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Activ Intimates Open Crotch Lace Bodysuit”.

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

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

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

3 images 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.1 MB in 184 requests on a phone: scripts 996 KiB (53), other files 822 KiB (116) and images 136 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 25 characters: “Lingerie– Activ Intimates”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 244 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

The homepage links to 49 pages on activintimates.com and 15 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/ and /collections/lingerie all use the title “Lingerie– Activ Intimates”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/shop, /pages/videos, /blogs/actively-intimate-blog, /collections/lingerie and /collections/all use the same meta description. A description written for each page earns more clicks.

/collections/lingerie has 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 22 found) and read each the way a search engine does.

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

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.

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 234 words of visible text; thin pages give Google and first-time buyers little to go on.

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

activintimates.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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.

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