capillus.com website review

46 files are served with short cache lifetimes, so returning visitors download them again (1,007 KiB).

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

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Shopify and others), adding 2.8 MB and 3.2 s of main-thread time.

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

Signyfyd costs a phone 800 ms of main-thread work and 281 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.

Google Tag Manager costs a phone 594 ms of main-thread work and 737 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 584 ms of main-thread work and 640 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.

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

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

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

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

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

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

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

57 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

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

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' tap response (inp) went from 179 ms to 170 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.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 406 requests on a phone: scripts 3.9 MB (194), other files 853 KiB (147) and images 473 KiB (33). Under 2 MB keeps phones on slow connections fast.

TRISPECTRUM-HERO-HOME-MOBILE-26.webp 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 (63 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.71 g of CO₂e: 205.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

There are 3 <h1> headlines (“Capillus Capillus”, “Early Black Friday” and “The Most Trusted Red Light Therapy Company”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, CollectionPage, ImageObject and Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 96 pages on capillus.com and 12 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/products/capillus-trispectrum has no <title>, so Google invents the link text in results.

/products/capillus-trispectrum has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/black-friday, /collections/laser-therapy-caps-for-hair-growth-copy, /products/capillus-trispectrum and /products/capillus-spectrum have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://tags.w55c.net/rs?id=32bdf49b2d1d41f6bcf632b2026e5856&t=completed_view.

6 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

Large scripts ship without source maps.

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.

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

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

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.

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

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

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 Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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 55 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 81 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.