Website review, no card needed
appliedmembranes.com website review
Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 87 checks
This review found 40 issues worth fixing on appliedmembranes.com, 14 of them high impact, across 87 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
81B- #40,435 of 120,337 reviewed websitesbeats 61%
- #26,939 of 68,137 online storesbeats 54%
- #25,974 of 62,092 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 151 ms |
| May 9, 2026 | 129 ms |
| May 16, 2026 | 117 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 114 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 132 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 108 ms |
| Aug 8, 2026 | 108 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 105 ms |
| Aug 29, 2026 | 105 ms |
| Sep 5, 2026 | 110 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 126 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
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.3 s
2.7 s
3.1 s
Speed
Reduce unused JavaScript
1.8 s · 463 KiBAbout 463 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.3 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 55). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Klaviyo and bc0a.com and others), adding 1.4 MB and 725 ms of main-thread time.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 728 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 86 KiBAbout 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
450 ms · 64 KiB1 image could be 64 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 352 ms
352 msGoogle Tag Manager costs a phone 352 ms of main-thread work and 502 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.
Use efficient cache lifetimes
300 ms · 38 KiB6 files are served with short cache lifetimes, so returning visitors download them again (38 KiB).
2,146 HTML elements
The page has 2,146 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 127 ms
127 msKlaviyo costs a phone 127 ms of main-thread work and 323 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 53 ms
53 msShopify costs a phone 53 ms of main-thread work and 316 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.
Legacy JavaScript
150 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.9 s
15.9 sYour largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
Speed Index: 8.8 s
8.8 sVisually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 537 ms
537 msScripts block taps and scrolling for 537 ms in total while the page loads. Good is under 200 ms.
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) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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 LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 126 ms
126 msReal visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 637 ms
637 msReal visitors wait 637 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 151 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
4 images far larger than shown
602 KiB4 images are downloaded at several times the size a phone draws them, for example systems_area_panorama_with_container_AMI_logo_1_2000x1101.pn at 2,000 px wide, shown at 390 px. Resized copies would save about 602 KiB.
Page weight: 3.6 MB in 268 requests
3.6 MBYour homepage downloads 3.6 MB in 268 requests on a phone: scripts 1.6 MB (137), images 1.0 MB (9) and other files 753 KiB (104). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Invalid ARIA attributes
5 elements use ARIA attributes their role does not allow, which confuses screen readers.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (93 characters)
Your title is 93 characters, so Google will cut it off around 60: “Applied Membranes Inc. | Reverse Osmosis & Water Filtration Systems — Applied Membranes, …”.
Meta description is long (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
252 internal links, 27 external
The homepage links to 252 pages on appliedmembranes.com and 27 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.appliedmembranes.com/.
Structured data in place
Structured data found: 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://www.appliedmembranes.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 (1,579 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.appliedmembranes.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.appliedmembranes.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.appliedmembranes.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.appliedmembranes.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.appliedmembranes.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 113 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Best practices
6 small tap targets
6 of 28 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: the server responded with a status of 403 ()”.
1 checks passed
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 1,037 words of copy
The homepage carries about 1,037 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
11 calls to action
The homepage has 11 calls to action, for example “How to Place an Order”, “Contact Us” and “How to Order”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 84 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 appliedmembranes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on appliedmembranes.com, including 19 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.