Website review, no card needed

bndnails.com logo

bndnails.com website review

Visit site (opens in a new tab)Reviewed 9 November 202638 issues · 89 checks

This review found 38 issues worth fixing on bndnails.com, 10 of them high impact, across 89 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s946 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.6 s
Jun 13, 20261.4 s
Jun 20, 20261.2 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.1 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
159 ms88 msMay 23Nov 7141 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202696 ms
May 30, 202698 ms
Jun 6, 2026104 ms
Jun 13, 2026112 ms
Jun 20, 2026112 ms
Jun 27, 2026114 ms
Jul 4, 2026120 ms
Jul 11, 2026121 ms
Jul 18, 2026127 ms
Jul 25, 2026129 ms
Aug 1, 2026130 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026135 ms
Aug 29, 2026137 ms
Sep 5, 2026143 ms
Sep 12, 2026150 ms
Sep 19, 2026149 ms
Sep 26, 2026151 ms
Oct 3, 2026146 ms
Oct 10, 2026145 ms
Oct 17, 2026145 ms
Oct 24, 2026146 ms
Oct 31, 2026145 ms
Nov 7, 2026141 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of bndnails.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bndnails.com at 1.0 s1.0 s
  2. bndnails.com at 2.0 s2.0 s
  3. bndnails.com at 3.0 s3.0 s
  4. bndnails.com at 4.0 s4.0 s
  5. bndnails.com at 5.0 s5.0 s
  6. bndnails.com at 6.1 s6.1 s
  7. bndnails.com at 7.1 s7.1 s
  8. bndnails.com at 8.1 s8.1 s

Speed

10 to fix68
  • Main-thread work: 7.1 s

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

  • 6,851 HTML elements

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

  • Improve image delivery

    700 ms · 956 KiB

    13 images could be 956 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

  • Mobile performance score: 68

    68/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and smile.io and others), adding 2.1 MB and 759 ms of main-thread time.

  • Render-blocking requests

    800 ms

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

  • Klaviyo adds 406 ms

    406 ms

    Klaviyo costs a phone 406 ms of main-thread work and 525 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 adds 178 ms

    178 ms

    Shopify costs a phone 178 ms of main-thread work and 309 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.

  • smile.io adds 151 ms

    151 ms

    smile.io costs a phone 151 ms of main-thread work and 363 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.

  • klaviyomail.com adds 0 ms

    0 ms

    klaviyomail.com costs a phone 0 ms of main-thread work and 979 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.

  • Reduce unused JavaScript

    137 KiB

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

  • 13 long tasks on the main thread

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

  • Reduce unused CSS

    44 KiB

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

  • Use efficient cache lifetimes

    25 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

  • Duplicated JavaScript

    6 KiB

    6 KiB JavaScript is shipped twice across bundles.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 28 ms

    28 ms

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

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 20.5 s

    20.5 s

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

  • Speed Index: 8.3 s

    8.3 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

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

  • Real-user INP: 218 ms

    218 ms

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

  • Tap response (INP) got 47% slower for real visitors

    +47%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 233 ms

    233 ms

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

7 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 580 ms

    580 ms

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

  • Largest content (LCP) got 39% faster for real visitors

    -39%

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 5.3 MB in 279 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 279 requests on a phone: images 2.9 MB (38), scripts 1.0 MB (133) and other files 625 KiB (67). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    LAVIS_Amber_Jelly_Gel_Collection_Mobile.jpg 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).

  • 3 images far larger than shown

    334 KiB

    3 images are downloaded at several times the size a phone draws them, for example DC_PART_13_4dcfbbd0-23e4-41b9-9de4-cb9dd820e738.jpg at 375 px wide, shown at 57 px. Resized copies would save about 334 KiB.

  • About 1.5 g of CO₂ per visit

    1.51 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9796
  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (4 elements)

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

  • 39 links without text

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

  • Headings should not be empty (12 elements)

    Headings should not be empty: 12 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 335 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

5 to fixGoogle 9277
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Wholesale Nail Supplies USA — OPI, DND, Lavis & A'DOR – DTK Nail Supply”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Wholesale Nail Supplies for US Salons & Home Stud…”). One clear main headline is easier for people and search engines.

  • Meta description is long (165 characters)

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

  • Structured data has 1 problem

    Structured data found (FAQPage, Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//dtknailsupply.com/cdn/shop/t/109/assets/logo.png?v=16…”.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 1,097 internal links, 8 external

    The homepage links to 1,097 pages on bndnails.com and 8 external pages.

4 checks passed
  • Canonical URL set

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

  • Open Graph tags complete

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

  • robots.txt in place

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

  • XML sitemap found

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

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://dtknailsupply.com/llms.txt (50 KiB, 221 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix58
  • 1 page without a title

    https://dtknailsupply.com/holiday-catalog has no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://dtknailsupply.com/collections/types declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://dtknailsupply.com/collections/types all use the title “Wholesale Nail Supplies USA — OPI, DND, Lavis & A'DOR – DTK Nail Supp…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://dtknailsupply.com/holiday-catalog and https://dtknailsupply.com/collections/dnd-dc-diva-starter-sets have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://dtknailsupply.com/products/lavis-super-clear-cat-eye-gel, https://dtknailsupply.com/products/ador-beauty-hema-free-set-64-colors-gel-polish-colletion, https://dtknailsupply.com/products/lavis-bath-bomb-buy-5-get-1-free, https://dtknailsupply.com/products/buy-lds-j04-jelly-collection-free-1-lds-moon-light-silver-cat-eye-1-lds-rain-bow-cat-eye-1-chrome-powder-super-clear-2-ador-drip-base-top-1-ribbon-magnet, https://dtknailsupply.com/products/buy-lds-softly-sheer-collection-free-color-sample and https://dtknailsupply.com/products/bundle-save-lavis-c01-jelly-jamboree-collection and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9297
  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    92 of 100 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • Local business without LocalBusiness data

    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.

  • No analytics detected

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

  • No map or directions link

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

  • No risk reducer

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

  • About 1,344 words of copy

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop New Arrivals →”.

  • 91 calls to action

    The homepage has 91 calls to action, for example “LAVIS Bath Bomb: Buy 5, Get 1 FREE”, “Sign in/ Register” and “SHOP ALL”.

  • 17 short forms

    17 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 34 testimonial or review blocks, a star rating and “480+ reviews”.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 2 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 32 other companies contacted

    Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at bndnails.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Accessibility Assistant · Gift Box Builder · elfsight.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Cloudflare

Company

Headquarters
San Jose

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on bndnails.com, including 17 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25