xait.com website review

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

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

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

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

8 third-party services load with your homepage (Unpkg, hsappstatic.net and Hubspot and others), adding 1.2 MB and 1.7 s of main-thread time.

Unpkg costs a phone 936 ms of main-thread work and 96 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.

hsappstatic.net costs a phone 485 ms of main-thread work and 697 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.

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

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

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

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

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

4 KiB could be saved by minifying CSS.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Xait combines enterprise proposal software with Agentic AI …”.

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

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

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

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

For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

Your homepage downloads 3.2 MB in 144 requests on a phone: scripts 1.7 MB (35), images 1.3 MB (76) and stylesheets 119 KiB (13). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example www.xait.comhubfscustomer-storiesDeepOceanDeepocean-customer at 1,920 px wide, shown at 302 px. Resized copies would save about 98 KiB.

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

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

Elements must only use permitted ARIA attributes: 7 elements on the page fail this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Your title is 73 characters, so Google will cut it off around 60: “Xait – Software for Proposals, Co-Authoring, RFPs and Intelligent Pricing”.

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 65 pages on xait.com and 15 external pages.

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.

There is no https://www.xait.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.

https://www.xait.com/lp/get-started-with-xait has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.xait.com/blog/bids-and-proposals and https://www.xait.com/blog/agentic-ai-automation use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.xait.com/lp/get-started-with-xait, whose canonical is https://www.xait.com/get-started-with-xait. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.xait.com/lp/get-started-with-xait has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.xait.com/lp/get-started-with-xait 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.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 710 words of visible text.

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

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

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