Website review, no card needed
zhumell.com website review
Visit site (opens in a new tab)Reviewed 12 November 202630 issues · 71 checks
This review found 30 issues worth fixing on zhumell.com, 7 of them high impact, across 71 checks. The most urgent: 5 text elements with low contrast. 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
83B- #23,896 of 103,223 reviewed websitesbeats 72%
- #15,522 of 57,514 online storesbeats 67%
- #15,049 of 52,341 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.2 s |
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
Mobile performance score: 77
77/100Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Reduce unused JavaScript
150 ms · 22 KiBAbout 22 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
83 KiB2 images could be 83 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
4 third-party services on the page
4 third-party services load with your homepage (Shopify, FontAwesome CDN and Google Fonts and others), adding 191 KiB and 17 ms of main-thread time.
Reduce unused CSS
16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page.
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.
Use efficient cache lifetimes
1 KiB1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 223 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
Largest Contentful Paint: 4.8 s
4.8 sYour largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (2.0 s).
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 4.8 s
4.8 sThe page becomes fully interactive after 4.8 s. Good is under 3.8 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (81 KiB) is 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 0.4 g of CO₂ per visit
0.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.37 g of CO₂e: 44.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.3 MB in 128 requests
1.3 MBYour homepage downloads 1.3 MB in 128 requests on a phone: other files 673 KiB (76), images 236 KiB (6) and scripts 229 KiB (32). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Alternative text of images should not be repeated as text (9 elements)
Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (7 characters)
Your title is only 7 characters: “Zhumell”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
38 internal links, 3 external
The homepage links to 38 pages on zhumell.com and 3 external pages.
4 checks passed
One H1 headline
Your main headline reads: “<img src="//zhumell.com/cdn/shop/files/zhumell_logo_reverse_358x.png?v=1614295381" srcset="//zhumell.com/cdn/shop/files…”.
Canonical URL set
The canonical URL is https://zhumell.com/.
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://zhumell.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
llms.txt published
The site publishes https://zhumell.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://zhumell.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://zhumell.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://zhumell.com/community/contact and https://zhumell.com/pages/contact-us all use the title “Contact Us – Zhumell”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://zhumell.com/customer_authentication/redirect, https://zhumell.com/collections/all, https://zhumell.com/community/contact, https://zhumell.com/pages/contact-us, https://zhumell.com/collections and https://zhumell.com/collections/dobsonian-telescopes and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://zhumell.com/community/contact, whose canonical is https://zhumell.com/pages/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://zhumell.com/customer_authentication/redirect and https://zhumell.com/collections have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://zhumell.com/community/contact, https://zhumell.com/pages/contact-us, https://zhumell.com/collections, https://zhumell.com/collections/dobsonian-telescopes, https://zhumell.com/collections/astronomy-binoculars and https://zhumell.com/collections/telescope-accessories and 1 other 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://zhumell.com/cdn/shop/t/2/assets/fontawesome.min.css?v=65' because its MIME type ('…”.
2 checks passed
Tap targets are thumb-sized
20 of 22 tappable elements near the top are at least 24 px.
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 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.
Only about 140 words
The homepage has only about 140 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
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “Contact Support”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
7 other companies contacted
Loading the homepage contacts 7 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 zhumell.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- jQuery
- 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 30 issues on zhumell.com, including 7 speed issues, 5 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.