Website review, no card needed

dockersshoes.com logo

dockersshoes.com website review

Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 71 checks

This review found 26 issues worth fixing on dockersshoes.com, 5 of them high impact, across 71 checks. The most urgent: delayed refresh under 20 hours must not be used (1 element). 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.2 s1.5 sMay 23Nov 71.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20261.8 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Nov 7, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
115 ms82 msMay 23Sep 2687 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202686 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202696 ms
Jun 20, 2026107 ms
Jun 27, 202695 ms
Jul 4, 202692 ms
Aug 1, 2026110 ms
Aug 8, 2026111 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Sep 5, 202696 ms
Sep 12, 202691 ms
Sep 19, 202688 ms
Sep 26, 202687 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 dockersshoes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dockersshoes.com at 0.4 s0.4 s
  2. dockersshoes.com at 0.8 s0.8 s
  3. dockersshoes.com at 1.3 s1.3 s
  4. dockersshoes.com at 1.7 s1.7 s
  5. dockersshoes.com at 2.1 s2.1 s
  6. dockersshoes.com at 2.5 s2.5 s
  7. dockersshoes.com at 3.0 s3.0 s
  8. dockersshoes.com at 3.4 s3.4 s

Speed

5 to fix70
  • Mobile performance score: 70

    70/100

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

  • Render-blocking requests

    650 ms

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

  • Use efficient cache lifetimes

    500 ms · 76 KiB

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

  • Legacy JavaScript

    450 ms · 56 KiB

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

  • Reduce unused JavaScript

    300 ms · 105 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (negate.io, Shopify and Klaviyo and others), adding 336 KiB and 385 ms of main-thread time.

  • Improve image delivery

    249 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    50 KiB

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

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 7.1 s

    7.1 s

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

  • Time to Interactive: 7.1 s

    7.1 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

6 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.9 s

    1.9 s

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Total Blocking Time: 87 ms

    87 ms

    Scripts block the page for only 87 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.50 g

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

1 checks passed
  • Page weight: 1.8 MB in 169 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 169 requests on a phone: other files 736 KiB (98), scripts 608 KiB (56) and images 322 KiB (7). That is a lean page.

Accessibility

4 to fixGoogle 8688
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • All page content should be contained by landmarks (1 element)

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Nashville Shoe Warehouse sells mens, womens, kids shoes-FREE shipping”.

  • Meta description is long (309 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.nashvilleshoewarehouse.com/search?q={search_term_string}")”.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 85 internal links, 0 external

    The homepage links to 85 pages on dockersshoes.com and 0 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “THE BOOTS YOU'VE BEEN WAITING FOR”.

  • Canonical URL set

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

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.nashvilleshoewarehouse.com/collections/men, https://www.nashvilleshoewarehouse.com/collections/womens-styles, https://www.nashvilleshoewarehouse.com/collections/kids, https://www.nashvilleshoewarehouse.com/collections/slip-resistant and https://www.nashvilleshoewarehouse.com/collections/slippers have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.nashvilleshoewarehouse.com/collections has 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 37 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

  • No analytics detected

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

  • Only about 10 words

    The homepage has only about 10 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.

3 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop Shoes”, “Shop by Shoe Type” and “Shop by Brand”.

  • 4 short forms

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

  • Direct contact links

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

Privacy and tracking

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Bm Country Blocker Ip Blocker · Klaviyo Email Marketing Sms · Boostymark Regionblock · bazaarvoice.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
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on dockersshoes.com, including 10 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