nuix.com website review

24 images could be 9.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

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

About 130 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.

6 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google Fonts and others), adding 786 KiB and 601 ms of main-thread time.

Google Tag Manager costs a phone 524 ms of main-thread work and 522 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.

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (33 KiB).

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 50.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FINDING TRUTH IN THE DIGITAL WORLD Leading AI-powered solut…”.

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

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

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

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

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

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

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

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

Your homepage downloads 15.7 MB in 80 requests on a phone: images 13.7 MB (61), scripts 894 KiB (7) and other files 520 KiB (3). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example Doc Portal Web Image 1800x700 1 (2).jpg at 5,400 px wide, shown at 390 px. Resized copies would save about 5.3 MB.

Doc Portal Web Image 1800x700 1 (2).jpg weighs 4.3 MB. On a phone connection a single image that size takes seconds.

13 images (6.0 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.

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

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

1 button has no accessible name, so screen readers announce just “button”.

8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 element hidden from screen readers can still receive keyboard focus.

7 images have no alt text, which hurts accessibility and image search.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 67 characters, so Google will cut it off around 60: “Nuix: Leading Global Provider of Investigative & Analytics Software”.

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 143 pages on nuix.com and 12 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.

/our-industries, /about-us and /solutions/neo-foundation have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /solutions/neo-discover, whose canonical is /solutions/nuix-discover. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/request-a-demo and /solutions/neo-discover have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Large scripts ship without source maps.

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

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

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

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 2,065 words of visible text.

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 Ads, Google Analytics and Google Tag Manager (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.

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