Website review, no card needed

fairindigo.com logo

fairindigo.com website review

Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 86 checks

This review found 33 issues worth fixing on fairindigo.com, 12 of them high impact, across 86 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
2.0 s1.3 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
209 ms174 msMay 16Oct 31178 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026184 ms
May 23, 2026187 ms
May 30, 2026188 ms
Jun 6, 2026191 ms
Jun 13, 2026196 ms
Jun 20, 2026197 ms
Jun 27, 2026204 ms
Jul 4, 2026203 ms
Jul 11, 2026196 ms
Jul 18, 2026196 ms
Jul 25, 2026191 ms
Aug 1, 2026195 ms
Aug 8, 2026196 ms
Aug 15, 2026198 ms
Aug 22, 2026205 ms
Aug 29, 2026204 ms
Sep 5, 2026198 ms
Sep 12, 2026199 ms
Sep 19, 2026195 ms
Sep 26, 2026194 ms
Oct 3, 2026195 ms
Oct 10, 2026191 ms
Oct 17, 2026187 ms
Oct 24, 2026186 ms
Oct 31, 2026178 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 fairindigo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fairindigo.com at 0.5 s0.5 s
  2. fairindigo.com at 1.1 s1.1 s
  3. fairindigo.com at 1.6 s1.6 s
  4. fairindigo.com at 2.1 s2.1 s
  5. fairindigo.com at 2.6 s2.6 s
  6. fairindigo.com at 3.2 s3.2 s
  7. fairindigo.com at 3.7 s3.7 s
  8. fairindigo.com at 4.2 s4.2 s

Speed

11 to fix35
  • Reduce unused JavaScript

    2.7 s · 749 KiB

    About 749 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Use efficient cache lifetimes

    1.3 s · 230 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 4.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, negate.io and Cloudflare CDN and others), adding 1.7 MB and 1.8 s of main-thread time.

  • Google Tag Manager adds 859 ms

    859 ms

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

  • negate.io adds 473 ms

    473 ms

    negate.io costs a phone 473 ms of main-thread work and 40 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.

  • Render-blocking requests

    450 ms

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

  • 13 long tasks on the main thread

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

  • 1,514 HTML elements

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

  • Shopify adds 74 ms

    74 ms

    Shopify costs a phone 74 ms of main-thread work and 451 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

    150 ms · 18 KiB

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

  • Improve image delivery

    111 KiB

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

  • Minify JavaScript

    25 KiB

    25 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    22 KiB

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 20.4 s

    20.4 s

    Your largest element takes 20.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “organic cotton clothing fair indigo”.

  • Time to Interactive: 22.3 s

    22.3 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Total Blocking Time: 849 ms

    849 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Cumulative Layout Shift: 0.188

    0.188

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

  • Tap response (INP) held steady for real visitors

    -2%

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

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

    1.7 s

    Real visitors wait 1.7 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.2 s

    1.2 s

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

  • Real-user TTFB: 577 ms

    577 ms

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

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

    -20%

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

Images and page weight

2 to fix81
  • Page weight: 3.8 MB in 345 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 345 requests on a phone: scripts 1.8 MB (136), other files 1.0 MB (149) and images 492 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    alpaca_gifts_2026.11.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).

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

5 to fixGoogle 9593
  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • Interactive controls must not be nested (5 elements)

    Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 16 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 55 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • Meta description is long (296 characters)

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

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

  • 171 internal links, 9 external

    The homepage links to 171 pages on fairindigo.com and 9 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Organic clothing made from Pima cotton”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Organic Clothing | Fair Trade Sustainable Clothes | Fair Indigo”.

  • Canonical URL set

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

  • 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://www.fairindigo.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 (737 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.fairindigo.com/pages/organic-pima-cotton-fabrics has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.fairindigo.com/collections/womens-organic-tees-fair-trade-tops, https://www.fairindigo.com/collections/100-organic-cotton-t-shirts and https://www.fairindigo.com/pages/organic-pima-cotton-fabrics have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.fairindigo.com/collections/womens-organic-tees-fair-trade-tops has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://www.fairindigo.com/collections/womens-organic-cotton-long-sleeve-tees and https://www.fairindigo.com/collections/womens-organic-elbow-sleeve-tops-and-tees took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Titles are unique

    Every page we checked has its own title.

  • 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 8891
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Identifier 'helloWidget' has already been declared”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 460 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 WOMENS” and “SHOP MENS”.

  • 26 calls to action

    The homepage has 26 calls to action, for example “> Shop Only 100% Cotton Tees”, “> Shop all 100% Cotton” and “> Shop by Fabric”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 24 testimonial or review blocks and 4 customer or partner logos.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies, 1 of them by other companies (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.

  • 29 other companies contacted

    Loading the homepage contacts 29 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 fairindigo.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

Powerful Form Builder · Keepcart Coupon Protect · Elevar Conversion Tracking · Yotpo Product Reviews · Omnisend · Back In Stock · klevu.com · returngo.ai · zdops.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

Company

Headquarters
Madison

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 fairindigo.com, including 17 speed issues, 2 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