Website review, no card needed

fatuite.com logo

fatuite.com website review

Visit site (opens in a new tab)Reviewed 6 November 202647 issues · 88 checks

This review found 47 issues worth fixing on fatuite.com, 19 of them high impact, across 88 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
2.7 s2.0 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.3 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
116 ms91 msMay 16Oct 3194 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026113 ms
May 23, 2026112 ms
May 30, 2026108 ms
Jun 6, 2026106 ms
Jun 13, 2026104 ms
Jun 20, 2026100 ms
Jun 27, 2026100 ms
Jul 4, 2026103 ms
Jul 11, 2026108 ms
Jul 18, 2026108 ms
Jul 25, 2026104 ms
Aug 1, 2026100 ms
Aug 8, 202696 ms
Aug 15, 202695 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202696 ms
Sep 12, 202696 ms
Sep 19, 202697 ms
Sep 26, 202698 ms
Oct 3, 202696 ms
Oct 10, 202695 ms
Oct 17, 202695 ms
Oct 24, 202695 ms
Oct 31, 202694 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 fatuite.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fatuite.com at 0.4 s0.4 s
  2. fatuite.com at 0.8 s0.8 s
  3. fatuite.com at 1.2 s1.2 s
  4. fatuite.com at 1.6 s1.6 s
  5. fatuite.com at 2.0 s2.0 s
  6. fatuite.com at 2.4 s2.4 s
  7. fatuite.com at 2.8 s2.8 s
  8. fatuite.com at 3.1 s3.1 s

Speed

11 to fix58
  • Use efficient cache lifetimes

    21.2 s · 23.8 MB

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

  • Improve image delivery

    17.6 s · 22.8 MB

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

  • Reduce unused JavaScript

    2.6 s · 461 KiB

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

  • Render-blocking requests

    2.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and New Relic and others), adding 24.2 MB and 346 ms of main-thread time.

  • cloudfront.net adds 99 ms

    99 ms

    cloudfront.net costs a phone 99 ms of main-thread work and 23.5 MB 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.

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    610 ms · 113 KiB

    About 113 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.

  • Minify JavaScript

    460 ms · 69 KiB

    69 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 218 ms

    218 ms

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

  • Google Fonts adds 3 ms

    3 ms

    Google Fonts costs a phone 3 ms of main-thread work and 401 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.

  • Minify CSS

    150 ms · 18 KiB

    18 KiB could be saved by minifying CSS.

  • 4 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 154 ms

    154 ms

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

Core Web Vitals

7 to fix100
  • 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: 80.1 s

    80.1 s

    Your largest element takes 80.1 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: 85.2 s

    85.2 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 2 images without width and height

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

8 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 89 ms

    89 ms

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

    1.7 s

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

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

    -16%

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

  • Total Blocking Time: 165 ms

    165 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 24.6 MB in 62 requests

    24.6 MB

    Your homepage downloads 24.6 MB in 62 requests on a phone: images 23.2 MB (20), scripts 865 KiB (8) and fonts 367 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 13 images over 500 KB

    13 images weigh 22.8 MB together. On a phone connection a single image that size takes seconds.

  • 15 images far larger than shown

    21.0 MB

    15 images are downloaded at several times the size a phone draws them, for example fa89474e1dedc1ee1acdff69b5e5bdc9f71cea5f-original.png at 2,536 px wide, shown at 168 px. Resized copies would save about 21.0 MB.

  • 17 images below the first screen load straight away

    17 images further down the page (23.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 17 images in older formats

    17 images (23.0 MB) are 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 7.0 g of CO₂ per visit

    6.98 g

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

Accessibility

10 to fixGoogle 7487
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 12 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Orphan list items

    Some list items are not inside a list.

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

  • 15 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 10080
  • Title is short (7 characters)

    Your title is only 7 characters: “FATUITE”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 short (42 characters)

    Your meta description is only 42 characters: “わがままを、自分らしさに。HAVE YOUR WAY, LOVE YOUR WAY.”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 48 internal links, 2 external

    The homepage links to 48 pages on fatuite.com and 2 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “FATUITE”.

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

AI search readiness

1 to fix83
  • 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://fatuite.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.

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

Other pages

2 to fix90
  • 15 pages share a title

    /, https://fatuite.com/shop/pages/holiday_collection_2026, https://fatuite.com/shop/pages/skincare-subscription-reopening, https://fatuite.com/shop, https://fatuite.com/shop/product_categories/products and https://fatuite.com/shop/pages/close-up and 9 others all use the title “FATUITE”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://fatuite.com/shop/information/henpin-perfectproofuvdefence, https://fatuite.com/shop/pages/holiday_collection_2026, https://fatuite.com/shop/pages/skincare-subscription-reopening, https://fatuite.com/shop, https://fatuite.com/shop/product_categories/products and https://fatuite.com/shop/pages/close-up and 9 others use the same meta description. A description written for each page earns more clicks.

  • 12 pages with very little text

    https://fatuite.com/shop/information/henpin-perfectproofuvdefence, https://fatuite.com/shop/pages/holiday_collection_2026, https://fatuite.com/shop/pages/skincare-subscription-reopening, https://fatuite.com/shop, https://fatuite.com/shop/product_categories/products and https://fatuite.com/shop/pages/close-up and 6 others 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 30 found) and read each the way a search engine does.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 10093
  • 13 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • 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 76 words

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

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

2 checks passed
  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 10 cookies set on arrival

    10

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

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
10 Shopify Products;Shopify;Shopify Plus
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on fatuite.com, including 18 speed issues, 4 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