Website review, no card needed

alen.com logo

alen.com website review

Visit site (opens in a new tab)Reviewed 19 October 202637 issues · 88 checks

This review found 37 issues worth fixing on alen.com, 17 of them high impact, across 88 checks. The most urgent: google Tag Manager adds 4.1 s. 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
2.8 s1.7 sApr 25Oct 101.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.6 s
May 2, 20262.6 s
May 9, 20262.5 s
May 16, 20262.3 s
May 23, 20262.2 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
228 ms174 msApr 25Oct 10200 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026212 ms
May 2, 2026217 ms
May 9, 2026211 ms
May 16, 2026196 ms
May 23, 2026187 ms
May 30, 2026182 ms
Jun 6, 2026180 ms
Jun 13, 2026180 ms
Jun 20, 2026186 ms
Jun 27, 2026188 ms
Jul 4, 2026192 ms
Jul 11, 2026194 ms
Jul 18, 2026191 ms
Jul 25, 2026192 ms
Aug 1, 2026191 ms
Aug 8, 2026196 ms
Aug 15, 2026198 ms
Aug 22, 2026209 ms
Aug 29, 2026216 ms
Sep 5, 2026216 ms
Sep 12, 2026222 ms
Sep 19, 2026216 ms
Sep 26, 2026204 ms
Oct 3, 2026201 ms
Oct 10, 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 alen.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alen.com at 1.2 s1.2 s
  2. alen.com at 2.5 s2.5 s
  3. alen.com at 3.7 s3.7 s
  4. alen.com at 4.9 s4.9 s
  5. alen.com at 6.2 s6.2 s
  6. alen.com at 7.4 s7.4 s
  7. alen.com at 8.6 s8.6 s
  8. alen.com at 9.9 s9.9 s

Speed

12 to fix30
  • Google Tag Manager adds 4.1 s

    4.1 s

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

  • Main-thread work: 25.3 s

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

  • Use efficient cache lifetimes

    1.3 s · 567 KiB

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

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 7,711 HTML elements

    The page has 7,711 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 (Google Tag Manager, Facebook and rebuyengine.com and others), adding 2.5 MB and 5.5 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Improve image delivery

    1.1 MB

    20 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    500 ms

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

  • rebuyengine.com adds 268 ms

    268 ms

    rebuyengine.com costs a phone 268 ms of main-thread work and 853 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.

  • Facebook adds 297 ms

    297 ms

    Facebook costs a phone 297 ms of main-thread work and 279 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    200 ms · 100 KiB

    Polyfills for old browsers add 100 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • Minify CSS

    150 ms · 2 KiB

    2 KiB could be saved by minifying CSS.

  • Minify JavaScript

    120 KiB

    120 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    28 KiB

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

  • 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: 16 ms

    16 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 20.2 s

    20.2 s

    Your largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AIR PURIFIERS FOR WILDFIRE SMOKE LEARN MORE”.

  • Time to Interactive: 44.5 s

    44.5 s

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

  • Speed Index: 12.8 s

    12.8 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

    The first text or image appears after 5.1 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • 18 images without width and height

    18 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 212 ms to 200 ms 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.9 s

    1.9 s

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

  • Real-user INP: 195 ms

    195 ms

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

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

    1.3 s

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

  • Real-user TTFB: 520 ms

    520 ms

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

  • Largest content (LCP) got 27% faster for real visitors

    -27%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

3 to fix43
  • Page weight: 7.9 MB in 762 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 762 requests on a phone: scripts 3.2 MB (142), images 2.3 MB (93) and other files 1.7 MB (461). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    559 KiB

    5 images are downloaded at several times the size a phone draws them, for example pollen.png at 900 px wide, shown at 68 px. Resized copies would save about 559 KiB.

  • 12 images below the first screen load straight away

    12 images further down the page (809 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (41 KiB) is 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.

  • About 2.2 g of CO₂ per visit

    2.24 g

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

Accessibility

5 to fixGoogle 8791
  • 9 text elements with low contrast

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

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 3 images without alt text

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

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3, h2 → h4 and h2 → h4), 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 8598
  • 36 links with vague text

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

  • 261 internal links, 23 external

    The homepage links to 261 pages on alen.com and 23 external pages.

8 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Alen air purifiers for homes and commercial businesses remove dust, mold and odors with True HEPA air filters. Rated #1…”.

  • One H1 headline

    Your main headline reads: “AIR PURIFIERS FOR WILDFIRE SMOKE”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “True HEPA Air Purifiers For Homes & Businesses | Alen®”.

  • Canonical URL set

    The canonical URL is https://alen.com/.

  • Structured data in place

    Structured data found: Organization and 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://alen.com/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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://alen.com/collections/alen-breathesmart-75i-filters and https://alen.com/collections/alen-breathesmart-35i-replacement-hepa-filters have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://alen.com/pages/digital-assistant 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 66 found) and read each the way a search engine does.

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

  • 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

6 to fixGoogle 5068
  • 10 broken images

    10 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/Product/499045999/415404001/square.jpg?1791818561.

  • 11 small tap targets

    11 of 33 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 (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

  • 21 distorted images

    21 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • 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 1,292 words of copy

    The homepage carries about 1,292 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: “LEARN MORE”.

  • 26 calls to action

    The homepage has 26 calls to action, for example “Back Shop”, “Back Get Started” and “Back Shop By Moods”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 109 testimonial or review blocks, 3 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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
  • 14 trackers load before any consent

    14

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

  • 42 cookies set on arrival

    42

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

  • 73 other companies contacted

    Loading the homepage contacts 73 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 alen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

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 37 issues on alen.com, including 18 speed issues, 1 SEO issue 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