gleamin.com website review

Your mobile performance score is 97. That is in Google's “good” band (90 and up).

A phone's processor spends 1.5 s on main-thread work while loading, 318 ms of it running JavaScript. That is comfortably low.

Your server sent the HTML in 17 ms, well inside Google's 600 ms guideline.

Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

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

For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

Real visitors see the first content after 1.4 s (75th percentile). 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 120 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Skincare built for skin prone to dark spots, with melanin-r…”.

The page is fully interactive after 2.1 s.

The layout barely moves while loading (CLS 0, good is under 0.1).

Scripts block the page for only 20 ms while loading. Good is under 200 ms.

Your homepage downloads 421 KiB in 28 requests on a phone: scripts 183 KiB (13), images 89 KiB (7) and fonts 63 KiB (2). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

Images below the first screen wait until the visitor scrolls to them.

No image is downloaded at more than three times the size it is drawn on a phone.

All 13 images in the HTML carry an alt attribute.

axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

Your meta description is 146 characters: “Skincare for skin prone to dark spots and uneven tone, made with melanin-rich skin in mind. Trusted by 1M+ people. The …”.

Your main headline reads: “The new Gleamin is almost here.”.

Your title is a healthy 53 characters: “Gleamin | Skincare for dark spots & hyperpigmentation”.

The canonical URL is https://gleamin.com/.

Structured data found: ImageObject, Organization, WebPage and WebSite.

Open Graph tags are complete, so shared links show a title, description and image.

robots.txt is in place and points crawlers to your sitemap.

Your XML sitemap is reachable at https://gleamin.com/sitemap.xml.

Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

Your server sends the page's text in the HTML (1,814 words), so crawlers that don't run JavaScript still read it.

The site publishes /llms.txt (6 KiB, 33 links), a plain-text guide to the site for AI tools.

All 15 pages we checked loaded without an error.

No page we checked hands its ranking to a different URL.

All 15 pages that loaded have a meta description.

Every page we checked has its own title.

Each page we checked has a main headline.

None of the pages we checked carries a noindex tag.

All 15 pages that loaded have a <title>.

No JavaScript errors were logged while the page loaded on a phone.

The page declares a mobile viewport.

The homepage is served over HTTPS (gleamin.com).

The certificate from Let's Encrypt · YR1 verifies for gleamin.com and is valid for another 44 days.

X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

A Content-Security-Policy is set, the main browser-side defence against injected scripts.

Strict-Transport-Security is set, so browsers always use https.

http://gleamin.com redirects to the secure version.

The server speaks HTTP/2, so browsers load many files over one connection.

All 36 links checked from your homepage (24 internal, 12 external) answered without errors; 1 did not answer within 5 s.

gleamin.com was registered in Aug 2016 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

gleamin.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

gleamin.com is registered until Aug 2027.

On a phone, the first screen shows a clear next step: “Shop them on Amazon here →”.

The homepage has 9 calls to action, for example “Shop on Amazon (opens in a new tab)”, “Join the waitlist” and “Shop them on Amazon here →”.

A short form (2 fields at most) is right on the homepage, asking for an email.

DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com ~all”.

A DKIM key is published (selector “google”), so receivers can verify mail really came from you.

No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).