Website review, no card needed
bibiy.store website review
Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 82 checks
This review found 34 issues worth fixing on bibiy.store, 11 of them high impact, across 82 checks. The most urgent: fails Core Web Vitals for real visitors. 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
75C- #79,760 of 121,555 reviewed websitesbeats 30%
- #50,854 of 68,770 online storesbeats 22%
- #48,044 of 62,664 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 114 ms |
| May 23, 2026 | 116 ms |
| May 30, 2026 | 117 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 133 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 126 ms |
| Oct 31, 2026 | 126 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
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 1.9 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 (channel.io, Google Tag Manager and Clarity and others), adding 1.4 MB and 1.1 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 428 KiBAbout 428 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
550 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
channel.io adds 407 ms
407 mschannel.io costs a phone 407 ms of main-thread work and 342 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 Tag Manager adds 249 ms
249 msGoogle Tag Manager costs a phone 249 ms of main-thread work and 323 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.
2,303 HTML elements
The page has 2,303 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
JSDelivr CDN adds 106 ms
106 msJSDelivr CDN costs a phone 106 ms of main-thread work and 323 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 · 76 KiBAbout 76 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
86 KiB63 files are served with short cache lifetimes, so returning visitors download them again (86 KiB).
Improve image delivery
43 KiB4 images could be 43 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 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.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 445 ms
445 msScripts block taps and scrolling for 445 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 114 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 603 ms
603 msReal visitors wait 603 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 356 requests
4.4 MBYour homepage downloads 4.4 MB in 356 requests on a phone: images 1.7 MB (120), scripts 1.6 MB (116) and other files 755 KiB (95). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (70 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.3 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
47 tap targets too small
47 tap targets are too small or too close together to hit reliably with a finger.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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 skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 97 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “Bibiy.|OFFICIAL ONLINE STORE”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (68 characters)
Your meta description is only 68 characters: “BIBIY. Develop a playful collection for "feminine and strong women."”. 70 to 160 characters is enough to sell the click.
106 internal links, 11 external
The homepage links to 106 pages on bibiy.store and 11 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Bibiy.”.
Canonical URL set
The canonical URL is https://bibiy.store/en.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://bibiy.store/sitemap.xml.
AI search readiness
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.
3 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 (773 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bibiy.store/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://bibiy.store/en/blogs/News/How%20to%20link%20online%20account%20and%20LINE-ID and https://bibiy.store/en/blogs/News/Similar%20products-Counterfeit%20products-Notice%20regarding%20illegal%20resale, which answer with an error. Visitors hit a dead end and search engines drop them.
5 pages without a meta description
https://bibiy.store/en/collections/26aw-new-10-2, https://bibiy.store/en/collections/bestseller, https://bibiy.store/en/collections/26ss-collection, https://bibiy.store/en/collections/26aw-collection and https://bibiy.store/en/collections/bestseller-knit-outerwear have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://bibiy.store/en/blogs/%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9/26aw-osaka-popup-store, whose canonical is https://bibiy.store/en/blogs/%e3%83%8b%e3%83%a5%e3%83%bc%e3%82%b9/26aw-osaka-popup-store. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages without an H1
https://bibiy.store/en/blogs/%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9/26aw-osaka-popup-store, https://bibiy.store/en/blogs/%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9/26aw-nagoya-popup-store, https://bibiy.store/en/collections/26aw-new-10-2, https://bibiy.store/en/collections/bestseller, https://bibiy.store/en/collections/prefer-order and https://bibiy.store/en/collections/all and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://bibiy.store/en/collections/26aw-collection took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
3 checks passed
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 13 pages that loaded have a <title>.
Best practices
60 small tap targets
60 of 82 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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 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 227 words
The homepage has only about 227 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.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “PRE-ORDER”, “Shop by Look” and “Start shopping”.
19 short forms
19 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
35 other companies contacted
Loading the homepage contacts 35 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 bibiy.store, 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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Langshop · Boost Ai Search Filter · Instafeed · Min Max Limits By Limitsify · Helium Customer Fields · Swish Wishlist King · channel.io · mixlogue.jp · zdops.net · useamp.com · Swym Wishlist Plus
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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify Hosted
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on bibiy.store, including 16 speed issues, 2 SEO issues and 4 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.