vivapharm.com website review

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

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

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

4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google/Doubleclick Ads and others), adding 1.8 MB and 888 ms of main-thread time.

YouTube costs a phone 877 ms of main-thread work and 1.7 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.

Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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.

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

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

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

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

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “No. 1 GMP Certified Pharmaceutical & Nutraceutical Manufact…”. Most of its time is element render delay (2.3 s).

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

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 3.1 MB in 53 requests on a phone: scripts 1.8 MB (12), images 615 KiB (15) and fonts 316 KiB (9). Under 2 MB keeps phones on slow connections fast.

5 images (182 KiB) 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.

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

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

autocomplete attribute must be used correctly: 2 elements on the page fail this check, rated serious by axe-core.

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

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

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 11 characters: “Home - Viva”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 36 pages on vivapharm.com and 6 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.vivapharm.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.

Your homepage links to https://www.vivapharm.com/viva, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.vivapharm.com/index.php/author/viva and https://www.vivapharm.com/index.php/brochure have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.vivapharm.com/index.php/author/viva, https://www.vivapharm.com/index.php/2026/09/18/viva-pharmaceutical-is-exhibiting-at-supply-side-global-2026, https://www.vivapharm.com/index.php/2026/09/01/viva-pharmaceutical-is-exhibiting-at-the-food-tech-summit-expo-2026 and https://www.vivapharm.com/index.php/2026/08/17/viva-pharmaceutical-is-exhibiting-at-vitafoods-asia-2026 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vivapharm.com/index.php/services, https://www.vivapharm.com/index.php/brochure and https://www.vivapharm.com/index.php/granular-powder 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.

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

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

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

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

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

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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.

The homepage carries about 390 words of visible text.

Before a visitor clicks anything, the page loads Google Ads (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 1 cookie, 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.