invitro.com.au website review

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.3 s).

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

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

13 images could be 6.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 982 KiB and 797 ms of main-thread time.

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

Google Tag Manager costs a phone 451 ms of main-thread work and 624 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 482 KiB of JavaScript is downloaded but never used on this page.

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

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

18 KiB could be saved by minifying CSS.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

16 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Since 2002, we have partnered with leading global manufactu…”. Most of its time is element render delay (2.4 s).

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

10 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 9.5 MB in 145 requests on a phone: images 7.6 MB (37), scripts 1.5 MB (72) and fonts 188 KiB (5). Under 2 MB keeps phones on slow connections fast.

6 images weigh 6.7 MB together. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example TSMED3.png at 1,020 px wide, shown at 155 px. Resized copies would save about 5.0 MB.

18 images (7.4 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.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is 101 characters, so Google will cut it off around 60: “In Vitro Technologies :: In Vitro Technologies - Empowering breakthroughs in Discovery an…”.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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 incomplete here.

The homepage links to 27 pages on invitro.com.au and 35 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://invitro.com.au/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://invitro.com.au/our-company, https://invitro.com.au/our-company/national-distribution-network, https://invitro.com.au/our-company/iso-9001-certified, https://invitro.com.au/our-company/locations, https://invitro.com.au/our-company/our-core-values and https://invitro.com.au/contact-us and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://invitro.com.au/feedback 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 16 found) and read each the way a search engine does.

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

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 404 ()”.

4 images are served at too low a resolution for sharp phone screens.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage has only about 181 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (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 12 cookies, 1 of them by other companies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.