Website review, no card needed

10percentcabinetry.com logo

10percentcabinetry.com website review

Visit site (opens in a new tab)Reviewed 10 November 202639 issues · 84 checks

This review found 39 issues worth fixing on 10percentcabinetry.com, 14 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
1.9 s966 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.5 s
Oct 31, 20261.3 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
81 ms58 msMay 23Oct 1069 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202665 ms
Jun 13, 202661 ms
Aug 15, 202678 ms
Aug 22, 202671 ms
Sep 5, 202671 ms
Sep 26, 202668 ms
Oct 3, 202669 ms
Oct 10, 202669 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 10percentcabinetry.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 10percentcabinetry.com at 0.5 s0.5 s
  2. 10percentcabinetry.com at 1.0 s1.0 s
  3. 10percentcabinetry.com at 1.4 s1.4 s
  4. 10percentcabinetry.com at 1.9 s1.9 s
  5. 10percentcabinetry.com at 2.4 s2.4 s
  6. 10percentcabinetry.com at 2.9 s2.9 s
  7. 10percentcabinetry.com at 3.4 s3.4 s
  8. 10percentcabinetry.com at 3.8 s3.8 s

Speed

10 to fix44
  • Improve image delivery

    4.5 s · 1.2 MB

    7 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.5 s faster on a phone.

  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.2 s · 269 KiB

    About 269 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 2.4 MB and 1.5 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Google CDN adds 901 ms

    901 ms

    Google CDN costs a phone 901 ms of main-thread work and 1.5 MB 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.

  • Minify JavaScript

    450 ms · 202 KiB

    202 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 459 ms

    459 ms

    Google Tag Manager costs a phone 459 ms of main-thread work and 507 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 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    10 KiB

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

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    5 KiB

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

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 12.3 s

    12.3 s

    Your largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ENJOY 10% MORE Become our dealer right now! REGISTER NOW”.

  • Time to Interactive: 27.5 s

    27.5 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Total Blocking Time: 816 ms

    816 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

    The first text or image appears after 3.0 s on a phone. Good is under 1.8 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

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

    +10%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    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-user LCP: 1.1 s

    1.1 s

    Real visitors wait 1.1 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.0 s

    1.0 s

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

  • Real-user TTFB: 711 ms

    711 ms

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

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

    -26%

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

2 to fix60
  • Page weight: 6.1 MB in 263 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 263 requests on a phone: scripts 2.6 MB (195), images 1.5 MB (16) and other files 1.0 MB (20). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    25 KiB

    3 images are downloaded at several times the size a phone draws them, for example sd-stowe_driftwood.png at 300 px wide, shown at 96 px. Resized copies would save about 25 KiB.

  • 4 images in older formats

    4 images (374 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 1.7 g of CO₂ per visit

    1.72 g

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

1 checks passed
  • Images load when needed

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

Accessibility

2 to fixGoogle 10098
  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

6 to fixGoogle 9270
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “RTA Cabinets USA Cincinnati| 10% Cabinetry | Wholesale Cabinets Distributor”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 36 internal links, 4 external

    The homepage links to 36 pages on 10percentcabinetry.com and 4 external pages.

3 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “10% Cabinetry offers high-quality, ready-to-assemble (RTA) cabinets at wholesale prices in USA Cincinnati. Contact us f…”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.10percentcabinetry.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.10percentcabinetry.com/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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

4 to fix60
  • 1 linked page is broken

    Your homepage links to https://www.10percentcabinetry.com/wall-cabinet, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages without a meta description

    https://www.10percentcabinetry.com/blog, https://www.10percentcabinetry.com/product.html and https://www.10percentcabinetry.com/resources/assemblyvideo/WM3030 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.10percentcabinetry.com/blog, whose canonical is https://www.10percentcabinetry.com/blog.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://www.10percentcabinetry.com/about-us, https://www.10percentcabinetry.com/product.html, https://www.10percentcabinetry.com/10-catalog, https://www.10percentcabinetry.com/shaker-driftwood.html, https://www.10percentcabinetry.com/bevel-blue.html and https://www.10percentcabinetry.com/bevel-green.html and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.10percentcabinetry.com/about-us, https://www.10percentcabinetry.com/product.html, https://www.10percentcabinetry.com/resources/assemblyvideo/WM3030, https://www.10percentcabinetry.com/10-catalog, https://www.10percentcabinetry.com/gallery and https://www.10percentcabinetry.com/become-a-dealer and 1 other have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

3 checks passed
  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 6 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://pro.fontawesome.com/releases/v5.15.4/css/all.css' from origin 'https://www.10perce…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

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

  • Only about 94 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REGISTER NOW”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “REGISTER NOW” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies (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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 10percentcabinetry.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on 10percentcabinetry.com, including 16 speed issues, 6 SEO issues and 5 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