Website review, no card needed

paneshoes.com logo

paneshoes.com website review

Visit site (opens in a new tab)Reviewed 4 November 202632 issues · 80 checks

This review found 32 issues worth fixing on paneshoes.com, 9 of them high impact, across 80 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
1.3 s896 msMay 16Oct 31958 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.2 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.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 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.1 s
Oct 3, 20261.1 s
Oct 10, 20261.0 s
Oct 17, 2026958 ms
Oct 24, 2026945 ms
Oct 31, 2026958 ms
Real-visitor tap response (INP)75th percentile, phones
112 ms93 msMay 16Oct 31110 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202695 ms
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202696 ms
Jun 20, 202698 ms
Jun 27, 2026101 ms
Jul 4, 2026102 ms
Jul 11, 2026102 ms
Jul 18, 2026103 ms
Jul 25, 2026101 ms
Aug 1, 2026102 ms
Aug 8, 2026102 ms
Aug 15, 2026102 ms
Aug 22, 2026103 ms
Aug 29, 2026101 ms
Sep 5, 2026100 ms
Sep 12, 2026101 ms
Sep 19, 2026104 ms
Sep 26, 2026104 ms
Oct 3, 2026105 ms
Oct 10, 2026107 ms
Oct 17, 2026108 ms
Oct 24, 2026109 ms
Oct 31, 2026110 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 paneshoes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. paneshoes.com at 0.9 s0.9 s
  2. paneshoes.com at 1.7 s1.7 s
  3. paneshoes.com at 2.6 s2.6 s
  4. paneshoes.com at 3.4 s3.4 s
  5. paneshoes.com at 4.3 s4.3 s
  6. paneshoes.com at 5.1 s5.1 s
  7. paneshoes.com at 6.0 s6.0 s
  8. paneshoes.com at 6.9 s6.9 s

Speed

11 to fix61
  • Reduce unused JavaScript

    1.5 s · 373 KiB

    About 373 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.

  • Render-blocking requests

    1.3 s

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

  • Improve image delivery

    250 ms · 802 KiB

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

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61. 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 (ContentSquare, Shopify and 506.io and others), adding 1.6 MB and 653 ms of main-thread time.

  • Use efficient cache lifetimes

    450 ms · 213 KiB

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

  • Shopify adds 278 ms

    278 ms

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

  • Main-thread work: 3.4 s

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

  • ContentSquare adds 324 ms

    324 ms

    ContentSquare costs a phone 324 ms of main-thread work and 168 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.

  • Legacy JavaScript

    300 ms · 27 KiB

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

  • 1,810 HTML elements

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

  • Reduce unused CSS

    150 ms · 21 KiB

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

  • 3 long tasks on the main thread

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 15.6 s

    15.6 s

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

  • Time to Interactive: 20.3 s

    20.3 s

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

  • Speed Index: 10.8 s

    10.8 s

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

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

  • 14 images without width and height

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

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

    +15%

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

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: 1.3 s

    1.3 s

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

  • Real-user INP: 112 ms

    112 ms

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

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

    1.1 s

    Real visitors see the first content after 1.1 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.

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

    -24%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.0 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).

  • Total Blocking Time: 23 ms

    23 ms

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

Images and page weight

2 to fix64
  • Page weight: 5.2 MB in 337 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 337 requests on a phone: images 2.5 MB (38), scripts 1.5 MB (137) and other files 827 KiB (142). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    ck_banner_c3200bcc-7e37-4f5c-a604-fc1424f0d8c9.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).

  • About 1.5 g of CO₂ per visit

    1.48 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9596
  • 7 tap targets too small

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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 → h6), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 107 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

Google 100100
  • 109 internal links, 7 external

    The homepage links to 109 pages on paneshoes.com and 7 external pages.

8 checks passed
  • Meta description: 75 characters

    Your meta description is 75 characters: “Clean minimalist sneakers with premium leather. Designed for everyday wear.”.

  • One H1 headline

    Your main headline reads: “pane”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Minimalist Leather Sneakers | PANE Official”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://paneshoes.com/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing sameAs (social profiles), 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 (686 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://paneshoes.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://paneshoes.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://paneshoes.com/pages/a-season-of-small-joy, https://paneshoes.com/customer_authentication/redirect, https://paneshoes.com/pages/about, https://paneshoes.com/pages/stores-list, https://paneshoes.com/collections/women-s and https://paneshoes.com/collections/new-arrivals-1 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://paneshoes.com/pages/a-season-of-small-joy, https://paneshoes.com/customer_authentication/redirect, https://paneshoes.com/pages/about and https://paneshoes.com/pages/stores-list 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 47 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.

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

Best practices

3 to fixGoogle 9679
  • 11 small tap targets

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

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Contentsquare tag 372900 skipped: another Contentsquare tag already runs”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 320 words of copy

    The homepage carries about 320 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET A FIRST LOOK”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Get a First Look”, “Shop Now” and “Subscribe”.

  • 8 short forms

    8 short forms (7 fields at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 19 cookies set on arrival

    19

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 paneshoes.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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Bm Country Blocker Ip Blocker · Hotjar Install · Inbox · Judge Me Reviews · Eg Auto Add To Cart · Seowill Page Speed · Boostymark Regionblock · Peppyduck Restock Whatsapp · Tms Prod V Ba10564 · Chizy Ai Chatbot · Pify Order Purchase Limit · Ecomsend · cloudfront.net

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 32 issues on paneshoes.com, including 16 speed 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