Website review, no card needed
bohme.com website review
Visit site (opens in a new tab)Reviewed 5 November 202637 issues · 86 checks
This review found 37 issues worth fixing on bohme.com, 13 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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- #77,362 of 117,405 reviewed websitesbeats 30%
- #49,589 of 66,899 online storesbeats 22%
- #46,881 of 61,006 Shopify storesbeats 19%
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.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 120 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 123 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 142 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 147 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 129 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
Render-blocking requests
1.6 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 23
23/100Your mobile performance score is 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
700 ms · 1.2 MB35 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Improve image delivery
700 ms · 1.1 MB21 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and Shopify and others), adding 1.8 MB and 1.5 s of main-thread time.
Reduce unused JavaScript
600 ms · 996 KiBAbout 996 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 453 ms
453 msGoogle Tag Manager costs a phone 453 ms of main-thread work and 528 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 168 ms
168 msShopify costs a phone 168 ms of main-thread work and 340 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.
Yotpo adds 163 ms
163 msYotpo costs a phone 163 ms of main-thread work and 328 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.
1,923 HTML elements
The page has 1,923 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 33 KiBAbout 33 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.
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 28.8 s
28.8 sThe page becomes fully interactive after 28.8 s. Good is under 3.8 s.
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 element shown below.
Cumulative Layout Shift: 0.847
0.847The layout shifts by 0.847 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 612 ms
612 msScripts block taps and scrolling for 612 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 120 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 88 ms
88 msReal visitors wait 88 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (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.
Real-user TTFB: 615 ms
615 msReal visitors wait 615 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 12.4 MB in 474 requests
12.4 MBYour homepage downloads 12.4 MB in 474 requests on a phone: media 6.2 MB (1), scripts 2.4 MB (122) and images 1.9 MB (30). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
20261015_SweatersHomepage-06_400x560_crop_center.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).
1 image below the first screen load straight away
1 image further down the page (152 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.50 g of CO₂e: 420.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
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
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.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
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. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Bohme | Shop Our Curated Collections of Unique & High Quality Clothing”.
Meta description is long (313 characters)
Your meta description is 313 characters; Google truncates after about 160, so the end of your pitch is cut.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
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.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
319 internal links, 6 external
The homepage links to 319 pages on bohme.com and 6 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://bohme.com/.
Structured data in place
Structured data found: ImageObject, OfferCatalog, 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://bohme.com/sitemap.xml.
AI search readiness
4 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.
Text is in the HTML
Your server sends the page's text in the HTML (844 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bohme.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 107 found) and read each the way a search engine does.
7 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.
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
17 small tap targets
17 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 175 words
The homepage has only about 175 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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “fall edit, shop new arrivals”.
22 calls to action
The homepage has 22 calls to action, for example “Learn more”, “Shop All Sale” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 mores (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.
43 cookies set on arrival
43Opening the homepage sets 43 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.
67 other companies contacted
Loading the homepage contacts 67 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 bohme.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 23 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Nosto · Black Crow Ai That Delivers · Gorgias Live Chat Helpdesk · Sc Easy Redirects · Triplewhale · Convert Experiences · Attentive · Yotpo Product Reviews · Yotpo Loyalty Rewards · Elevar Conversion Tracking · Mntn · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Convert Web Pixel · Loop Returns · Back In Stock · Veeper Stop Coupon Leaks · nfcube.com · wickedreports.com · cloudfront.net · corso.com · attn.tv
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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Hiring
- Hiring
- 33 open roles
- Teams
- Stores (30), Corporate (2), Warehouse (1)
- Job board
- rippling
- Careers page
- bohme.com/pages/careers (opens in a new tab)
Company
- Employees
- 260
- Headquarters
- Sandy
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on bohme.com, including 18 speed issues, 5 SEO issues and 2 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.