Website review, no card needed
b-hype.com website review
Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 81 checks
This review found 30 issues worth fixing on b-hype.com, 6 of them high impact, across 81 checks. The most urgent: 7,995 HTML elements. 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
89B- #3,685 of 117,615 reviewed websitesbeats 95%
- #1,903 of 66,923 online storesbeats 95%
- #1,847 of 61,018 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 101 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 102 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 106 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 117 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 118 ms |
| Oct 10, 2026 | 124 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 113 ms |
| Oct 31, 2026 | 124 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
7,995 HTML elements
The page has 7,995 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused JavaScript
259 KiBAbout 259 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 484 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 113 ms
113 msShopify costs a phone 113 ms of main-thread work and 302 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.
7 third-party services on the page
7 third-party services load with your homepage (Shopify, Snapchat and omnisnippet1.com and others), adding 498 KiB and 223 ms of main-thread time.
Improve image delivery
150 ms · 40 KiB2 images could be 40 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 24 KiBAbout 24 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.
Use efficient cache lifetimes
138 KiB12 files are served with short cache lifetimes, so returning visitors download them again (138 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 89 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).
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: 26 ms
26 msYour server sent the HTML in 26 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 4.1 s
4.1 sThe page becomes fully interactive after 4.1 s. Good is under 3.8 s.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 101 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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 CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 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).
Total Blocking Time: 39 ms
39 msScripts block the page for only 39 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.0 MB in 172 requests
2.0 MBYour homepage downloads 2.0 MB in 172 requests on a phone: other files 761 KiB (98), scripts 632 KiB (46) and images 412 KiB (16). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.9 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
16 buttons without a name
16 buttons have no accessible name, so screen readers announce just “button”.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
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.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
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 422 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
269 internal links, 0 external
The homepage links to 269 pages on b-hype.com and 0 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Bhype Society Global Store”.
Title: 56 characters
Your title is a healthy 56 characters: “The Latest Retail & Resale drops with exclusive products”.
Canonical URL set
The canonical URL is https://b-hype.com/.
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://b-hype.com/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 (3,165 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://b-hype.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://b-hype.com/collections/out-now, https://b-hype.com/collections/tees-1, https://b-hype.com/collections/tank-top, https://b-hype.com/collections/hoodies, https://b-hype.com/collections/bhype-sweatpants and https://b-hype.com/collections/tracksuits and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://b-hype.com/collections/swim-short/swim-shorts+swimwear, whose canonical is https://b-hype.com/collections/swim-short. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 107 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
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
13 small tap targets
13 of 32 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 “[Regios Discounts] [USER ERROR] To display discounts on product pages, you need to create an automatic product discount…”.
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
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: 8 trust badges. 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.
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.
About 1,222 words of copy
The homepage carries about 1,222 words of visible text.
2 checks passed
17 calls to action
The homepage has 17 calls to action, for example “SHOP NOW”, “Join the Society” and “SHOP NOWNFL COLLECTIONS”.
296 short forms
296 short forms (1 field at most) are right on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap Pixel and 1 more (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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies, 1 of them by other companies (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.
15 other companies contacted
Loading the homepage contacts 15 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 b-hype.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Mp Size Chart · Regios Discounts · snapchat.com · goaffpro.com · nfcube.com · omnisnippet1.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
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on b-hype.com, including 8 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.