Website review, no card needed
getsteripod.com website review
Visit site (opens in a new tab)Reviewed 12 November 202631 issues · 76 checks
This review found 31 issues worth fixing on getsteripod.com, 10 of them high impact, across 76 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
Site score
75C- #71,879 of 108,773 reviewed websitesbeats 30%
- #45,779 of 61,720 online storesbeats 22%
- #43,301 of 56,321 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.7 s · 412 KiBAbout 412 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Improve image delivery
1.0 s · 292 KiB9 images could be 292 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and Bazaarvoice and others), adding 8.8 MB and 615 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Shopify adds 24 ms
24 msShopify costs a phone 24 ms of main-thread work and 8.1 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.
Use efficient cache lifetimes
300 ms · 134 KiB11 files are served with short cache lifetimes, so returning visitors download them again (134 KiB).
Google Tag Manager adds 378 ms
378 msGoogle Tag Manager costs a phone 378 ms of main-thread work and 452 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
300 ms · 78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 217 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 5 KiB5 KiB could be saved by minifying CSS.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.9 s
12.9 sYour largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalize content and ads, provide soci…”.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Time to Interactive: 12.9 s
12.9 sThe page becomes fully interactive after 12.9 s. Good is under 3.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 241 ms
241 msScripts block taps and scrolling for 241 ms in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.044
0.044The layout barely moves while loading (CLS 0.044, good is under 0.1).
Images and page weight
Page weight: 15.7 MB in 168 requests
15.7 MBYour homepage downloads 15.7 MB in 168 requests on a phone: media 13.3 MB (1), scripts 1,004 KiB (36) and other files 775 KiB (91). Under 2 MB keeps phones on slow connections fast.
About 4.4 g of CO₂ per visit
4.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.44 g of CO₂e: 533.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
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.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
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 18 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 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 meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (8 characters)
Your title is only 8 characters: “Steripod”. 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.
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.
41 internal links, 11 external
The homepage links to 41 pages on getsteripod.com and 11 external pages.
5 checks passed
One H1 headline
Your main headline reads: “<img class="" src="//getsteripod.com/cdn/shop/files/Steripod_PMS_GreenC_no_background_1000x1000.png?v=1667352683" alt="…”.
Canonical URL set
The canonical URL is https://getsteripod.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://getsteripod.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.
Opted out of AI training for 1 crawler
robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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://getsteripod.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://getsteripod.com/pages/privacy, https://getsteripod.com/pages/terms-of-use, https://getsteripod.com/collections/all, https://getsteripod.com/pages/about-us, https://getsteripod.com/pages/faq and https://getsteripod.com/pages/cookies and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://getsteripod.com/collections/frontpage/products/steripod-clip-on-toothbrush-protector, whose canonical is https://getsteripod.com/products/steripod-clip-on-toothbrush-protector. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://getsteripod.com/collections/all, https://getsteripod.com/pages/about-us and https://getsteripod.com/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://getsteripod.com/pages/privacy, https://getsteripod.com/pages/terms-of-use, https://getsteripod.com/pages/cookies and https://getsteripod.com/pages/cookie-list 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.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
11 pages of 12 loaded without an error (the rest turned automated requests away).
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
16 small tap targets
16 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
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 112 words
The homepage has only about 112 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: “Shop All” and “Learn More”.
4 calls to action
The homepage has 4 calls to action, for example “Shop All”, “Learn more” and “Contact Us”.
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 getsteripod.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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on getsteripod.com, including 13 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.