Website review, no card needed

efilters.ca logo

efilters.ca website review

Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 72 checks

This review found 26 issues worth fixing on efilters.ca, 5 of them high impact, across 72 checks. The most urgent: page weight: 24.9 MB in 241 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

Full-page screenshot of efilters.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. efilters.ca at 0.5 s0.5 s
  2. efilters.ca at 0.9 s0.9 s
  3. efilters.ca at 1.4 s1.4 s
  4. efilters.ca at 1.9 s1.9 s
  5. efilters.ca at 2.3 s2.3 s
  6. efilters.ca at 2.8 s2.8 s
  7. efilters.ca at 3.3 s3.3 s
  8. efilters.ca at 3.7 s3.7 s

Speed

5 to fix68
  • Use efficient cache lifetimes

    900 ms · 178 KiB

    19 files are served with short cache lifetimes, so returning visitors download them again (178 KiB).

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 150 KiB

    About 150 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Render-blocking requests

    350 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • 1,597 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Mailchimp, Shopify and Help Scout and others), adding 472 KiB and 220 ms of main-thread time.

  • Improve image delivery

    167 KiB

    4 images could be 167 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

    A phone's processor spends 1.6 s on main-thread work while loading, 479 ms of it running JavaScript. That is comfortably low.

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 10.4 s

    10.4 s

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

  • Time to Interactive: 10.5 s

    10.5 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 39 ms

    39 ms

    Scripts block the page for only 39 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 24.9 MB in 241 requests

    24.9 MB

    Your homepage downloads 24.9 MB in 241 requests on a phone: media 22.9 MB (8), other files 741 KiB (88) and scripts 662 KiB (85). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 7.1 g of CO₂ per visit

    7.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 7.07 g of CO₂e: 848.5 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 are sized for phones

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

Accessibility

6 to fixGoogle 9393
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9284
  • Meta description is long (161 characters)

    Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.efilters.ca")”.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 161 internal links, 3 external

    The homepage links to 161 pages on efilters.ca and 3 external pages.

5 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “Everpure Water Filters For Your Home & Business – Efilters.ca”.

  • Canonical URL set

    The canonical URL is https://www.efilters.ca/.

  • 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.efilters.ca/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,060 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

7 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 a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 7785
  • 12 small tap targets

    12 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 549 words of copy

    The homepage carries about 549 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “LEARN MORE”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop”, “Add a note to your order” and “LEARN MORE”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 11 cookies set on arrival

    11

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 efilters.ca, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pagefly Ai Page Builder · Essential Announcer · Seo Manager Venntov · Minmaxify Order Limits · Essential Announcement Bar · Mailchimp · azureedge.net · stamped.io · kxcdn.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on efilters.ca, including 9 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

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