Website review, no card needed

altair.com logo

altair.com website review

Visit site (opens in a new tab)Reviewed 19 October 202626 issues · 78 checks

This review found 26 issues worth fixing on altair.com, 11 of them high impact, across 78 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
3.8 s2.8 sMay 2Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.6 s
May 9, 20263.5 s
May 16, 20263.4 s
May 23, 20263.3 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
407 ms318 msMay 2Oct 17385 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026332 ms
May 9, 2026328 ms
May 16, 2026328 ms
May 23, 2026334 ms
May 30, 2026339 ms
Jun 6, 2026351 ms
Jun 13, 2026363 ms
Jun 20, 2026366 ms
Jun 27, 2026367 ms
Jul 4, 2026368 ms
Jul 11, 2026369 ms
Jul 18, 2026373 ms
Jul 25, 2026370 ms
Aug 1, 2026369 ms
Aug 8, 2026373 ms
Aug 15, 2026374 ms
Aug 22, 2026372 ms
Aug 29, 2026371 ms
Sep 5, 2026369 ms
Sep 12, 2026373 ms
Sep 19, 2026383 ms
Sep 26, 2026386 ms
Oct 3, 2026391 ms
Oct 10, 2026397 ms
Oct 17, 2026385 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 altair.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. altair.com at 0.4 s0.4 s
  2. altair.com at 0.8 s0.8 s
  3. altair.com at 1.1 s1.1 s
  4. altair.com at 1.5 s1.5 s
  5. altair.com at 1.9 s1.9 s
  6. altair.com at 2.3 s2.3 s
  7. altair.com at 2.6 s2.6 s
  8. altair.com at 3.0 s3.0 s

Speed

6 to fix55
  • Reduce unused JavaScript

    3.8 s · 757 KiB

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

  • Render-blocking requests

    2.8 s

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

  • Use efficient cache lifetimes

    1.9 s · 351 KiB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    750 ms · 143 KiB

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

  • 1,861 HTML elements

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (siemens-cdn.com, Usercentrics CMP and niceincontact.com), adding 336 KiB and 315 ms of main-thread time.

  • Font display

    250 ms

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 20 KiB

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

  • Phones get a much slower page than desktops

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

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

  • Improve image delivery

    5 KiB

    1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

9 to fix33
  • 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 TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 15.6 s

    15.6 s

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

  • First Contentful Paint: 7.4 s

    7.4 s

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

  • Time to Interactive: 15.7 s

    15.7 s

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

  • Speed Index: 7.7 s

    7.7 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 330 ms

    330 ms

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

4 checks passed
  • 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 11% faster for real visitors

    -11%

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

  • Total Blocking Time: 186 ms

    186 ms

    Scripts block the page for only 186 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 99 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 99 requests on a phone: scripts 1.4 MB (50), fonts 337 KiB (5) and other files 231 KiB (31). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.65 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9196
  • 1 image without alt text

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

Google 92100
  • 13 internal links, 9 external

    The homepage links to 13 pages on altair.com and 9 external pages.

8 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Siemens acquires Altair, expanding Siemens Xcelerator with the world's most complete AI-powered world's most complete A…”.

  • One H1 headline

    Your main headline reads: “Siemens acquires Altair”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Altair is now part of Siemens | Siemens”.

  • Canonical URL set

    The canonical URL is https://www.siemens.com/en-us/company/about/businesses/digital-industries/altair/.

  • Structured data in place

    Structured data found: WebPage.

  • 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://www.siemens.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 (387 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.siemens.com/llms.txt (3 KiB, 19 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.siemens.com/en-us/products/simcenter/digital-engineering/altair-one has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.siemens.com/en-us/contact has 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.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 13 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 a meta description

    All 13 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 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 small tap targets

    3 of 8 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 fix50
  • 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.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 form on the homepage

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

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

    The homepage carries about 376 words of visible text.

1 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact us”.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 7 other companies contacted

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

2 checks passed
  • Consent tool: Usercentrics

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

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 altair.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
Astro

Company

Founded
1985
Headquarters
Troy

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on altair.com, including 15 speed 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