Website review, no card needed

indochino.com logo

indochino.com website review

Visit site (opens in a new tab)Reviewed 29 October 202637 issues · 84 checks

This review found 37 issues worth fixing on indochino.com, 16 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
3.2 s1.9 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.3 s
Aug 29, 20262.7 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
150 ms137 msMay 9Oct 24144 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026139 ms
May 16, 2026140 ms
May 23, 2026138 ms
May 30, 2026139 ms
Jun 6, 2026142 ms
Jun 13, 2026142 ms
Jun 20, 2026143 ms
Jun 27, 2026144 ms
Jul 4, 2026144 ms
Jul 11, 2026144 ms
Jul 18, 2026142 ms
Jul 25, 2026139 ms
Aug 1, 2026139 ms
Aug 8, 2026139 ms
Aug 15, 2026143 ms
Aug 22, 2026146 ms
Aug 29, 2026146 ms
Sep 5, 2026148 ms
Sep 12, 2026147 ms
Sep 19, 2026146 ms
Sep 26, 2026145 ms
Oct 3, 2026144 ms
Oct 10, 2026144 ms
Oct 17, 2026143 ms
Oct 24, 2026144 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 indochino.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. indochino.com at 0.8 s0.8 s
  2. indochino.com at 1.5 s1.5 s
  3. indochino.com at 2.3 s2.3 s
  4. indochino.com at 3.1 s3.1 s
  5. indochino.com at 3.9 s3.9 s
  6. indochino.com at 4.6 s4.6 s
  7. indochino.com at 5.4 s5.4 s
  8. indochino.com at 6.2 s6.2 s

Speed

10 to fix15
  • Use efficient cache lifetimes

    4.0 s · 7.3 MB

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

  • Reduce unused JavaScript

    5.0 s · 1.9 MB

    About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

  • Render-blocking requests

    5.4 s

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

  • Mobile performance score: 15

    15/100

    Your mobile performance score is 15. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.8 s

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

  • 3,898 HTML elements

    The page has 3,898 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 (Stripe, Facebook and Yottaa and others), adding 1.4 MB and 1.2 s of main-thread time.

  • Improve image delivery

    538 KiB

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

  • Stripe adds 245 ms

    245 ms

    Stripe costs a phone 245 ms of main-thread work and 336 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.

  • alhena.ai adds 84 ms

    84 ms

    alhena.ai costs a phone 84 ms of main-thread work and 318 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    54 KiB

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    17 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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: 76 ms

    76 ms

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

Core Web Vitals

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

  • First Contentful Paint: 8.4 s

    8.4 s

    The first text or image appears after 8.4 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 37.0 s

    37.0 s

    Your largest element takes 37.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BLACK FRIDAY IS HERE”.

  • Time to Interactive: 43.3 s

    43.3 s

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

  • Speed Index: 15.0 s

    15.0 s

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

  • Cumulative Layout Shift: 0.415

    0.415

    The layout shifts by 0.415 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 928 ms

    928 ms

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 139 ms to 144 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-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 154 ms

    154 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user TTFB: 540 ms

    540 ms

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

Images and page weight

1 to fix33
  • Page weight: 12.0 MB in 258 requests

    12.0 MB

    Your homepage downloads 12.0 MB in 258 requests on a phone: images 6.8 MB (53), scripts 4.5 MB (67) and fonts 311 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 3.4 g of CO₂ per visit

    3.40 g

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

Accessibility

2 to fix92
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 tap targets too small

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 checks passed
  • Every image has alt text

    All 89 images in the HTML carry an alt attribute.

SEO

1 to fixGoogle 10097
  • No social preview image

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

  • No X (Twitter) card tag

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

  • 747 internal links, 10 external

    The homepage links to 747 pages on indochino.com and 10 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Explore Indochino: Custom clothing for the modern man. We're innovating the way men dress. Shop made-to-measure suits, …”.

  • One H1 headline

    Your main headline reads: “INDOCHINO Shop Custom Men's Made-to-Measure Suits”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “INDOCHINO | Custom Men's Made-to-Measure Suits”.

  • Canonical URL set

    The canonical URL is https://www.indochino.com/.

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

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

  • Organization data: 6 of 6 facts

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

  • llms.txt published

    The site publishes https://www.indochino.com/llms.txt (38 KiB, 188 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 10 pages share a title

    https://www.indochino.com/collection/premium-suits, https://www.indochino.com/collection/luxury-suits, https://www.indochino.com/collection/black-label-suits, https://www.indochino.com/collection/european-collection, https://www.indochino.com/collection/studio-collection-suits and https://www.indochino.com/collection/black-suits and 4 others all use the title “Access to this page has been denied”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages share a meta description

    https://www.indochino.com/collection/premium-suits, https://www.indochino.com/collection/luxury-suits, https://www.indochino.com/collection/black-label-suits, https://www.indochino.com/collection/european-collection, https://www.indochino.com/collection/studio-collection-suits and https://www.indochino.com/collection/black-suits and 4 others use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://www.indochino.com/collection/suits, https://www.indochino.com/collection/new-arrivals, https://www.indochino.com/collection/best-selling-suits, https://www.indochino.com/collection/sale, https://www.indochino.com/collection/premium-suits and https://www.indochino.com/collection/luxury-suits 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 200 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

4 to fixGoogle 3185
  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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 401 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix56
  • 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 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.

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

  • Only about 18 words

    The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

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

3 checks passed
  • 61 calls to action

    The homepage has 61 calls to action, for example “Shop All Suits”, “Book an appointment.” and “Shop All Tuxedos”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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

  • 4 cookies set on arrival

    4

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

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 indochino.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
AWS

Company

Founded
2007
Headquarters
Vancouver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on indochino.com, including 20 speed issues, 1 SEO issue and 6 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