Website review, no card needed

aeris.com logo

aeris.com website review

Visit site (opens in a new tab)Reviewed 27 October 202640 issues · 90 checks

This review found 40 issues worth fixing on aeris.com, 18 of them high impact, across 90 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
9.3 s5.6 sMay 9Oct 246.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20268.4 s
May 16, 20268.6 s
May 23, 20268.9 s
May 30, 20268.7 s
Jun 6, 20268.7 s
Jun 13, 20268.1 s
Jun 20, 20267.5 s
Jun 27, 20267.6 s
Jul 4, 20267.7 s
Jul 11, 20267.7 s
Jul 18, 20267.7 s
Jul 25, 20267.9 s
Aug 1, 20267.9 s
Aug 8, 20267.8 s
Aug 15, 20267.7 s
Aug 22, 20267.4 s
Aug 29, 20267.7 s
Sep 5, 20267.7 s
Sep 12, 20267.2 s
Sep 19, 20266.7 s
Sep 26, 20267.1 s
Oct 3, 20267.2 s
Oct 10, 20267.1 s
Oct 17, 20266.8 s
Oct 24, 20266.0 s
Real-visitor tap response (INP)75th percentile, phones
233 ms144 msMay 9Oct 24195 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026202 ms
May 16, 2026210 ms
May 23, 2026211 ms
May 30, 2026223 ms
Jun 6, 2026200 ms
Jun 13, 2026200 ms
Jun 20, 2026200 ms
Jun 27, 2026187 ms
Jul 4, 2026188 ms
Jul 11, 2026186 ms
Jul 18, 2026174 ms
Jul 25, 2026177 ms
Aug 1, 2026166 ms
Aug 8, 2026171 ms
Aug 15, 2026177 ms
Aug 22, 2026183 ms
Aug 29, 2026201 ms
Sep 5, 2026210 ms
Sep 12, 2026185 ms
Sep 19, 2026154 ms
Sep 26, 2026183 ms
Oct 3, 2026183 ms
Oct 10, 2026184 ms
Oct 17, 2026203 ms
Oct 24, 2026195 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 aeris.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aeris.com at 0.9 s0.9 s
  2. aeris.com at 1.9 s1.9 s
  3. aeris.com at 2.8 s2.8 s
  4. aeris.com at 3.8 s3.8 s
  5. aeris.com at 4.7 s4.7 s
  6. aeris.com at 5.7 s5.7 s
  7. aeris.com at 6.6 s6.6 s
  8. aeris.com at 7.5 s7.5 s

Speed

14 to fix25
  • Reduce unused JavaScript

    3.7 s · 631 KiB

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

  • Main-thread work: 41.6 s

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

  • Use efficient cache lifetimes

    1.6 s · 509 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Google Tag Manager adds 1.2 s

    1.2 s

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

  • Mobile performance score: 25

    25/100

    Your mobile performance score is 25 (desktop: 50). 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, cookiepro.com and Hubspot and others), adding 1.4 MB and 2.8 s of main-thread time.

  • Improve image delivery

    750 ms · 501 KiB

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

  • Reduce unused CSS

    660 ms · 67 KiB

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

  • 20 long tasks on the main thread

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

  • cookiepro.com adds 398 ms

    398 ms

    cookiepro.com costs a phone 398 ms of main-thread work and 217 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 337 ms

    337 ms

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

  • Hubspot adds 338 ms

    338 ms

    Hubspot costs a phone 338 ms of main-thread work and 140 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.

  • Clarity adds 282 ms

    282 ms

    Clarity costs a phone 282 ms of main-thread work and 28 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

    180 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    44 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 50 but mobile only 25. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    9 KiB

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

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

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

  • Real-user LCP: 7.2 s

    7.2 s

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

  • Real-user FCP: 7.5 s

    7.5 s

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

  • Largest Contentful Paint: 21.2 s

    21.2 s

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

  • Speed Index: 15.4 s

    15.4 s

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

  • Total Blocking Time: 11.3 s

    11.3 s

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

  • Time to Interactive: 49.0 s

    49.0 s

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

  • First Contentful Paint: 6.7 s

    6.7 s

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

  • Real-user TTFB: 890 ms

    890 ms

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

  • Tap response (INP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 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.

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

    -24%

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

  • 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: 4.4 MB in 177 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 177 requests on a phone: images 2.2 MB (59), scripts 1.7 MB (52) and fonts 189 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

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

  • 1 image far larger than shown

    71 KiB

    1 image is downloaded at several times the size a phone draws it, for example Partner-Ecosystem_1.webp at 1,200 px wide, shown at 256 px. Resized copies would save about 71 KiB.

  • 2 images in older formats

    2 images (70 KiB) 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 1.2 g of CO₂ per visit

    1.25 g

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

Accessibility

3 to fixGoogle 9595
  • 4 tap targets too small

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Headings skip levels

    Headings skip levels (h2 → h4), 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. (1 element).

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 10090
  • Title is short (27 characters)

    Your title is only 27 characters: “Aeris: Secure IoT Solutions”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 120 internal links, 11 external

    The homepage links to 120 pages on aeris.com and 11 external pages.

6 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Aeris provides cutting-edge cellular IoT solutions, offering seamless connectivity, security and advanced IoT platform …”.

  • One H1 headline

    Your main headline reads: “The secure connectivity platform for the Physical AI world”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness, Organization and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.aeris.com/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing logo, sameAs (social profiles) 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.

  • No llms.txt

    There is no https://www.aeris.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,664 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.aeris.com/connected-vehicles and https://www.aeris.com/platform/service-management all use the title “Aeris Mobility Suite | Optimize Connected Vehicle Services”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.aeris.com/use-cases has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.aeris.com/connected-vehicles and https://www.aeris.com/platform/service-management 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 43 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.

  • 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

1 to fixGoogle 10093
  • 9 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 2,302 words of visible text.

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Learn more Learn more”, “Contact Us” and “Book a meeting Book a meeting”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies (measured from a US location before any click).

  • 44 other companies contacted

    Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Upkeep, stack and company

Stack

CMS
WordPress
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Headquarters
San Jose

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on aeris.com, including 23 speed issues, 2 SEO issues and 4 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