identigen.com website review

15 files are served with short cache lifetimes, so returning visitors download them again (7.4 MB).

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

7 third-party services load with your homepage (quadia.net, Google Tag Manager and Optanon and others), adding 8.9 MB and 735 ms of main-thread time.

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

cloudfront.net costs a phone 0 ms of main-thread work and 7.0 MB 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.

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

quadia.net costs a phone 431 ms of main-thread work and 1.4 MB 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.

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

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

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

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

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

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

4 KiB JavaScript is shipped twice across bundles.

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

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

Your 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 image “DataLabs Healthier animals”.

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

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

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

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 10.6 MB in 83 requests on a phone: images 8.2 MB (20), scripts 2.2 MB (26) and stylesheets 95 KiB (8). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (490 KiB) 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 3.00 g of CO₂e: 360.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 frames have no title, so screen-reader users cannot tell what they contain.

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 21 pages on identigen.com and 9 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/, /es, /fr, /de, /nl and /pt and 1 other all use the title “IdentiGEN - Centre of excellence for data-driven solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

/es, /fr, /de, /nl, /pt and /it use the same meta description. A description written for each page earns more clicks.

/smart-data-philosophy has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://pixel.wp.com/g.gif?v=ext&blog=207256366&post=2&tz=0&srv=www.identigen.com&hp=vip&j=1%3A16.1.3&host=www.identigen.com&ref=&fcp=836&rand=0.2601754299068906.

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

4 errors were logged to the browser console while the page loaded, for example “Creating a TrustedTypePolicy named 'goog#html' violates the following Content Security policy directive: "trusted-types…”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Content security policy”).

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.

identigen.com 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.

identigen.com'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 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 361 words of visible text.

identigen.com 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 Tag Manager and LinkedIn Insight (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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