Website review, no card needed
fabuleuse.shop website review
Visit site (opens in a new tab)Reviewed 16 November 202628 issues · 68 checks
This review found 28 issues worth fixing on fabuleuse.shop, 12 of them high impact, across 68 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68D- #103,446 of 117,615 reviewed websitesbeats 10%
- #62,424 of 66,923 online storesbeats 5%
- #57,571 of 61,018 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.3 s |
| Nov 7, 2026 | 3.4 s |
| Nov 14, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 464 ms |
| Jun 6, 2026 | 505 ms |
| Jun 20, 2026 | 510 ms |
| Jun 27, 2026 | 499 ms |
| Jul 4, 2026 | 494 ms |
| Jul 11, 2026 | 523 ms |
| Jul 18, 2026 | 499 ms |
| Jul 25, 2026 | 491 ms |
| Aug 1, 2026 | 423 ms |
| Aug 8, 2026 | 418 ms |
| Aug 15, 2026 | 408 ms |
| Aug 22, 2026 | 423 ms |
| Aug 29, 2026 | 464 ms |
| Sep 5, 2026 | 464 ms |
| Sep 12, 2026 | 464 ms |
| Sep 19, 2026 | 464 ms |
| Sep 26, 2026 | 416 ms |
| Oct 3, 2026 | 380 ms |
| Oct 10, 2026 | 397 ms |
| Oct 17, 2026 | 397 ms |
| Oct 24, 2026 | 397 ms |
| Oct 31, 2026 | 446 ms |
| Nov 7, 2026 | 431 ms |
| Nov 14, 2026 | 409 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
Speed
Use efficient cache lifetimes
1.1 s · 234 KiB2 files are served with short cache lifetimes, so returning visitors download them again (234 KiB).
Reduce unused JavaScript
1.1 s · 190 KiBAbout 190 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 59 KiB4 images could be 59 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Facebook, TikTok and Shopify and others), adding 752 KiB and 260 ms of main-thread time.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 83 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
30 ms · 14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30 ms faster on a phone.
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.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 469 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 8.8 s
8.8 sThe page becomes fully interactive after 8.8 s. Good is under 3.8 s.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 409 ms
409 msReal visitors wait 409 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 464 ms to 409 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 45 ms
45 msScripts block the page for only 45 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 59.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.8 MB in 129 requests
1.8 MBYour homepage downloads 1.8 MB in 129 requests on a phone: other files 664 KiB (69), scripts 628 KiB (26) and fonts 225 KiB (5). That is a lean page.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (9 characters)
Your title is only 9 characters: “Fabuleuse”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
8 internal links, 0 external
The homepage links to 8 pages on fabuleuse.shop and 0 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://fabuleuse.shop/.
Structured data in place
Structured data found: Organization and WebSite.
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://fabuleuse.shop/sitemap.xml.
AI search readiness
No llms.txt
There is no https://fabuleuse.shop/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.
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.
Other pages
3 pages without a meta description
https://fabuleuse.shop/products/crop-top, https://fabuleuse.shop/products/ponytail and https://fabuleuse.shop/products/hair-topper have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://fabuleuse.shop/products/crop-top, https://fabuleuse.shop/products/ponytail and https://fabuleuse.shop/products/hair-topper have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://fabuleuse.shop/products/crop-top, https://fabuleuse.shop/products/ponytail and https://fabuleuse.shop/products/hair-topper 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.
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 3 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 3 pages that loaded have a <title>.
Best practices
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 429 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 10 words
The homepage has only about 10 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
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: TikTok Pixel.
Privacy and tracking
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.
1 other company contacted
Loading the homepage contacts 1 host 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 fabuleuse.shop, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Easysell Cod Form
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 28 issues on fabuleuse.shop, 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.