Website review, no card needed

1587sneakers.com logo

1587sneakers.com website review

Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 76 checks

This review found 33 issues worth fixing on 1587sneakers.com, 5 of them high impact, across 76 checks. The most urgent: scrollable region must have keyboard access (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
1.3 s720 msMay 23Nov 7972 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026840 ms
May 30, 2026804 ms
Jun 6, 2026788 ms
Jun 13, 2026812 ms
Jun 20, 2026828 ms
Jun 27, 2026984 ms
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 2026981 ms
Sep 5, 2026990 ms
Sep 12, 2026973 ms
Sep 19, 2026993 ms
Sep 26, 20261.1 s
Oct 3, 2026928 ms
Oct 10, 2026911 ms
Oct 17, 2026923 ms
Oct 24, 2026908 ms
Oct 31, 2026989 ms
Nov 7, 2026972 ms
Real-visitor tap response (INP)75th percentile, phones
135 ms91 msMay 23Nov 7120 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202697 ms
Jun 13, 2026101 ms
Jun 20, 2026104 ms
Jun 27, 2026104 ms
Jul 4, 2026113 ms
Jul 11, 2026120 ms
Jul 18, 2026124 ms
Jul 25, 2026129 ms
Aug 1, 2026130 ms
Aug 8, 2026121 ms
Aug 15, 2026122 ms
Aug 22, 2026120 ms
Aug 29, 2026116 ms
Sep 5, 2026113 ms
Sep 12, 2026104 ms
Sep 19, 2026103 ms
Sep 26, 2026121 ms
Oct 3, 2026116 ms
Oct 10, 2026112 ms
Oct 17, 2026113 ms
Oct 24, 2026112 ms
Oct 31, 2026112 ms
Nov 7, 2026120 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 1587sneakers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1587sneakers.com at 0.5 s0.5 s
  2. 1587sneakers.com at 1.0 s1.0 s
  3. 1587sneakers.com at 1.5 s1.5 s
  4. 1587sneakers.com at 1.9 s1.9 s
  5. 1587sneakers.com at 2.4 s2.4 s
  6. 1587sneakers.com at 2.9 s2.9 s
  7. 1587sneakers.com at 3.4 s3.4 s
  8. 1587sneakers.com at 3.9 s3.9 s

Speed

11 to fix65
  • Reduce unused JavaScript

    300 ms · 928 KiB

    About 928 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 (route.com, loox.io and Klaviyo and others), adding 1.6 MB and 1.0 s of main-thread time.

  • Use efficient cache lifetimes

    1.1 MB

    14 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Improve image delivery

    600 ms · 473 KiB

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

  • Mobile performance score: 65

    65/100

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

  • route.com adds 637 ms

    637 ms

    route.com costs a phone 637 ms of main-thread work and 1.1 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.

  • Duplicated JavaScript

    150 ms · 523 KiB

    523 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    500 ms

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 67 KiB

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

  • Main-thread work: 3.0 s

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

  • Legacy JavaScript

    33 KiB

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

  • Minify CSS

    6 KiB

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

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
  • Time to Interactive: 18.0 s

    18.0 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

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

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

    +21%

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

  • Total Blocking Time: 423 ms

    423 ms

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

  • Speed Index: 4.8 s

    4.8 s

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

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

8 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 INP: 120 ms

    120 ms

    Real visitors wait 120 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: 0.7 s

    0.7 s

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

  • Real-user TTFB: 394 ms

    394 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

3 to fix74
  • Page weight: 3.8 MB in 188 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 188 requests on a phone: scripts 1.7 MB (79), images 1.2 MB (21) and other files 690 KiB (69). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    251109_1587_x_ddk_ECOMM_GROUP-030.jpg 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).

  • 2 images far larger than shown

    33 KiB

    2 images are downloaded at several times the size a phone draws them, for example Approved_1_e7d7470a-13d0-42a8-88ca-5e721781de8d.png at 390 px wide, shown at 120 px. Resized copies would save about 33 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (109 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.09 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.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 use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9396
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 27 images without alt text

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

  • 42 links without text

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

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 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 8576
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (13 characters)

    Your title is only 13 characters: “1587 Sneakers”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 88 internal links, 10 external

    The homepage links to 88 pages on 1587sneakers.com and 10 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “1587 Sneakers”.

  • Canonical URL set

    The canonical URL is https://www.1587sneakers.com/.

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

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.1587sneakers.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9687
  • 34 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 502 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 5 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 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 384 words of copy

    The homepage carries about 384 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 29 calls to action

    The homepage has 29 calls to action, for example “Shop”, “Apply” and “SHOP NOW”.

  • 4 short forms

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

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 35 other companies contacted

    Loading the homepage contacts 35 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 1587sneakers.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Reelup Shoppable Videos Reels · Route Protection Tracking · Inbox · Klaviyo Email Marketing Sms · Selleasy · loox.io · nfcube.com · govx.com · kaktusapp.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
SvelteKit
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Boston

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on 1587sneakers.com, including 16 speed issues, 4 SEO 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