Website review, no card needed

topdrawershop.com logo

topdrawershop.com website review

Visit site (opens in a new tab)Reviewed 20 October 202637 issues · 84 checks

This review found 37 issues worth fixing on topdrawershop.com, 9 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
3.0 s2.1 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.9 s
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
331 ms244 msMay 2Oct 17258 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026321 ms
May 9, 2026302 ms
May 16, 2026287 ms
May 23, 2026278 ms
May 30, 2026270 ms
Jun 6, 2026279 ms
Jun 13, 2026287 ms
Jun 20, 2026289 ms
Jun 27, 2026291 ms
Jul 4, 2026314 ms
Jul 11, 2026303 ms
Jul 18, 2026287 ms
Jul 25, 2026287 ms
Aug 1, 2026275 ms
Aug 8, 2026271 ms
Aug 15, 2026261 ms
Aug 22, 2026262 ms
Aug 29, 2026270 ms
Sep 5, 2026280 ms
Sep 12, 2026274 ms
Sep 19, 2026264 ms
Sep 26, 2026256 ms
Oct 3, 2026254 ms
Oct 10, 2026269 ms
Oct 17, 2026258 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 topdrawershop.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. topdrawershop.com at 1.2 s1.2 s
  2. topdrawershop.com at 2.4 s2.4 s
  3. topdrawershop.com at 3.6 s3.6 s
  4. topdrawershop.com at 4.9 s4.9 s
  5. topdrawershop.com at 6.1 s6.1 s
  6. topdrawershop.com at 7.3 s7.3 s
  7. topdrawershop.com at 8.5 s8.5 s
  8. topdrawershop.com at 9.7 s9.7 s

Speed

12 to fix50
  • Reduce unused JavaScript

    1.5 s · 578 KiB

    About 578 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 320 KiB

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

  • Main-thread work: 4.8 s

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

  • Improve image delivery

    50 ms · 2.9 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (osano.com, cloudfront.net and Yotpo and others), adding 4.2 MB and 1.0 s of main-thread time.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50 (desktop: 63). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    900 ms

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

  • Reduce unused CSS

    450 ms · 175 KiB

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

  • cloudfront.net adds 150 ms

    150 ms

    cloudfront.net costs a phone 150 ms of main-thread work and 2.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.

  • 1,763 HTML elements

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

  • Shopify adds 100 ms

    100 ms

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

  • Klaviyo adds 140 ms

    140 ms

    Klaviyo costs a phone 140 ms of main-thread work and 322 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.

  • Minify JavaScript

    150 ms · 73 KiB

    73 KiB could be saved by minifying JavaScript.

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    98 KiB

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

  • Font display

    50 ms

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

  • 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: 7 ms

    7 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 18.2 s

    18.2 s

    Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A person with blonde hair is sitting at a green table, writ…”.

  • Time to Interactive: 34.5 s

    34.5 s

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

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Total Blocking Time: 294 ms

    294 ms

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

9 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: 2.1 s

    2.1 s

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

  • Real-user INP: 194 ms

    194 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 441 ms

    441 ms

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

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

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

    -23%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix69
  • Page weight: 7.7 MB in 562 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 562 requests on a phone: images 3.9 MB (30), scripts 1.9 MB (235) and other files 1.4 MB (251). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • 1 image below the first screen load straight away

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

  • 1 image in older formats

    1 image (30 KiB) is 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 2.2 g of CO₂ per visit

    2.17 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9796
  • 2 tap targets too small

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

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

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

  • 7 links without text

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

4 to fixGoogle 9284
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

  • Meta description is long (265 characters)

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

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

  • 200 internal links, 8 external

    The homepage links to 200 pages on topdrawershop.com and 8 external pages.

5 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “House Shoes, Bags, Eyewear, Pens & Paper | Topdrawer”.

  • Canonical URL set

    The canonical URL is https://topdrawershop.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://topdrawershop.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix78
  • 2 pages share a title

    https://topdrawershop.com/collections/view-all-house-shoes and https://topdrawershop.com/collections/view-all-house-shoes-kolo all use the title “Japanese House Shoes – Topdrawer”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://topdrawershop.com/collections/view-all-house-shoes, https://topdrawershop.com/collections/cotton-house-shoes, https://topdrawershop.com/collections/wool-house-shoes, https://topdrawershop.com/collections/linen-house-shoes, https://topdrawershop.com/collections/suede-leather-house-shoes and https://topdrawershop.com/collections/view-all-house-shoes-kolo and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://topdrawershop.com/collections/view-all-house-shoes, whose canonical is https://topdrawershop.com/collections/view-all-house-shoes-kolo. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://topdrawershop.com/collections/all, https://topdrawershop.com/collections/view-all-house-shoes, https://topdrawershop.com/collections/cotton-house-shoes, https://topdrawershop.com/collections/wool-house-shoes, https://topdrawershop.com/collections/linen-house-shoes and https://topdrawershop.com/collections/suede-leather-house-shoes and 9 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 91 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • 18 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • 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 237 words

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

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign Up”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Return to shop”, “Sign Up” and “shop now”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Klaviyo and Pinterest Tag (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • 17 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on topdrawershop.com, including 17 speed issues, 4 SEO issues and 4 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