nailboo.com website review

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

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

Hotjar costs a phone 1.0 s of main-thread work and 65 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

8 third-party services load with your homepage (Hotjar, Google Tag Manager and Facebook and others), adding 1.8 MB and 2.9 s of main-thread time.

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

Google Tag Manager costs a phone 844 ms of main-thread work and 693 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.

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

About 754 KiB of JavaScript is downloaded but never used on this page.

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

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

Facebook costs a phone 331 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.

TikTok costs a phone 255 ms of main-thread work and 157 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 159 ms of main-thread work and 315 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.

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

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

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

11 KiB could be saved by minifying JavaScript.

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.

2 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

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

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

The first text or image appears after 1.8 s on a phone. 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 163 ms to 163 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.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.4 MB in 555 requests on a phone: scripts 2.3 MB (127), images 1.7 MB (205) and other files 903 KiB (164). Under 2 MB keeps phones on slow connections fast.

MOBILE_IMAGE-2_1.png 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).

By the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 184.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

Some list items are not inside a list.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your meta description is 252 characters; Google truncates after about 160, so the end of your pitch is cut.

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

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 113 pages on nailboo.com and 8 external pages.

https://nailboo.com/pages/nailflix-academy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://nailboo.com/pages/nailflix-academy all use the title “Nailboo® | Premium Nail Products”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nailboo.com/collections/shop-all, https://nailboo.com/pages/rewards, https://nailboo.com/pages/build-a-kit, https://nailboo.com/collections/press-ons-collection, https://nailboo.com/collections/removal-essentials and https://nailboo.com/collections/nail-care-essentials and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://nailboo.com/pages/rewards, whose canonical is https://nailboo.com/pages/boo-club. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://nailboo.com/collections/shop-all, https://nailboo.com/pages/build-a-kit, https://nailboo.com/collections/press-ons-collection, https://nailboo.com/collections/powder, https://nailboo.com/collections/gel-polish and https://nailboo.com/collections/removal-essentials and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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