Website review, no card needed

clearlyfiltered.com logo

clearlyfiltered.com website review

Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 87 checks

This review found 42 issues worth fixing on clearlyfiltered.com, 15 of them high impact, across 87 checks. The most urgent: page weight: 32.6 MB in 463 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s1.5 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20262.3 s
Jun 13, 20263.0 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.4 s
Jul 11, 20263.2 s
Jul 18, 20262.9 s
Jul 25, 20263.0 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20262.8 s
Oct 10, 20262.5 s
Oct 17, 20262.2 s
Oct 24, 20262.0 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
237 ms170 msMay 16Oct 31200 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026178 ms
May 23, 2026179 ms
May 30, 2026180 ms
Jun 6, 2026194 ms
Jun 13, 2026212 ms
Jun 20, 2026222 ms
Jun 27, 2026225 ms
Jul 4, 2026229 ms
Jul 11, 2026221 ms
Jul 18, 2026210 ms
Jul 25, 2026204 ms
Aug 1, 2026186 ms
Aug 8, 2026180 ms
Aug 15, 2026182 ms
Aug 22, 2026186 ms
Aug 29, 2026187 ms
Sep 5, 2026193 ms
Sep 12, 2026196 ms
Sep 19, 2026203 ms
Sep 26, 2026208 ms
Oct 3, 2026211 ms
Oct 10, 2026212 ms
Oct 17, 2026210 ms
Oct 24, 2026206 ms
Oct 31, 2026200 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

Full-page screenshot of clearlyfiltered.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. clearlyfiltered.com at 1.9 s1.9 s
  2. clearlyfiltered.com at 3.7 s3.7 s
  3. clearlyfiltered.com at 5.6 s5.6 s
  4. clearlyfiltered.com at 7.5 s7.5 s
  5. clearlyfiltered.com at 9.4 s9.4 s
  6. clearlyfiltered.com at 11.2 s11.2 s
  7. clearlyfiltered.com at 13.1 s13.1 s
  8. clearlyfiltered.com at 15.0 s15.0 s

Speed

16 to fix38
  • Main-thread work: 19.7 s

    A phone's processor spends 19.7 s on main-thread work while loading, 9.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Tag Manager adds 1.7 s

    1.7 s

    Google Tag Manager costs a phone 1.7 s of main-thread work and 706 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.

  • Render-blocking requests

    1.6 s

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Reduce unused CSS

    1.1 s · 186 KiB

    About 186 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38. 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 (Google Tag Manager, Shopify and route.com and others), adding 2.9 MB and 3.6 s of main-thread time.

  • Improve image delivery

    450 ms · 1.4 MB

    8 images could be 1.4 MB 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.

  • Use efficient cache lifetimes

    150 ms · 1.5 MB

    50 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

  • Reduce unused JavaScript

    1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 796 ms. During a long task the page ignores taps.

  • Shopify adds 511 ms

    511 ms

    Shopify costs a phone 511 ms of main-thread work and 998 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.

  • route.com adds 346 ms

    346 ms

    route.com costs a phone 346 ms of main-thread work and 542 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.

  • Minify CSS

    300 ms · 44 KiB

    44 KiB could be saved by minifying CSS.

  • UpSellit adds 290 ms

    290 ms

    UpSellit costs a phone 290 ms of main-thread work and 20 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.

  • 1,681 HTML elements

    The page has 1,681 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • shippedsuite.com adds 127 ms

    127 ms

    shippedsuite.com costs a phone 127 ms of main-thread work and 355 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

    65 KiB

    Polyfills for old browsers add 65 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.

1 checks passed
  • Server response: 18 ms

    18 ms

    Your server sent the HTML in 18 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix67
  • 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: 12.8 s

    12.8 s

    Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 39.6 s

    39.6 s

    The page becomes fully interactive after 39.6 s. Good is under 3.8 s.

  • Total Blocking Time: 2.4 s

    2.4 s

    Scripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 7.9 s

    7.9 s

    Visually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.

  • Real-user INP: 205 ms

    205 ms

    Real visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 178 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 789 ms

    789 ms

    Real visitors wait 789 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix38
  • Page weight: 32.6 MB in 463 requests

    32.6 MB

    Your homepage downloads 32.6 MB in 463 requests on a phone: media 24.9 MB (16), scripts 3.2 MB (241) and images 3.0 MB (44). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    whats-in-your-water.gif weighs 7.4 MB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (7.5 MB) are 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.

  • 4 images below the first screen load straight away

    4 images further down the page (7.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 9.2 g of CO₂ per visit

    9.24 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.24 g of CO₂e: 1108.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 9092
  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 18 links without text

    18 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8587
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Filtered Water Bottles and Pitchers - Get Cleaner Water Today – Clearly Filtered”.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("Liquid error (snippets/tracking-scripts line 54): inval…”.

  • 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.

  • 126 internal links, 10 external

    The homepage links to 126 pages on clearlyfiltered.com and 10 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Clearly Filtered products remove tap water contaminants like Fluoride, Lead, Mercury, Arsenic and Chromium-6 by up to 9…”.

  • One H1 headline

    Your main headline reads: “Clearly Filtered”.

  • Canonical URL set

    The canonical URL is https://clearlyfiltered.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://clearlyfiltered.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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,217 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://clearlyfiltered.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 4 pages without a meta description

    https://clearlyfiltered.com/collections/pitchers, https://clearlyfiltered.com/collections/accessories, https://clearlyfiltered.com/blogs/all and https://clearlyfiltered.com/pages/pitcher-performance-data have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.

6 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.

  • 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

2 to fixGoogle 9678
  • 3 broken images

    3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=295019071&tm=gtm002&Ver=2&mid=7f7c5e70-4011-44a7-a483-c40ff1f0e757&bo=1&sid=a1869f00d8a511f18283a141eaec57a4&vid=a186fd30d8a511f186ac995f90f71e41&vids=1&msclkid=N&pi=9.

  • 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://clearlyfiltered.com/cdn/shop/t/273/assets/pdp-video-slider.css?v=58587' because it…”.

2 checks passed
  • Tap targets are thumb-sized

    28 of 32 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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 554 words of copy

    The homepage carries about 554 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 All Products”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop All”, “Contact Us” and “Shop”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating and “350k+ Reviews”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • 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

1 to fix
  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 6 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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 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.

  • 63 other companies contacted

    Loading the homepage contacts 63 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 clearlyfiltered.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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Okendo · Triplewhale · Elevar Conversion Tracking · Gdpr Cookie Consent · rechargecdn.com · gorgias.chat · route.com · klaviyo.com · 9gtb.com · superfiliate-cdn.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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Rancho Santa Margarita

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on clearlyfiltered.com, including 22 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25