Website review, no card needed

tukshoes.com logo

tukshoes.com website review

Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 82 checks

This review found 33 issues worth fixing on tukshoes.com, 8 of them high impact, across 82 checks. The most urgent: improve image delivery. 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.0 s932 msMay 16Oct 31982 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026982 ms
May 23, 2026967 ms
May 30, 2026967 ms
Jun 6, 2026955 ms
Jun 13, 2026965 ms
Jun 20, 2026984 ms
Jun 27, 2026993 ms
Jul 4, 20261.0 s
Jul 11, 2026966 ms
Jul 18, 2026943 ms
Jul 25, 2026941 ms
Aug 1, 2026941 ms
Aug 8, 2026960 ms
Aug 15, 2026976 ms
Aug 22, 2026982 ms
Aug 29, 2026988 ms
Sep 5, 2026980 ms
Sep 12, 2026991 ms
Sep 19, 2026987 ms
Sep 26, 2026982 ms
Oct 3, 2026988 ms
Oct 10, 2026985 ms
Oct 17, 2026997 ms
Oct 24, 2026991 ms
Oct 31, 2026982 ms
Real-visitor tap response (INP)75th percentile, phones
110 ms100 msMay 16Oct 31105 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026102 ms
May 23, 2026101 ms
May 30, 2026103 ms
Jun 6, 2026104 ms
Jun 13, 2026104 ms
Jun 20, 2026104 ms
Jun 27, 2026105 ms
Jul 4, 2026107 ms
Jul 11, 2026106 ms
Jul 18, 2026105 ms
Jul 25, 2026105 ms
Aug 1, 2026105 ms
Aug 8, 2026106 ms
Aug 15, 2026106 ms
Aug 22, 2026106 ms
Aug 29, 2026106 ms
Sep 5, 2026107 ms
Sep 12, 2026109 ms
Sep 19, 2026109 ms
Sep 26, 2026107 ms
Oct 3, 2026106 ms
Oct 10, 2026105 ms
Oct 17, 2026105 ms
Oct 24, 2026105 ms
Oct 31, 2026105 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 tukshoes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tukshoes.com at 0.6 s0.6 s
  2. tukshoes.com at 1.2 s1.2 s
  3. tukshoes.com at 1.9 s1.9 s
  4. tukshoes.com at 2.5 s2.5 s
  5. tukshoes.com at 3.1 s3.1 s
  6. tukshoes.com at 3.7 s3.7 s
  7. tukshoes.com at 4.3 s4.3 s
  8. tukshoes.com at 4.9 s4.9 s

Speed

9 to fix68
  • Improve image delivery

    2.3 s · 1.2 MB

    14 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68. 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 (Google Tag Manager, Shopify and Klaviyo and others), adding 1.5 MB and 820 ms of main-thread time.

  • Render-blocking requests

    850 ms

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

  • Reduce unused JavaScript

    150 ms · 524 KiB

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

  • Google Tag Manager adds 308 ms

    308 ms

    Google Tag Manager costs a phone 308 ms of main-thread work and 522 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.

  • Main-thread work: 2.6 s

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

  • 1,735 HTML elements

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

  • Klaviyo adds 132 ms

    132 ms

    Klaviyo costs a phone 132 ms of main-thread work and 327 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 CSS

    150 ms · 55 KiB

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

  • Use efficient cache lifetimes

    172 KiB

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

  • 8 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    28 KiB

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

  • Minify CSS

    13 KiB

    13 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: 9 ms

    9 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 9.3 s

    9.3 s

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

  • Time to Interactive: 21.4 s

    21.4 s

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

  • 68 images without width and height

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

  • Speed Index: 5.4 s

    5.4 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

    113 ms

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

  • Real-user CLS: 0.06

    0.06

    For real visitors the layout shifts by 0.06 (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: 494 ms

    494 ms

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

  • Total Blocking Time: 193 ms

    193 ms

    Scripts block the page for only 193 ms while loading. Good is under 200 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

2 to fix63
  • Page weight: 4.2 MB in 237 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 237 requests on a phone: images 1.6 MB (28), scripts 1.5 MB (92) and other files 748 KiB (89). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.19 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 142.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 9396
  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • 2 tap targets too small

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 50 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

6 to fixGoogle 9270
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “T.U.K. Footwear | Creeper Shoes, Platforms, Punk Boots, Vegan Shoes”.

  • No structured data

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

  • Meta description is long (315 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 146 internal links, 8 external

    The homepage links to 146 pages on tukshoes.com and 8 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.tukshoes.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.tukshoes.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 (519 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.tukshoes.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://www.tukshoes.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

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

  • 2 pages without a meta description

    https://www.tukshoes.com/customer_authentication/redirect and https://www.tukshoes.com/collections/restock-collection have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.tukshoes.com/customer_authentication/redirect, https://www.tukshoes.com/collections/new-arrivals, https://www.tukshoes.com/collections/womens-new-arrivals, https://www.tukshoes.com/collections/mens-new-arrivals, https://www.tukshoes.com/collections/anarchic and https://www.tukshoes.com/collections/restock-collection and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.tukshoes.com/customer_authentication/redirect, https://www.tukshoes.com/collections/anarchic, https://www.tukshoes.com/collections/restock-collection, https://www.tukshoes.com/collections/womens and https://www.tukshoes.com/collections/womens-creepers took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 99 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

2 to fixGoogle 9687
  • 54 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 473 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGN UP”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Women Shop All”, “Men Shop All” and “Shop All”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 38 testimonial or review blocks and 8 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 27 cookies set on arrival

    27

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

  • 47 other companies contacted

    Loading the homepage contacts 47 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 tukshoes.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

Klaviyo Email Marketing Sms · Judge Me Reviews · Redo · Attentive · Instafeed · Managed Markets · attn.tv · esc-apps-cdn.com · kxcdn.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
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Poway

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 tukshoes.com, including 13 speed issues, 6 SEO issues and 1 conversion gap. 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