letsdisco.com website review

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

About 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

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

8 third-party services load with your homepage (shgcdn3.com, Unpkg and Google Fonts and others), adding 1.8 MB and 56 ms of main-thread time.

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

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

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

1 long task block the main thread while loading, the longest for 57 ms. During a long task the page ignores taps.

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

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.

Your largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “1,694+ 5-Star Reviews Your New Anti-Aging Secret Our best-s…”.

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

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

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

11 images are downloaded at several times the size a phone draws them, for example Disco-product-face-scrub.jpg at 1,800 px wide, shown at 350 px. Resized copies would save about 863 KiB.

Your homepage downloads 3.9 MB in 141 requests on a phone: images 2.9 MB (81), scripts 564 KiB (36) and fonts 243 KiB (4). Under 2 MB keeps phones on slow connections fast.

Disco-product-face-scrub.jpg 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).

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

1 button has no accessible name, so screen readers announce just “button”.

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

2 links inside paragraphs rely on colour alone to stand out.

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

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

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

Your title is only 23 characters: “Disco™ Skincare for Men”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 54 characters: “Disco™ makes science-backed skincare products for men.”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Your New Anti-Aging Secret” and “Your New Anti-Aging Secret”). One clear main headline is easier for people and search engines.

Structured data found (untyped) but with 8 problems, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

2 links have no real href, so search engines can't follow them.

The homepage links to 126 pages on letsdisco.com and 7 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.

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

2 images failed to load on a phone, for example https://letsdisco.com/cdn/shop/files/sale-logo-badge-updated-new.png?v=217943.

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

1 error was 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.

1 link go through two or more redirects, for example https://letsdisco.com/checkout/.

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.

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

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

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

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

DMARC is set to p=none, so mail pretending to be letsdisco.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 Google Tag Manager (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 8 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.