Website review, no card needed
officialhydromaxpump.com website review
Visit site (opens in a new tab)Reviewed 7 November 202643 issues · 88 checks
This review found 43 issues worth fixing on officialhydromaxpump.com, 15 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
One score from every part of this review. How it works
How it loaded on a phone
1.6 s
3.3 s
4.9 s
6.5 s
8.1 s
9.8 s
11.4 s
13.0 s
Speed
Reduce unused JavaScript
9.3 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.3 s faster on a phone.
Avoid multiple page redirects
4.2 sThe page goes through 2 redirects before it starts loading, costing about 4.2 s. Link and advertise the final URL directly.
Use efficient cache lifetimes
2.6 s · 695 KiB36 files are served with short cache lifetimes, so returning visitors download them again (695 KiB).
Main-thread work: 24.8 s
A phone's processor spends 24.8 s on main-thread work while loading, 9.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.6 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
alia-prod.com adds 1.0 s
1.0 salia-prod.com costs a phone 1.0 s of main-thread work and 269 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (alia-prod.com, Hotjar and Google Tag Manager and others), adding 4.4 MB and 5.2 s of main-thread time.
Hotjar adds 948 ms
948 msHotjar costs a phone 948 ms of main-thread work and 260 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 884 ms
884 msGoogle Tag Manager costs a phone 884 ms of main-thread work and 688 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.
bathmatedirect.com adds 673 ms
673 msbathmatedirect.com costs a phone 673 ms of main-thread work and 2.0 MB 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.
Legacy JavaScript
500 ms · 114 KiBPolyfills for old browsers add 114 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
trustedsite.com adds 590 ms
590 mstrustedsite.com costs a phone 590 ms of main-thread work and 6 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
380 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 380 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 351 ms. During a long task the page ignores taps.
2,087 HTML elements
The page has 2,087 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
270 ms · 54 KiB54 KiB could be saved by minifying JavaScript.
Document request latency
200 msThe HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Minify CSS
130 ms · 9 KiB9 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
14 KiB2 images could be 14 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 19 ms
19 msYour server sent the HTML in 19 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: 40.7 s
40.7 sYour largest element takes 40.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GET UP TO 40% OFF BATHMATE PUMPS”.
Speed Index: 21.6 s
21.6 sVisually, the page fills in at 21.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.9 s
40.9 sThe page becomes fully interactive after 40.9 s. Good is under 3.8 s.
Total Blocking Time: 3.0 s
3.0 sScripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.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.
4 checks passed
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 596 ms
596 msReal visitors wait 596 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Images and page weight
Page weight: 6.9 MB in 627 requests
6.9 MBYour homepage downloads 6.9 MB in 627 requests on a phone: scripts 3.9 MB (200), other files 1.6 MB (335) and images 535 KiB (43). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
1.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.96 g of CO₂e: 235.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “The Official Home of Hydromax – Best Hydro Penis Pumps – Official Hydromax Pump”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“.site-header__logo-image { height: 40px; }” and “WELCOME TO THE OFFICIAL HYDROMAX STORE”). One clear main headline is easier for people and search engines.
Meta description is long (202 characters)
Your meta description is 202 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
75 internal links, 43 external
The homepage links to 75 pages on officialhydromaxpump.com and 43 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://officialhydromaxpump.com/.
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://officialhydromaxpump.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.
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 (2,898 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://officialhydromaxpump.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages share 2 titles
https://officialhydromaxpump.com/collections/hydromax-series, https://officialhydromaxpump.com/collections/hydroxtreme-series, https://officialhydromaxpump.com/collections/up-to-five, https://officialhydromaxpump.com/collections/five-to-seven, https://officialhydromaxpump.com/collections/seven-to-nine and https://officialhydromaxpump.com/collections/more-than-nine all use the title “Penis Pumps | Hydro & Water Penis Pumps | Bathmate”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://officialhydromaxpump.com/pages/hydromax-reviews has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://officialhydromaxpump.com/collections/hydromax-series, https://officialhydromaxpump.com/collections/hydroxtreme-series, https://officialhydromaxpump.com/collections/up-to-five, https://officialhydromaxpump.com/collections/five-to-seven, https://officialhydromaxpump.com/collections/seven-to-nine and https://officialhydromaxpump.com/collections/more-than-nine use the same meta description. A description written for each page earns more clicks.
9 pages slow to respond
https://officialhydromaxpump.com/collections/hydromax-pumps, https://officialhydromaxpump.com/collections/hydro-series, https://officialhydromaxpump.com/collections/hydromax-series, https://officialhydromaxpump.com/collections/hydroxtreme-series, https://officialhydromaxpump.com/collections/up-to-five and https://officialhydromaxpump.com/collections/five-to-seven and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
4 small tap targets
4 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 830 words of copy
The homepage carries about 830 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Sign up and save up to 40%”.
7 calls to action
The homepage has 7 calls to action, for example “Shop By Size”, “Up To 5 Inches Shop Up To 5 Inches” and “5 to 7 Inches Shop 5 to 7 Inches”.
3 short forms
3 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Analytics.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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.
52 cookies set on arrival
52Opening the homepage sets 52 cookies, 17 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.
72 other companies contacted
Loading the homepage contacts 72 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 officialhydromaxpump.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Optimonk Popup Cro A B Test · Judge Me Reviews · Zipify Oneclickupsell · amazonaws.com · conversionbear.com · popt.in · gorgias.chat · 9gtb.com · pushowl.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Company
- Headquarters
- Horbury
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on officialhydromaxpump.com, including 25 speed issues, 5 SEO issues and 1 conversion gap. 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.