Website review, no card needed

gatsbyshoes.co logo

gatsbyshoes.co website review

Visit site (opens in a new tab)Reviewed 9 November 202627 issues · 80 checks

This review found 27 issues worth fixing on gatsbyshoes.co, 8 of them high impact, across 80 checks. The most urgent: 5 buttons without a name. 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.4 s962 msMay 23Nov 71.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Oct 10, 20261.2 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
116 ms84 msMay 23Oct 2489 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026106 ms
May 30, 2026104 ms
Jun 6, 2026103 ms
Jun 13, 2026112 ms
Jun 20, 2026104 ms
Jun 27, 2026100 ms
Jul 4, 2026100 ms
Jul 11, 202688 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Oct 17, 202696 ms
Oct 24, 202689 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 gatsbyshoes.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gatsbyshoes.co at 0.7 s0.7 s
  2. gatsbyshoes.co at 1.5 s1.5 s
  3. gatsbyshoes.co at 2.2 s2.2 s
  4. gatsbyshoes.co at 3.0 s3.0 s
  5. gatsbyshoes.co at 3.7 s3.7 s
  6. gatsbyshoes.co at 4.5 s4.5 s
  7. gatsbyshoes.co at 5.2 s5.2 s
  8. gatsbyshoes.co at 6.0 s6.0 s

Speed

5 to fix99
  • 3,787 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vitals.app, Shopify and debutify.com and others), adding 1.4 MB and 222 ms of main-thread time.

  • Main-thread work: 2.7 s

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

  • vitals.app adds 199 ms

    199 ms

    vitals.app costs a phone 199 ms of main-thread work and 485 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 23 ms

    23 ms

    Shopify costs a phone 23 ms of main-thread work and 779 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

    210 KiB

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

  • 4 long tasks on the main thread

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

  • Improve image delivery

    77 KiB

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

  • Reduce unused CSS

    76 KiB

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

  • Use efficient cache lifetimes

    61 KiB

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

  • Legacy JavaScript

    10 KiB

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

  • 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
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Server response: 18 ms

    18 ms

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

Core Web Vitals

2 to fix100
  • Time to Interactive: 8.0 s

    8.0 s

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

  • Speed Index: 3.5 s

    3.5 s

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

11 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.0 s

    1.0 s

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 611 ms

    611 ms

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

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

    -12%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 106 ms to 89 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-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.009

    0.009

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Total Blocking Time: 54 ms

    54 ms

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.54 g

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

4 checks passed
  • Page weight: 1.9 MB in 123 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 123 requests on a phone: images 884 KiB (41), scripts 813 KiB (60) and fonts 120 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8492
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 8 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 45 images without alt text

    45 images have no alt text, which hurts accessibility and image search.

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “50% OFF + FREE SHIPPING ON ALL ORDERS!”). One clear main headline is easier for people and search engines.

  • Meta description is long (269 characters)

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

  • Structured data has 3 problems

    Structured data found (BreadcrumbList, Organization and WebSite) but with 3 problems, for example “WebSite: missing name”.

  • 157 internal links, 4 external

    The homepage links to 157 pages on gatsbyshoes.co and 4 external pages.

5 checks passed
  • Title: 39 characters

    Your title is a healthy 39 characters: “GatsbyShoes - Quality Men's Dress Shoes”.

  • Canonical URL set

    The canonical URL is https://gatsbyshoes.co/.

  • 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://gatsbyshoes.co/sitemap.xml.

AI search readiness

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

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 (1,654 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix57
  • 2 linked pages are broken

    Your homepage links to https://gatsbyshoes.co/www.pinterest.com/gatsbyshoesco and https://gatsbyshoes.co/www.youtube.com/@gatsbyshoesco, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 4 pages share 2 titles

    https://gatsbyshoes.co/products/oxford-lisse and https://gatsbyshoes.co/products/oxford-lisse-all-day-comfort-dress-shoe-copy all use the title “Oxford Lisse Dress Shoes | Premium Leather Comfort | GatsbyShoes”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://gatsbyshoes.co/collections/our-shoes, https://gatsbyshoes.co/pages/contact-us, https://gatsbyshoes.co/pages/about-us and https://gatsbyshoes.co/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://gatsbyshoes.co/products/oxford-lisse and https://gatsbyshoes.co/products/oxford-lisse-all-day-comfort-dress-shoe-copy use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://gatsbyshoes.co/collections/our-shoes, https://gatsbyshoes.co/apps/trackingmore, https://gatsbyshoes.co/pages/contact-us, https://gatsbyshoes.co/pages/about-us, https://gatsbyshoes.co/products/oxford-lisse and https://gatsbyshoes.co/products/oxford-no-stripe-lisse-orthopedic-dress-shoe and 3 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 45 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://gatsbyshoes.co/cdn/shop/t/59/assets/tiny.content.min.css?v=17023' because its MIME…”.

2 checks passed
  • Tap targets are thumb-sized

    105 of 121 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 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.

  • About 2,202 words of copy

    The homepage carries about 2,202 words of visible text.

  • Urgency cues

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

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Track My Order”, “Contact Us” and “Learn More About Our Story ⟶”.

  • 22 short forms

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

  • Social proof on the page

    Social proof on the homepage: 76 testimonial or review blocks and 1 trust badge.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 gatsbyshoes.co, 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 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Pagefly Ai Page Builder · Klaviyo Email Marketing Sms · Redo · Vitals · Countdown Timer · Stape Remix · Zipify Oneclickupsell · kiwisizing.com · trackingmore.net · getredo.com · nfcube.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
Gatsby
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 27 issues on gatsbyshoes.co, including 7 speed issues, 3 SEO issues and 3 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