Website review, no card needed
aeva.com website review
Visit site (opens in a new tab)Reviewed 17 November 202645 issues · 89 checks
This review found 45 issues worth fixing on aeva.com, 14 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.0 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 81 ms |
| Jun 6, 2026 | 85 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 93 ms |
| Jun 27, 2026 | 93 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 91 ms |
| Jul 18, 2026 | 91 ms |
| Jul 25, 2026 | 92 ms |
| Aug 1, 2026 | 93 ms |
| Aug 8, 2026 | 91 ms |
| Aug 15, 2026 | 91 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 91 ms |
| Sep 5, 2026 | 89 ms |
| Sep 12, 2026 | 88 ms |
| Sep 19, 2026 | 86 ms |
| Sep 26, 2026 | 92 ms |
| Oct 3, 2026 | 93 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 92 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 88 ms |
| Nov 7, 2026 | 86 ms |
| Nov 14, 2026 | 85 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
Speed
Use efficient cache lifetimes
3.0 s · 77.5 MB111 files are served with short cache lifetimes, so returning visitors download them again (77.5 MB).
Font display
2.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.1 s).
Render-blocking requests
1.7 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Improve image delivery
750 ms · 50.9 MB41 images could be 50.9 MB 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.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 278 KiBAbout 278 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Hubspot, Google Tag Manager and hsappstatic.net and others), adding 791 KiB and 636 ms of main-thread time.
Reduce unused CSS
300 ms · 67 KiBAbout 67 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.
Hubspot adds 250 ms
250 msHubspot costs a phone 250 ms of main-thread work and 302 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.
Google Tag Manager adds 227 ms
227 msGoogle Tag Manager costs a phone 227 ms of main-thread work and 320 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: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 882 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aeva’s next-generation sensing and perception systems use u…”. Most of its time is element render delay (3.6 s).
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
2 images without width and height
2 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-14, real Chrome visitors' tap response (inp) went from 81 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 74 ms
74 msReal visitors wait 74 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Total Blocking Time: 155 ms
155 msScripts block the page for only 155 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 78.0 MB in 135 requests
78.0 MBYour homepage downloads 78.0 MB in 135 requests on a phone: images 52.7 MB (75), media 23.9 MB (7) and scripts 898 KiB (24). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 46.7 MB together. On a phone connection a single image that size takes seconds.
14 images far larger than shown
45.0 MB14 images are downloaded at several times the size a phone draws them, for example 20211105-Aeva-Final-V2-7-With-Logo-1.png at 6,417 px wide, shown at 330 px. Resized copies would save about 45.0 MB.
34 images in older formats
34 images (49.8 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.
33 images below the first screen load straight away
33 images further down the page (49.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 22.1 g of CO₂ per visit
22.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 22.10 g of CO₂e: 2652.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
41 buttons without a name
41 buttons have no accessible name, so screen readers announce just “button”.
36 tap targets too small
36 tap targets are too small or too close together to hit reliably with a finger.
22 text elements with low contrast
22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 70 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
34 internal links, 43 external
The homepage links to 34 pages on aeva.com and 43 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Perception for Everything™”.
Title: 40 characters
Your title is a healthy 40 characters: “Aeva – 4DLiDAR for Autonomous Navigation”.
Canonical URL set
The canonical URL is https://www.aeva.com/.
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.aeva.com/wp-sitemap.xml.
AI search readiness
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.
Some text only appears after JavaScript runs
60%The HTML your server sends has 987 of the 1,650 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.aeva.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.
1 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.
Other pages
15 pages without a meta description
https://www.aeva.com/press/aeva-launches-optical-connectivity-business-signs-first-customer-agreement-for-a-major-hyperscaler, https://www.aeva.com/atlas, https://www.aeva.com/atlas-ultra, https://www.aeva.com/omni, https://www.aeva.com/atlas-orion and https://www.aeva.com/eve-1 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.aeva.com/press/aeva-launches-optical-connectivity-business-signs-first-customer-agreement-for-a-major-hyperscaler, https://www.aeva.com/press/aeva-introduces-atlas-ultra-its-slimmest-high-resolution-long-range-4d-lidar-sensor-at-ces-2025, https://www.aeva.com/media/cnbc-squawk-alley-interviews-aeva-ceo-on-taking-the-company-public-on-the-nyse, https://www.aeva.com/media/volkswagens-artemis-ceo-on-unique-autonomous-driving-capabilities-unlocked-by-aevas-4d-lidar and https://www.aeva.com/media/cnbc-mad-moneys-jim-cramer-interview-with-aeva-ceo-soroush-salehian have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://www.aeva.com/news, https://www.aeva.com/contact-us, https://www.aeva.com/media/cnbc-squawk-alley-interviews-aeva-ceo-on-taking-the-company-public-on-the-nyse, https://www.aeva.com/media/volkswagens-artemis-ceo-on-unique-autonomous-driving-capabilities-unlocked-by-aevas-4d-lidar and https://www.aeva.com/media/cnbc-mad-moneys-jim-cramer-interview-with-aeva-ceo-soroush-salehian have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://www.aeva.com/careers took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 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
4 small tap targets
4 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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 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: 2 customer or partner logos. 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 1,650 words of copy
The homepage carries about 1,650 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “JOIN THE TEAM” and “CONTACT US”.
5 calls to action
The homepage has 5 calls to action, for example “Join the Team”, “Contact Us” and “Join The Team”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 7 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.
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 aeva.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
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Hiring
- Hiring
- 44 open roles
- Job board
- careers page
- Careers page
- www.aeva.com/careers (opens in a new tab)
Company
- Founded
- 2016
- Headquarters
- Mountain View
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on aeva.com, including 20 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.