Website review, no card needed

kswiss.com logo

kswiss.com website review

Visit site (opens in a new tab)Reviewed 5 November 202624 issues · 79 checks

This review found 24 issues worth fixing on kswiss.com, 4 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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 s981 msMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.8 s
Aug 15, 20261.5 s
Aug 22, 20261.3 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
399 ms140 msMay 16Oct 31322 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026170 ms
May 23, 2026186 ms
May 30, 2026203 ms
Jun 6, 2026225 ms
Jun 13, 2026237 ms
Jun 20, 2026236 ms
Jun 27, 2026238 ms
Jul 4, 2026238 ms
Jul 11, 2026237 ms
Jul 18, 2026246 ms
Jul 25, 2026255 ms
Aug 1, 2026267 ms
Aug 8, 2026287 ms
Aug 15, 2026293 ms
Aug 22, 2026305 ms
Aug 29, 2026325 ms
Sep 5, 2026338 ms
Sep 12, 2026358 ms
Sep 19, 2026369 ms
Sep 26, 2026369 ms
Oct 3, 2026358 ms
Oct 10, 2026347 ms
Oct 17, 2026336 ms
Oct 24, 2026326 ms
Oct 31, 2026322 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 kswiss.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kswiss.com at 0.4 s0.4 s
  2. kswiss.com at 0.8 s0.8 s
  3. kswiss.com at 1.1 s1.1 s
  4. kswiss.com at 1.5 s1.5 s
  5. kswiss.com at 1.9 s1.9 s
  6. kswiss.com at 2.3 s2.3 s
  7. kswiss.com at 2.6 s2.6 s
  8. kswiss.com at 3.0 s3.0 s

Speed

5 to fix100
  • Render-blocking requests

    1.6 s

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

  • 3,172 HTML elements

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

  • Use efficient cache lifetimes

    800 ms · 185 KiB

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

  • Improve image delivery

    444 KiB

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

  • Shopify adds 4 ms

    4 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (shgcdn3.com, Shopify and truevaultcdn.com and others), adding 553 KiB and 34 ms of main-thread time.

  • Reduce unused CSS

    33 KiB

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 100

    100/100

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

  • Main-thread work: 0.6 s

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

  • Server response: 18 ms

    18 ms

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

Core Web Vitals

4 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 313 ms

    313 ms

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

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

    +82%

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

  • 3 images without width and height

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

11 checks passed
  • 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 CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 631 ms

    631 ms

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

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

    -41%

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

    0

    The layout barely moves while loading (CLS 0, 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 “🔄”.

  • Speed Index: 1.8 s

    1.8 s

    Visually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.4 s

    1.4 s

    The page is fully interactive after 1.4 s.

Images and page weight

1 to fix85
  • Page weight: 2.4 MB in 137 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 137 requests on a phone: images 1.2 MB (36), scripts 857 KiB (59) and stylesheets 132 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (171 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.7 g of CO₂ per visit

    0.67 g

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

2 checks passed
  • 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

2 to fixGoogle 10098
  • 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 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “K-Swiss: Tennis and Pickleball Shoes & Apparel | Official Store – K-Swiss US”.

  • 10 links crawlers can't follow

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

  • 381 internal links, 21 external

    The homepage links to 381 pages on kswiss.com and 21 external pages.

7 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Founded in California in 1966, K-Swiss is a heritage American tennis brand, known for on-court performance and off-cour…”.

  • One H1 headline

    Your main headline reads: “.header__heading-logo-wrapper{ column-gap: 5px; } .ksrc_logo{ margin-left: 5px; } .ksrc_logo_line{ width: 1px; height: …”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, ShoeStore 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://kswiss.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,542 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix75
  • 1 linked page hidden from search

    https://kswiss.com/pages/page-faq is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://kswiss.com/products/04603-062-m and https://kswiss.com/products/94603-118-m all use the title “HYPERCOURT EXPRESS 3 – K-Swiss US”. 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://kswiss.com/collections/all, https://kswiss.com/policies/shipping-policy, https://kswiss.com/pages/page-faq and https://kswiss.com/pages/k-swiss-60-years have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://kswiss.com/collections/all, https://kswiss.com/products/04437-109-m, https://kswiss.com/products/94437-181-m, https://kswiss.com/products/09483-047-m, https://kswiss.com/products/04603-062-m and https://kswiss.com/products/94603-118-m and 8 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 161 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • A 11-field form

    Your longest form asks for 11 fields (6 required). Every extra field lowers completion.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 299 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 MEN” and “SHOP WOMEN”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “SHOP MEN”, “SHOP WOMEN” and “SHOP MENS”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Opening hours shown

    Your opening hours are on the homepage.

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.

  • 7 cookies set on arrival

    7

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

  • 13 other companies contacted

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

Apps your storefront loads

Geo Pro Geolocation · Intelligems A B Testing · Blockify Fraud Filter · Gift Card Hero All In One · Tinyseo Seo Speed · Pn8fl95fp Opensend · Attentive · Microsoft Clarity · Powerful Form Builder · Klaviyo Email Marketing Sms · Doofinder Search Discovery · Easylocation · Region Restrictions · Swym Wishlist Plus · Giftnote App · Imageagram · signifyd.com · govx.com · pepperjam.com · bogos.io · b-cdn.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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
4 open roles
Job board
careers page

Company

Founded
1966
Headquarters
Westlake Village

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on kswiss.com, including 9 speed issues, 2 SEO issues and 5 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