Website review, no card needed

aerosolms.com logo

aerosolms.com website review

Visit site (opens in a new tab)Reviewed 10 November 202646 issues · 89 checks

This review found 46 issues worth fixing on aerosolms.com, 16 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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.1 s1.8 sMay 23Nov 71.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.8 s
Nov 7, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
113 ms100 msMay 23Nov 7102 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026107 ms
May 30, 2026106 ms
Jun 6, 2026111 ms
Jun 13, 2026110 ms
Jun 20, 2026109 ms
Jun 27, 2026110 ms
Jul 4, 2026106 ms
Jul 11, 2026106 ms
Jul 18, 2026105 ms
Jul 25, 2026109 ms
Aug 1, 2026110 ms
Aug 8, 2026108 ms
Aug 15, 2026106 ms
Aug 22, 2026103 ms
Aug 29, 2026102 ms
Sep 5, 2026101 ms
Sep 12, 2026104 ms
Sep 19, 2026106 ms
Sep 26, 2026108 ms
Oct 3, 2026106 ms
Oct 10, 2026108 ms
Oct 17, 2026106 ms
Oct 24, 2026104 ms
Oct 31, 2026104 ms
Nov 7, 2026102 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 aerosolms.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aerosolms.com at 0.4 s0.4 s
  2. aerosolms.com at 0.8 s0.8 s
  3. aerosolms.com at 1.2 s1.2 s
  4. aerosolms.com at 1.6 s1.6 s
  5. aerosolms.com at 2.0 s2.0 s
  6. aerosolms.com at 2.4 s2.4 s
  7. aerosolms.com at 2.8 s2.8 s
  8. aerosolms.com at 3.2 s3.2 s

Speed

12 to fix57
  • Reduce unused JavaScript

    3.9 s · 821 KiB

    About 821 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Use efficient cache lifetimes

    1.0 s · 220 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (POWr, Google Tag Manager and Clarity and others), adding 2.6 MB and 1.3 s of main-thread time.

  • Mobile performance score: 57

    57/100

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

  • Reduce unused CSS

    450 ms · 121 KiB

    About 121 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.

  • Google Tag Manager adds 373 ms

    373 ms

    Google Tag Manager costs a phone 373 ms of main-thread work and 848 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.

  • POWr adds 427 ms

    427 ms

    POWr costs a phone 427 ms of main-thread work and 13 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.

  • Main-thread work: 3.9 s

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

  • Improve image delivery

    352 KiB

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

  • 1,917 HTML elements

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

  • Shopify adds 64 ms

    64 ms

    Shopify costs a phone 64 ms of main-thread work and 1.2 MB 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

    250 ms · 41 KiB

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

  • 10 long tasks on the main thread

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

  • Minify CSS

    20 KiB

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

8 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: 21.3 s

    21.3 s

    Your largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BN-01-MOBILE-ADI”.

  • Time to Interactive: 22.4 s

    22.4 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Total Blocking Time: 270 ms

    270 ms

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user INP: 133 ms

    133 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 749 ms

    749 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 5.0 MB in 400 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 400 requests on a phone: scripts 2.2 MB (112), images 1.2 MB (36) and other files 1.1 MB (225). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    BN-02-MOBILE-ADI.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    56 KiB

    2 images are downloaded at several times the size a phone draws them, for example Banner_RSMD_01_RPV.jpg at 600 px wide, shown at 149 px. Resized copies would save about 56 KiB.

  • About 1.4 g of CO₂ per visit

    1.42 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 8188
  • 33 tap targets too small

    33 tap targets are too small or too close together to hit reliably with a finger.

  • 3 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 form fields without a label

    8 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 5 links without text

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

  • Headings should not be empty (11 elements)

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 8377
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Aerosol Medical Systems | Expertos en Terapia Respiratoria | México”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 165 internal links, 10 external

    The homepage links to 165 pages on aerosolms.com and 10 external pages.

5 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Aerosol Medical Systems es el proveedor líder de equipo médico para tratar enfermedades respiratorias y trastornos del …”.

  • Canonical URL set

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

AI search readiness

1 to fix88
  • 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 (733 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix88
  • 12 pages share a meta description

    https://aerosolms.com/collections/terapia-respiratoria/C%C3%A1maras-Espaciadoras, https://aerosolms.com/collections/terapia-respiratoria/Fluj%C3%B3metros, https://aerosolms.com/collections/terapia-respiratoria/Ejercitadores-Respiratorios, https://aerosolms.com/collections/terapia-respiratoria/Nebulizadores-y-Compresores, https://aerosolms.com/collections/terapia-respiratoria/Micronebulizadores and https://aerosolms.com/collections/terapia-respiratoria/Accesorios and 1 other use the same meta description. A description written for each page earns more clicks.

  • 12 links to non-canonical URLs

    Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://aerosolms.com/collections/terapia-respiratoria/C%C3%A1maras-Espaciadoras, whose canonical is https://aerosolms.com/collections/terapia-respiratoria/c%c3%a1maras-espaciadoras. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://aerosolms.com/collections/all, https://aerosolms.com/collections/terapia-respiratoria, https://aerosolms.com/collections/terapia-respiratoria/C%C3%A1maras-Espaciadoras, https://aerosolms.com/collections/terapia-respiratoria/Fluj%C3%B3metros, https://aerosolms.com/collections/terapia-respiratoria/Ejercitadores-Respiratorios and https://aerosolms.com/collections/terapia-respiratoria/Nebulizadores-y-Compresores and 9 others have 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 100 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.

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

  • 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
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343118727&tm=shpfy_ui&Ver=2&mid=def43ba1-16f1-4fcd-b004-db638653b586&bo=1&sid=80430090dccf11f1815f15ed065c36f8&vid=80433680dccf11f196be8127c9deff75&vids=1&msclkid=N&pi.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Error: <symbol> attribute viewBox: Unexpected end of attribute. Expected number, "".”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

    The homepage carries about 477 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Quick Shop”.

  • 8 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity, Hotjar and LinkedIn Insight.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies, 3 of them by other companies (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.

  • 56 other companies contacted

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

Apps your storefront loads

Loyalty Rewards And Referrals · Ecomposer Builder · Avada Faqs · Smart Menu · automizely.com · chimpstatic.com · powr.io · conversionbear.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on aerosolms.com, including 20 speed issues, 4 SEO issues and 3 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