Website review, no card needed

aerox.com logo

aerox.com website review

Visit site (opens in a new tab)Reviewed 17 November 202651 issues · 100 checks

This review found 51 issues worth fixing on aerox.com, 21 of them high impact, across 100 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.4 s1.2 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.5 s
Jul 4, 20261.6 s
Jul 11, 20261.5 s
Jul 18, 20261.6 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
142 ms56 msMay 30Nov 1476 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026104 ms
Jun 6, 202679 ms
Jun 13, 202666 ms
Jun 20, 202679 ms
Jun 27, 2026108 ms
Jul 4, 2026113 ms
Jul 11, 2026108 ms
Jul 18, 202693 ms
Jul 25, 202687 ms
Aug 1, 202688 ms
Aug 8, 202695 ms
Aug 15, 2026106 ms
Aug 22, 2026104 ms
Aug 29, 2026132 ms
Sep 5, 2026131 ms
Sep 12, 2026105 ms
Sep 19, 2026103 ms
Sep 26, 202679 ms
Oct 3, 202678 ms
Oct 10, 202685 ms
Oct 17, 202685 ms
Oct 24, 202685 ms
Oct 31, 202681 ms
Nov 7, 202672 ms
Nov 14, 202676 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 aerox.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aerox.com at 0.5 s0.5 s
  2. aerox.com at 0.9 s0.9 s
  3. aerox.com at 1.4 s1.4 s
  4. aerox.com at 1.8 s1.8 s
  5. aerox.com at 2.3 s2.3 s
  6. aerox.com at 2.7 s2.7 s
  7. aerox.com at 3.2 s3.2 s
  8. aerox.com at 3.6 s3.6 s

Speed

12 to fix34
  • Reduce unused JavaScript

    11.0 s · 1.9 MB

    About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.0 s faster on a phone.

  • YouTube adds 1.5 s

    1.5 s

    YouTube costs a phone 1.5 s of main-thread work and 2.9 MB 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.

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 4.9 s

    A phone's processor spends 4.9 s on main-thread work while loading, 2.6 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 (YouTube, Google Tag Manager and Bigcommerce and others), adding 14.6 MB and 2.3 s of main-thread time.

  • Use efficient cache lifetimes

    2.9 MB

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

  • Bigcommerce adds 299 ms

    299 ms

    Bigcommerce costs a phone 299 ms of main-thread work and 11.0 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.

  • Improve image delivery

    600 ms · 645 KiB

    6 images could be 645 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 114 KiB

    About 114 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 308 ms

    308 ms

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

  • Render-blocking requests

    350 ms

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

  • 2,710 HTML elements

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

  • 18 long tasks on the main thread

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

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    12 KiB

    12 KiB JavaScript is shipped twice across bundles.

  • 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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 56 ms

    56 ms

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

Core Web Vitals

9 to fix100
  • 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.

  • First Contentful Paint: 14.5 s

    14.5 s

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

  • Largest Contentful Paint: 54.7 s

    54.7 s

    Your largest element takes 54.7 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: 59.9 s

    59.9 s

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

  • Speed Index: 14.5 s

    14.5 s

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

  • Total Blocking Time: 985 ms

    985 ms

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

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

    +39%

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

  • Real-user TTFB: 826 ms

    826 ms

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

  • 11 images without width and height

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

6 checks passed
  • 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: 77 ms

    77 ms

    Real visitors wait 77 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.6 s

    1.6 s

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

  • Tap response (INP) got 19% faster for real visitors

    -19%

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

5 to fix18
  • Page weight: 14.8 MB in 108 requests

    14.8 MB

    Your homepage downloads 14.8 MB in 108 requests on a phone: images 10.6 MB (36), scripts 3.5 MB (34) and HTML 281 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    8.0 MB

    5 images are downloaded at several times the size a phone draws them, for example e6dd0a80-ba74-4965-bc96-a75e822da326.jpg at 11,375 px wide, shown at 259 px. Resized copies would save about 8.0 MB.

  • 2 images over 500 KB

    2 images weigh 7.4 MB together. On a phone connection a single image that size takes seconds.

  • 8 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (7.4 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.

  • About 4.2 g of CO₂ per visit

    4.20 g

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

Accessibility

10 to fixGoogle 8287
  • Orphan list items

    Some list items are not inside a list.

  • 5 text elements with low contrast

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

  • Malformed lists

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

  • 2 tap targets too small

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 15 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 33 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 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9286
  • No structured data

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

  • 27 links crawlers can't follow

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 252 internal links, 6 external

    The homepage links to 252 pages on aerox.com and 6 external pages.

5 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Aerox is the World Leader in Engineered Aviation Oxygen Systems. Providing Portable and Installed Solutions. Fly Higher…”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Aerox Aviation Oxygen Systems and Accessories”.

  • Canonical URL set

    The canonical URL is https://www.aerox.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.aerox.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.

  • No llms.txt

    There is no https://www.aerox.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

3 to fix81
  • 1 page points its canonical at the homepage

    https://www.aerox.com/compare declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.aerox.com/compare all use the title “Aerox Aviation Oxygen Systems and Accessories”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.aerox.com/giftcertificates.php and https://www.aerox.com/compare use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 70 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.

  • 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 7388
  • 5 third-party cookies

    5 third-party cookies are 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 “Access to XMLHttpRequest at 'https://cdn-images.mailchimp.com/embedcode/classic-10_7.css' from origin 'https://www.aero…”.

  • 3 distorted images

    3 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”).

2 checks passed
  • Tap targets are thumb-sized

    25 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 1,130 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Register”, “Download the Aerox Corporate Brochure” and “Subscribe”.

  • 3 short forms

    3 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 2 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.

  • 16 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
BigCommerce
Analytics
Google Analytics
Hosting
Cloudflare

Company

Employees
13

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on aerox.com, including 21 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