Website review, no card needed

faire.com logo

faire.com website review

Visit site (opens in a new tab)Reviewed 12 October 202639 issues · 85 checks

This review found 39 issues worth fixing on faire.com, 15 of them high impact, across 85 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.5 s2.3 sApr 18Oct 32.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.4 s
Apr 25, 20262.4 s
May 2, 20262.4 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
326 ms254 msApr 18Oct 3316 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026265 ms
Apr 25, 2026262 ms
May 2, 2026268 ms
May 9, 2026266 ms
May 16, 2026265 ms
May 23, 2026271 ms
May 30, 2026271 ms
Jun 6, 2026281 ms
Jun 13, 2026288 ms
Jun 20, 2026294 ms
Jun 27, 2026301 ms
Jul 4, 2026306 ms
Jul 11, 2026313 ms
Jul 18, 2026318 ms
Jul 25, 2026318 ms
Aug 1, 2026312 ms
Aug 8, 2026308 ms
Aug 15, 2026308 ms
Aug 22, 2026308 ms
Aug 29, 2026312 ms
Sep 5, 2026314 ms
Sep 12, 2026316 ms
Sep 19, 2026314 ms
Sep 26, 2026315 ms
Oct 3, 2026316 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 faire.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. faire.com at 0.5 s0.5 s
  2. faire.com at 0.9 s0.9 s
  3. faire.com at 1.4 s1.4 s
  4. faire.com at 1.8 s1.8 s
  5. faire.com at 2.3 s2.3 s
  6. faire.com at 2.8 s2.8 s
  7. faire.com at 3.2 s3.2 s
  8. faire.com at 3.7 s3.7 s

Speed

9 to fix37
  • Render-blocking requests

    3.1 s

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

  • Reduce unused JavaScript

    1.4 s · 1,014 KiB

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

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 6.3 s

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

  • Improve image delivery

    5.3 MB

    18 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    300 ms · 3.3 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.4 MB and 1.5 s of main-thread time.

  • Google Tag Manager adds 679 ms

    679 ms

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

  • Facebook adds 312 ms

    312 ms

    Facebook costs a phone 312 ms of main-thread work and 340 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.

  • 18 long tasks on the main thread

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

  • Legacy JavaScript

    66 KiB

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 86 ms

    86 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 18.9 s

    18.9 s

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

  • Time to Interactive: 52.0 s

    52.0 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Total Blocking Time: 906 ms

    906 ms

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

  • Real-user INP: 405 ms

    405 ms

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

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

    +20%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user CLS: 0.09

    0.09

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

  • Real-user TTFB: 717 ms

    717 ms

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

  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

2 to fix50
  • Page weight: 13.3 MB in 348 requests

    13.3 MB

    Your homepage downloads 13.3 MB in 348 requests on a phone: images 6.0 MB (34), scripts 3.7 MB (185) and media 2.6 MB (1). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    573 KiB

    6 images are downloaded at several times the size a phone draws them, for example 13a083e49afe827d88bcb4a76b4ef731ff4d9258b74e625a8b264a49c32a at 2,000 px wide, shown at 358 px. Resized copies would save about 573 KiB.

  • About 3.8 g of CO₂ per visit

    3.78 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.78 g of CO₂e: 453.7 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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 8491
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Alternative text of images should not be repeated as text (10 elements)

    Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 7790
  • No structured data

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

  • No XML sitemap

    No XML sitemap at https://www.faire.com/sitemap-index.xml.gz, so Google discovers your pages only by following links.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 56 internal links, 3 external

    The homepage links to 56 pages on faire.com and 3 external pages.

6 checks passed
  • Meta description: 77 characters

    Your meta description is 77 characters: “Faire is the platform connecting thousands of brands and retailers worldwide.”.

  • One H1 headline

    Your main headline reads: “Find your next bestseller”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Your one-stop shop for wholesale - Faire”.

  • Canonical URL set

    The canonical URL is https://www.faire.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.

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.

  • No llms.txt

    There is no https://www.faire.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 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 (821 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 1 linked page hidden from search

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

  • 4 pages share a title

    /, https://www.faire.com/apply, https://www.faire.com/about and https://www.faire.com/affiliates all use the title “Your one-stop shop for wholesale - Faire”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://www.faire.com/apply, https://www.faire.com/about and https://www.faire.com/affiliates use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://www.faire.com/apply, https://www.faire.com/suppliers/All%20Brands/brand-value/women-owned, https://www.faire.com/suppliers/Beauty%20&%20Wellness/subcategory/Skincare/Creams%20&%20Moisturizers, https://www.faire.com/about, https://www.faire.com/news and https://www.faire.com/careers and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.faire.com/suppliers/All%20Brands/brand-value/women-owned, https://www.faire.com/suppliers/Beauty%20&%20Wellness/subcategory/Skincare/Creams%20&%20Moisturizers, https://www.faire.com/about and https://www.faire.com/open-with-faire have 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    9 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 meta description

    All 9 pages that loaded have a meta description.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5483
  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

  • 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: net::ERR_FAILED”.

  • Browser-reported issues

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

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 form on the homepage

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

  • About 336 words of copy

    The homepage carries about 336 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 to buy” and “Sign up to sell”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Sign up to buy”, “Sign up to sell” and “Shop women owned”.

  • Social proof on the page

    Social proof on the homepage: 1 trust badge and “over 100,000 brands”.

  • Analytics in place

    Analytics detected: Meta Pixel.

  • 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

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 8 other companies contacted

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

2 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on faire.com, including 18 speed issues, 3 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