cupids.com website review

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

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

8 third-party services load with your homepage (alia-prod.com, replocdn.com and Shopify and others), adding 14.3 MB and 1.1 s of main-thread time.

Shopify costs a phone 150 ms of main-thread work and 12.9 MB 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.

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

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

About 696 KiB of JavaScript is downloaded but never used on this page.

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

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

alia-prod.com costs a phone 290 ms of main-thread work and 331 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.

replocdn.com costs a phone 278 ms of main-thread work and 371 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.

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 16.4 MB in 415 requests on a phone: media 11.3 MB (6), scripts 2.1 MB (115) and images 1.3 MB (38). Under 2 MB keeps phones on slow connections fast.

5 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

16 images are downloaded at several times the size a phone draws them, for example cologne.webp at 820 px wide, shown at 135 px. Resized copies would save about 2.3 MB.

20 images (4.6 MB) 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.

13 images further down the page (878 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 4.64 g of CO₂e: 556.4 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: 17 elements on the page fail this check, rated serious by axe-core.

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

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

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

All page content should be contained by landmarks: 3 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: 2 elements on the page fail this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 67 characters, so Google will cut it off around 60: “Cupids Fragrances | Pheromone-Infused Cologne | Scent That Attracts”.

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

2 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 40 pages on cupids.com and 1 external page.

/collections/shop-all and /collections/all all use the title “Shop All – Cupids”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/shop-all, /collections/all, /pages/cologne-bundle, /pages/deodorant-bundles, /pages/soap-bundles and /pages/body-wash-bundles and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/shop-all, /collections/all, /pages/cologne-bundle, /pages/deodorant-bundles, /pages/soap-bundles and /pages/body-wash-bundles and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/shop-all, /collections/all, /pages/cologne-bundle, /pages/deodorant-bundles, /pages/soap-bundles and /pages/body-wash-bundles and 3 others 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 20 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0735/1615/5191/files/1729852599-bfcm-mobile.webp?v=1730106795&width=820.

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

6 links from your homepage to your own site are broken, for example https://www.cupids.com/collections/shop-all (network).

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

1 link go through two or more redirects, for example https://www.cupids.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.

cupids.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

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

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 1,174 words of visible text.

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

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 Amplitude, Hotjar, Klaviyo and Microsoft Clarity (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 22 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 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.