Website review, no card needed
gopurepressure.com website review
Visit site (opens in a new tab)Reviewed 6 November 202629 issues · 77 checks
This review found 29 issues worth fixing on gopurepressure.com, 6 of them high impact, across 77 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
73C- #91,955 of 124,581 reviewed websitesbeats 23%
- #57,219 of 69,967 online storesbeats 15%
- #53,506 of 63,604 Shopify storesbeats 13%
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
3.8 s · 668 KiBAbout 668 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Render-blocking requests
1.8 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused CSS
900 ms · 137 KiBAbout 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 411 ms. During a long task the page ignores taps.
Google Tag Manager adds 229 ms
229 msGoogle Tag Manager costs a phone 229 ms of main-thread work and 317 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics and others), adding 441 KiB and 230 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 34 KiB3 files are served with short cache lifetimes, so returning visitors download them again (34 KiB).
Improve image delivery
150 ms · 31 KiB4 images could be 31 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
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: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 532 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.3 s
12.3 sYour largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.3 s
12.3 sThe page becomes fully interactive after 12.3 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 525 ms
525 msScripts block taps and scrolling for 525 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
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.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 57.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.7 MB in 27 requests
1.7 MBYour homepage downloads 1.7 MB in 27 requests on a phone: scripts 1.3 MB (7), fonts 170 KiB (4) and stylesheets 157 KiB (3). That is a lean page.
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
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Headings skip levels
Headings skip levels (h2 → h4, h1 → h4 and h1 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
47 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: 47 passed and 2 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: “Solventless Select | Precision Filtration Bags & Processing Consumable”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 H1 headlines
There are 4 <h1> headlines (“Keep Your Operation Running Without Interruptions…”, “Request a Product or Custom Supply” and “Need Equipment to Complete Your Setup?”). One clear main headline is easier for people and search engines.
Meta description is long (173 characters)
Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.
43 internal links, 3 external
The homepage links to 43 pages on gopurepressure.com and 3 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.solventlessselect.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://www.solventlessselect.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.
Parts of the site are closed to 1 AI crawler
Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.
No llms.txt
There is no https://www.solventlessselect.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (402 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.solventlessselect.com/shop/wishlist and https://www.solventlessselect.com/shop all use the title “Products | Solventless Select”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages without a meta description
https://www.solventlessselect.com/filtration-wash-bags, https://www.solventlessselect.com/downloads, https://www.solventlessselect.com/shop/wishlist, https://www.solventlessselect.com/shop, https://www.solventlessselect.com/shop/category/solventless-select-purepacks-1 and https://www.solventlessselect.com/shop/category/solventless-select-parchment-paper-2 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.solventlessselect.com/shop/wishlist, whose canonical is https://www.solventlessselect.com/shop. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.solventlessselect.com/consumable-subscriptions, https://www.solventlessselect.com/downloads, https://www.solventlessselect.com/shop/wishlist and https://www.solventlessselect.com/shop have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.solventlessselect.com/downloads has 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.
9 pages slow to respond
https://www.solventlessselect.com/consumables, https://www.solventlessselect.com/consumable-subscriptions, https://www.solventlessselect.com/aboutus, https://www.solventlessselect.com/downloads, https://www.solventlessselect.com/contactus and https://www.solventlessselect.com/shop/wishlist 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 19 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
11 small tap targets
11 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 290 words of copy
The homepage carries about 290 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: “Shop Consumables” and “Subscribe & Save”.
11 calls to action
The homepage has 11 calls to action, for example “Contact Us”, “Shop Consumables” and “Subscribe & Save”.
4 short forms
4 short forms (7 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Umami.
Phone number on the homepage
Your phone number is on the homepage.
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
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
5 cookies set on arrival
5Opening the homepage sets 5 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.
6 other companies contacted
Loading the homepage contacts 6 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 gopurepressure.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Odoo
- Framework
- Tailwind CSS
- E-commerce
- Shopify;Shopify Plus
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on gopurepressure.com, including 11 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.