nailsinc.com website review

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

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

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

38 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

8 third-party services load with your homepage (Facebook, Kaltura Video Platform and Yotpo and others), adding 2.3 MB and 930 ms of main-thread time.

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

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

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

Kaltura Video Platform costs a phone 191 ms of main-thread work and 573 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 120 ms of main-thread work and 707 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.

Yotpo costs a phone 149 ms of main-thread work and 382 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.

Polyfills for old browsers add 102 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

42 KiB could be saved by minifying JavaScript.

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.

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

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

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 “Nails Inc London”.

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

4 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-24, real Chrome visitors' tap response (inp) went from 112 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.3 MB in 309 requests on a phone: scripts 2.0 MB (91), images 971 KiB (41) and other files 938 KiB (147). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example AllureBestofBeauty_Outline.png at 3,000 px wide, shown at 75 px. Resized copies would save about 242 KiB.

1 image further down the page (243 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 144.9 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”.

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 16 characters: “Nails Inc London”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 175 pages on nailsinc.com and 22 external pages.

https://nailsinc.com/en-us/collections/new-in-1, https://nailsinc.com/en-us/collections/the-complete-collection-us, https://nailsinc.com/en-us/pages/holiday-gift-guide, https://nailsinc.com/en-us/collections/press-on-nails-us, https://nailsinc.com/en-us/collections/web-exclusives-1 and https://nailsinc.com/en-us/collections/nail-polish-trends-us and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://nailsinc.com/en-us/pages/holiday-gift-guide has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://nailsinc.com/en-us.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

Social proof on the homepage: 1 trust badge. 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 has only about 204 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 29 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.