invitae.com website review

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

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

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

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

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

8 third-party services load with your homepage (Optanon, Google Tag Manager and Amplitude Mobile Analytics and others), adding 1.3 MB and 233 ms of main-thread time.

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

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

Optanon costs a phone 102 ms of main-thread work and 427 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.

Amplitude Mobile Analytics costs a phone 42 ms of main-thread work and 486 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.

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

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

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.

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

Your largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enable certain functions and tools on thi…”.

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

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

The layout shifts by 0.315 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 2.7 MB in 77 requests on a phone: scripts 2.3 MB (33), images 224 KiB (10) and other files 79 KiB (29). Under 2 MB keeps phones on slow connections fast.

Invitae_Homepage_-_Hero_3780x1312.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images are downloaded at several times the size a phone draws them, for example Invitae_Homepage_-_Text___Media_3_3000x3000.png at 633 px wide, shown at 173 px. Resized copies would save about 45 KiB.

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

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected property name or '}' in JSON at position 1 (line 1 )”.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 23 pages on invitae.com and 19 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.invitae.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.invitae.com/us/providers/papers-and-presentations and https://www.invitae.com/us/providers/educational-webinars all use the title “Scientific Expertise | Labcorp”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.invitae.com/us/providers/papers-and-presentations and https://www.invitae.com/us/providers/educational-webinars 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 https://www.invitae.com/us/providers/test-catalog, whose canonical is https://www.invitae.com/providers/test-catalog. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.invitae.com/us/providers/test-catalog has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.invitae.com/us/providers/test-catalog, https://www.invitae.com/us/contact, https://www.invitae.com/providers/test-catalog/neurology and https://www.invitae.com/providers/test-catalog/genetic-risk have 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.

https://www.invitae.com/us/providers/educational-webinars took over 3 s to send its HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

Large scripts ship without source maps.

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.

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

Before a visitor clicks anything, the page loads Amplitude and Google Tag Manager (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 6 cookies, 1 of them by other companies (measured from a US location before any click).

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