Website review, no card needed
zenbooth.net website review
Visit site (opens in a new tab)Reviewed 6 November 202645 issues · 91 checks
This review found 45 issues worth fixing on zenbooth.net, 16 of them high impact, across 91 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
78C- #56,859 of 111,813 reviewed websitesbeats 44%
- #37,562 of 64,007 online storesbeats 36%
- #35,946 of 58,481 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 137 ms |
| May 23, 2026 | 132 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 165 ms |
| Jun 13, 2026 | 166 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 187 ms |
| Jul 11, 2026 | 182 ms |
| Jul 18, 2026 | 166 ms |
| Jul 25, 2026 | 183 ms |
| Aug 1, 2026 | 208 ms |
| Aug 8, 2026 | 234 ms |
| Aug 15, 2026 | 268 ms |
| Aug 22, 2026 | 271 ms |
| Aug 29, 2026 | 268 ms |
| Sep 5, 2026 | 263 ms |
| Sep 12, 2026 | 232 ms |
| Sep 19, 2026 | 222 ms |
| Sep 26, 2026 | 254 ms |
| Oct 3, 2026 | 404 ms |
| Oct 10, 2026 | 350 ms |
| Oct 17, 2026 | 334 ms |
| Oct 24, 2026 | 281 ms |
| Oct 31, 2026 | 184 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
2.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 5.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
3.8 MB12 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Hotjar, Shopify and Google Tag Manager and others), adding 2.8 MB and 3.1 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 1.1 MB39 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Hotjar adds 699 ms
699 msHotjar costs a phone 699 ms of main-thread work and 264 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 643 ms
643 msGoogle Tag Manager costs a phone 643 ms of main-thread work and 764 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 664 ms
664 msShopify costs a phone 664 ms of main-thread work and 206 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.
hsappstatic.net adds 501 ms
501 mshsappstatic.net costs a phone 501 ms of main-thread work and 715 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 366 ms. During a long task the page ignores taps.
monkcommerce.app adds 176 ms
176 msmonkcommerce.app costs a phone 176 ms of main-thread work and 535 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 · 54 KiBAbout 54 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
82 KiBPolyfills for old browsers add 82 KiB JavaScript that modern phones do not need.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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: 21.6 s
21.6 sYour largest element takes 21.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: 52.7 s
52.7 sThe page becomes fully interactive after 52.7 s. Good is under 3.8 s.
Speed Index: 14.7 s
14.7 sVisually, the page fills in at 14.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 73% slower for real visitors
+73%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 137 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
69 images without width and height
69 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user TTFB: 724 ms
724 msReal visitors wait 724 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.093
0.093The layout barely moves while loading (CLS 0.093, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 11.2 MB in 354 requests
11.2 MBYour homepage downloads 11.2 MB in 354 requests on a phone: images 5.8 MB (43), scripts 3.9 MB (141) and other files 1,016 KiB (133). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 9.0 MB together. On a phone connection a single image that size takes seconds.
17 images far larger than shown
4.1 MB17 images are downloaded at several times the size a phone draws them, for example reforestation.jpg at 2,000 px wide, shown at 298 px. Resized copies would save about 4.1 MB.
8 images below the first screen load straight away
8 images further down the page (9.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (8.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 3.2 g of CO₂ per visit
3.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.18 g of CO₂e: 381.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
21 images without alt text
21 images have no alt text, which hurts accessibility and image search.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 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 long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Zenbooth | Office Phone Booths & Office Pods | Soundproof Meeting Pods”.
Meta description is long (288 characters)
Your meta description is 288 characters; Google truncates after about 160, so the end of your pitch is cut.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
65 internal links, 13 external
The homepage links to 65 pages on zenbooth.net and 13 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://zenbooth.net/.
Structured data in place
Structured data found: 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://zenbooth.net/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (848 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://zenbooth.net/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://zenbooth.net/products/growmeo declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://zenbooth.net/products/growmeo all use the title “Zenbooth | Office Phone Booths & Office Pods | Soundproof Meeting Pods”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://zenbooth.net/pages/request-a-quote, https://zenbooth.net/pages/who-we-serve, https://zenbooth.net/pages/sustainability, https://zenbooth.net/pages/contact-us, https://zenbooth.net/pages/zenbooth-showrooms and https://zenbooth.net/pages/dealers and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://zenbooth.net/pages/models, https://zenbooth.net/pages/who-we-serve, https://zenbooth.net/pages/office-phone-booth-comparison-guide, https://zenbooth.net/pages/sustainability, https://zenbooth.net/pages/zenbooth-showrooms and https://zenbooth.net/pages/dealers and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://zenbooth.net/pages/models, https://zenbooth.net/pages/request-a-quote, https://zenbooth.net/products/zenbooth-solo and https://zenbooth.net/products/zenbooth-duo took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26033724&Ver=2&mid=afd0373f-0eb0-481d-867b-00285eff0412&bo=1&sid=8780c9d0d9c611f1bc633dc60f143fa7&vid=8780e670d9c611f1afac530fd64791f2&vids=1&msclkid=N&pi=918639831&lg.
6 small tap targets
6 of 19 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 (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Failed to construct 'URL': Invalid URL”.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 748 words of copy
The homepage carries about 748 words of visible text.
7 checks passed
22 calls to action
The homepage has 22 calls to action, for example “Shop all”, “Request a Quote” and “Contact”.
3 short forms
3 short forms (0 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 90 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
50 other companies contacted
Loading the homepage contacts 50 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 zenbooth.net, 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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gtmanager · Go Product Page Gallery Zoom · Twilio Segment By Littledata · Uppromote Affiliate · Searchpie Seo Speed · Littledata The Data Layer · Vo Product Options · Xo Insert Code · Klaviyo Email Marketing Sms · Doc 404 Broken Links Repair · Google Tag Manager By Niddocks · Monk Free Gift With Purchase · Affliate By Secomapp · Announcement Bar Maker By Apphero · Back In Stock · herokuapp.com · getgoogletagmanager.com · commoninja.com · onetreeplanted.app · hubapi.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
- Analytics
- Segment
- Hosting
- Shopify
Company
- Headquarters
- Berkeley
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on zenbooth.net, including 22 speed issues, 4 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.