vetigel.com website review

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

YouTube costs a phone 2.4 s of main-thread work and 6.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and hsappstatic.net and others), adding 9.4 MB and 3.9 s of main-thread time.

Google Tag Manager costs a phone 623 ms of main-thread work and 846 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 254 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 410 ms faster on a phone.

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

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

Vimeo costs a phone 87 ms of main-thread work and 511 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.

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

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

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

8 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.

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

4 KiB could be saved by minifying CSS.

Your largest element takes 59.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

5 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 11.9 MB in 351 requests on a phone: scripts 9.0 MB (116), other files 766 KiB (143) and HTML 627 KiB (14). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example lighter at 1,920 px wide, shown at 351 px. Resized copies would save about 111 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

There are 2 <h1> headlines (“<img src="//vetigel.com/cdn/shop/files/Vetigel_lo…” and “Stop bleeding in seconds”). One clear main headline is easier for people and search engines.

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

The homepage links to 67 pages on vetigel.com and 25 external pages.

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

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

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.

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

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, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 36 cookies, 11 of them by other companies (measured from a US location before any click).

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