Website review, no card needed

fabulyssboutique.com logo

fabulyssboutique.com website review

Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 82 checks

This review found 36 issues worth fixing on fabulyssboutique.com, 10 of them high impact, across 82 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
1.2 s1.1 sMay 30Oct 31.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
169 ms125 msJul 4Oct 3130 ms
Show as table
DateReal-visitor tap response (INP)
Jul 4, 2026159 ms
Jul 11, 2026162 ms
Jul 18, 2026159 ms
Jul 25, 2026163 ms
Aug 1, 2026163 ms
Aug 8, 2026161 ms
Aug 15, 2026164 ms
Aug 22, 2026161 ms
Aug 29, 2026154 ms
Sep 5, 2026161 ms
Sep 12, 2026154 ms
Sep 19, 2026146 ms
Oct 3, 2026130 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 fabulyssboutique.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fabulyssboutique.com at 0.9 s0.9 s
  2. fabulyssboutique.com at 1.8 s1.8 s
  3. fabulyssboutique.com at 2.7 s2.7 s
  4. fabulyssboutique.com at 3.6 s3.6 s
  5. fabulyssboutique.com at 4.5 s4.5 s
  6. fabulyssboutique.com at 5.4 s5.4 s
  7. fabulyssboutique.com at 6.3 s6.3 s
  8. fabulyssboutique.com at 7.2 s7.2 s

Speed

8 to fix64
  • Use efficient cache lifetimes

    3.4 s · 593 KiB

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

  • Reduce unused JavaScript

    2.1 s · 433 KiB

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

  • 4,053 HTML elements

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

  • Mobile performance score: 64

    64/100

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

  • Improve image delivery

    100 ms · 470 KiB

    4 images could be 470 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (route.com, Shopify and Snapchat and others), adding 1.2 MB and 322 ms of main-thread time.

  • route.com adds 172 ms

    172 ms

    route.com costs a phone 172 ms of main-thread work and 542 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.

  • Shopify adds 96 ms

    96 ms

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

  • Reduce unused CSS

    150 ms · 71 KiB

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

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    7 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.3 s

    13.3 s

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

  • Time to Interactive: 13.5 s

    13.5 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

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

    1.6 s

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

  • Real-user INP: 128 ms

    128 ms

    Real visitors wait 128 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: 604 ms

    604 ms

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

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

    -14%

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

  • Total Blocking Time: 88 ms

    88 ms

    Scripts block the page for only 88 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

3 to fix69
  • Page weight: 3.6 MB in 357 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 357 requests on a phone: scripts 1.2 MB (164), other files 1.0 MB (151) and images 1,003 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Orange_and_Yellow_Simple_Welcome_Autumn_Banner.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).

  • 2 images far larger than shown

    192 KiB

    2 images are downloaded at several times the size a phone draws them, for example Orange_and_Yellow_Simple_Welcome_Autumn_Banner.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 192 KiB.

  • About 1.0 g of CO₂ per visit

    1.01 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9596
  • 13 text elements with low contrast

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

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail 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 (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Fabulyss Boutique: Stylish Self-Defense Keychains & Women's Personal S – Fab BTQ”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Fab BTQ” and “PROTECTION YOU CAN CARRY WITH CONFIDENCE!”). One clear main headline is easier for people and search engines.

  • Meta description is long (220 characters)

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 119 internal links, 2 external

    The homepage links to 119 pages on fabulyssboutique.com and 2 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://fabulyssbtq.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 (1,538 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://fabulyssbtq.com/collections/new-arrival, https://fabulyssbtq.com/collections/recently-restocked, https://fabulyssbtq.com/collections/self-defense-accessories, https://fabulyssbtq.com/collections/stun-guns, https://fabulyssbtq.com/collections/discrete-items and https://fabulyssbtq.com/collections/knifes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://fabulyssbtq.com/pages/contact-us, https://fabulyssbtq.com/collections/new-arrival, https://fabulyssbtq.com/collections/recently-restocked, https://fabulyssbtq.com/collections/self-defense-accessories, https://fabulyssbtq.com/collections/stun-guns and https://fabulyssbtq.com/collections/discrete-items and 1 other 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 57 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • 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 7 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://dr8h81twidjpw.cloudfront.net/uploads/popup_setting/popup_logo_img/Untitled907-20210115173053_2102160508.PNG.

  • 9 small tap targets

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

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

  • 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

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 177 words

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

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “CONTACT”, “SHOP” and “Join now”.

  • 4 short forms

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

  • 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

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Snap Pixel (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.

  • 5 cookies set on arrival

    5

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

  • 16 other companies contacted

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

Apps your storefront loads

Hulk Age Verification · Slicktext · Countdown Timer · Order Value Booster · Loyalty Program · snapchat.com · route.com · activehosted.com

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on fabulyssboutique.com, including 13 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