aaxis.ai website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and IPONWEB and others), adding 534 KiB and 240 ms of main-thread time.

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

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

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

4 KiB could be saved by minifying JavaScript.

Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DIGITAL COMMERCE & ENTERPRISE AI Powering Industrial Distri…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.4 MB in 97 requests on a phone: images 3.3 MB (53), scripts 931 KiB (25) and fonts 93 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

7 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

Your title is only 23 characters: “AAXIS Home Page | AAXIS”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Powering Industrial Distribution” and “Through Cutting-Edge Technology”). One clear main headline is easier for people and search engines.

Your meta description is 236 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 53 pages on aaxis.ai and 4 external pages.

/contact-us, /case-studies-resources/ferguson, /case-studies-resources/ufpi, /case-studies-resources/interstate-batteries, /resource-center and /building-materials and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

/case-studies-resources/ferguson, /case-studies-resources/ufpi and /case-studies-resources/interstate-batteries have no <h1> headline, so visitors and search engines get no clear main topic.

/resource-center, /blog/governing-ai-agents-from-outside-the-agent-what-we-learned-testing-nvidia-openshell and /blog/how-ai-can-improve-client-satisfaction-and-drive-growth-for-fund-administration-firms took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

aaxis.ai has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

aaxis.ai's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 618 words of visible text.

aaxis.ai has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads 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.

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

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.

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