equelle.com website review

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

Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Klaviyo, Accessibe Accessibility Overlay and Optanon and others), adding 1.7 MB and 552 ms of main-thread time.

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

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

Klaviyo costs a phone 196 ms of main-thread work and 616 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 19 ms of main-thread work and 377 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.

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

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

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

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

1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 KiB could be saved by minifying CSS.

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 15.6 s. Good is under 3.8 s.

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Multi-symptom menopause relief. Guaranteed. Equelle is a re…”.

The layout shifts by 0.618 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 821 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 2.4 MB in 160 requests on a phone: scripts 1.4 MB (87), fonts 421 KiB (12) and images 281 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

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

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

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 55 pages on equelle.com and 5 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.

/pages/healthcare-professionals has no <title>, so Google invents the link text in results.

/a/faqs and /tools/recurring/get-subscription-access all use the title “Equelle”. Search engines can't tell which page to show for a search, so each competes with the others.

/a/faqs, /pages/healthcare-professionals and /tools/recurring/get-subscription-access have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /pages/contact-us, whose canonical is /pages/contact-form. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/equelle-quiz and /pages/healthcare-professionals have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/contact-us took over 3 s to send its HTML from our server.

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

3 of 11 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: the server responded with a status of 404 ()”.

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.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 10 testimonial or review blocks. 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 shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,017 words of visible text.

DMARC is set to p=none, so mail pretending to be equelle.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 17 cookies (measured from a US location before any click).

Loading the homepage contacts 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.