niraskin.com website review

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

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

8 third-party services load with your homepage (negate.io, rapidlercdn.com and Shopify and others), adding 442 KiB and 104 ms of main-thread time.

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

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

1 long task block the main thread while loading, the longest for 72 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).

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

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

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.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 217 ms to 284 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 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 94 requests on a phone: images 2.3 MB (34), scripts 679 KiB (42) and HTML 112 KiB (1). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.91 g of CO₂e: 109.1 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: 7 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

[aria-*] attributes do not have valid values (1 element).

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

Elements use prohibited ARIA attributes (3 elements).

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

Your title is 70 characters, so Google will cut it off around 60: “At-Home Skincare Lasers | FDA-Cleared for Wrinkles & Fine Lines | NIRA”.

The homepage links to 150 pages on niraskin.com and 6 external pages.

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.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.

Before a visitor clicks anything, the page loads Klaviyo (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 14 cookies, 10 of them by other companies (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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.