Website review, no card needed

ivcevidensia.com logo

ivcevidensia.com website review

Visit site (opens in a new tab)Reviewed 4 November 202631 issues · 81 checks

This review found 31 issues worth fixing on ivcevidensia.com, 9 of them high impact, across 81 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
102 ms79 msMay 16Oct 3188 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202695 ms
May 23, 202697 ms
May 30, 202697 ms
Jun 6, 202689 ms
Jun 13, 202685 ms
Jun 20, 202689 ms
Jun 27, 202694 ms
Jul 4, 202695 ms
Jul 11, 202699 ms
Jul 18, 202694 ms
Jul 25, 202693 ms
Aug 1, 202697 ms
Aug 8, 202693 ms
Aug 15, 202693 ms
Aug 22, 202690 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202685 ms
Sep 19, 202683 ms
Sep 26, 202683 ms
Oct 3, 202682 ms
Oct 10, 202684 ms
Oct 17, 202685 ms
Oct 24, 202685 ms
Oct 31, 202688 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of ivcevidensia.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ivcevidensia.com at 0.4 s0.4 s
  2. ivcevidensia.com at 0.8 s0.8 s
  3. ivcevidensia.com at 1.2 s1.2 s
  4. ivcevidensia.com at 1.6 s1.6 s
  5. ivcevidensia.com at 2.0 s2.0 s
  6. ivcevidensia.com at 2.4 s2.4 s
  7. ivcevidensia.com at 2.8 s2.8 s
  8. ivcevidensia.com at 3.1 s3.1 s

Speed

7 to fix71
  • Render-blocking requests

    1.0 s

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

  • Improve image delivery

    750 ms · 4.7 MB

    7 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • Mobile performance score: 71

    71/100

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

  • Reduce unused JavaScript

    810 ms · 140 KiB

    About 140 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 810 ms faster on a phone.

  • Use efficient cache lifetimes

    700 ms · 98 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Optanon, Google CDN and Azure Web Services and others), adding 1.0 MB and 169 ms of main-thread time.

  • evidensia.be adds 0 ms

    0 ms

    evidensia.be costs a phone 0 ms of main-thread work and 576 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.

  • Reduce unused CSS

    150 ms · 36 KiB

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

  • Legacy JavaScript

    150 ms · 22 KiB

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

  • Font display

    100 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 211 ms of it running JavaScript. That is comfortably low.

  • Server response: 48 ms

    48 ms

    Your server sent the HTML in 48 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “IVC Evidensia”.

  • Real-user TTFB: 975 ms

    975 ms

    Real visitors wait 975 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Time to Interactive: 7.0 s

    7.0 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

7 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 86 ms

    86 ms

    Real visitors wait 86 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Tap response (INP) got 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.022

    0.022

    The layout barely moves while loading (CLS 0.022, good is under 0.1).

  • Total Blocking Time: 12 ms

    12 ms

    Scripts block the page for only 12 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix60
  • Page weight: 5.4 MB in 42 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 42 requests on a phone: images 4.9 MB (14), scripts 344 KiB (8) and fonts 136 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    267 KiB

    2 images are downloaded at several times the size a phone draws them, for example IVC-Evidensia-home-page_01.jpg at 1,800 px wide, shown at 360 px. Resized copies would save about 267 KiB.

  • 2 images in older formats

    2 images (424 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.

  • About 1.5 g of CO₂ per visit

    1.54 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9195
  • 11 text elements with low contrast

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

  • 5 images without alt text

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

  • All page content should be contained by landmarks (12 elements)

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

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8586
  • No meta description

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

  • No structured data

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 39 internal links, 20 external

    The homepage links to 39 pages on ivcevidensia.com and 20 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Healthy Animals, Happy Owners”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “The global leader in veterinary care | IVC Evidensia”.

  • Canonical URL set

    The canonical URL is https://ivcevidensia.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://ivcevidensia.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (326 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 11 pages without a meta description

    https://ivcevidensia.com/career, https://ivcevidensia.com/jobs, https://ivcevidensia.com/career/stories, https://ivcevidensia.com/career/ivc-evidensia-academy, https://ivcevidensia.com/career/graduate-academy and https://ivcevidensia.com/career/ethnic-diversity-scholarship-scheme and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://ivcevidensia.com/about-ivc-evidensia, https://ivcevidensia.com/about-ivc-evidensia/our-senior-leadership-team, https://ivcevidensia.com/about-ivc-evidensia/ethical-statement and https://ivcevidensia.com/about-ivc-evidensia/media-press use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://ivcevidensia.com/jobs has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://ivcevidensia.com/jobs 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.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 2 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Loading the font 'data:application/font-woff;charset=utf-8;base64, d09GRgABAAAAAAZgABAAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAA…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

    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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

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

  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

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

  • No risk reducer

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

  • About 356 words of copy

    The homepage carries about 356 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Download the report (PDF)” and “[email protected]”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 6 other companies contacted

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

2 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ivcevidensia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Imperva

Company

Founded
2017
Headquarters
Keynsham

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on ivcevidensia.com, including 14 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25