Website review, no card needed

anvisgroup.com logo

anvisgroup.com website review

Visit site (opens in a new tab)Reviewed 24 October 202634 issues · 77 checks

This review found 34 issues worth fixing on anvisgroup.com, 11 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
1.3 s1.1 sMay 16Oct 31.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Oct 3, 20261.1 s

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 anvisgroup.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. anvisgroup.com at 0.4 s0.4 s
  2. anvisgroup.com at 0.8 s0.8 s
  3. anvisgroup.com at 1.1 s1.1 s
  4. anvisgroup.com at 1.5 s1.5 s
  5. anvisgroup.com at 1.9 s1.9 s
  6. anvisgroup.com at 2.3 s2.3 s
  7. anvisgroup.com at 2.6 s2.6 s
  8. anvisgroup.com at 3.0 s3.0 s

Speed

8 to fix62
  • Improve image delivery

    30.9 s · 14.6 MB

    26 images could be 14.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 30.9 s faster on a phone.

  • Reduce unused JavaScript

    3.8 s · 398 KiB

    About 398 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 33). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    740 ms · 90 KiB

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

  • Render-blocking requests

    800 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.0 MB and 608 ms of main-thread time.

  • Google CDN adds 417 ms

    417 ms

    Google CDN costs a phone 417 ms of main-thread work and 734 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.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 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 on the main thread

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

  • Use efficient cache lifetimes

    58 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 111 ms

    111 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 64.7 s

    64.7 s

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

  • Speed Index: 15.7 s

    15.7 s

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

  • Time to Interactive: 67.3 s

    67.3 s

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

  • 7 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 159 ms

    159 ms

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

  • Cumulative Layout Shift: 0.062

    0.062

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

Images and page weight

5 to fix18
  • Page weight: 31.0 MB in 89 requests

    31.0 MB

    Your homepage downloads 31.0 MB in 89 requests on a phone: images 19.4 MB (38), media 10.0 MB (2) and scripts 1.0 MB (35). Under 2 MB keeps phones on slow connections fast.

  • 7 images over 500 KB

    7 images weigh 8.4 MB together. On a phone connection a single image that size takes seconds.

  • 15 images far larger than shown

    5.9 MB

    15 images are downloaded at several times the size a phone draws them, for example Dilatoflex_Stillife_20220868.jpg at 8,256 px wide, shown at 352 px. Resized copies would save about 5.9 MB.

  • 22 images in older formats

    22 images (11.8 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.

  • 20 images below the first screen load straight away

    20 images further down the page (9.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 8.8 g of CO₂ per visit

    8.79 g

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

Accessibility

5 to fixGoogle 9192
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

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

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

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

  • ARIA role should be appropriate for the element (20 elements)

    ARIA role should be appropriate for the element: 20 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 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 8593
  • Meta description is short (5 characters)

    Your meta description is only 5 characters: “Anvis”. 70 to 160 characters is enough to sell the click.

  • 24 links with vague text

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

  • 50 internal links, 4 external

    The homepage links to 50 pages on anvisgroup.com and 4 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “ANVIS IS CREATING USE CASES WE CAN'T EVEN IMAGINE YET.”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “ANVIS Group | Tailored rubber antivibration solutions”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://anvisgroup.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://anvisgroup.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 (784 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 5 pages share 2 titles

    /, https://anvisgroup.com/de and https://anvisgroup.com/fr all use the title “ANVIS Group | Tailored rubber antivibration solutions”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://anvisgroup.com/about-anvis, https://anvisgroup.com/solutions, https://anvisgroup.com/standards, https://anvisgroup.com/processes, https://anvisgroup.com/job-offers and https://anvisgroup.com/public-relation-and-press and 9 others use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://anvisgroup.com/anvis/solutions, whose canonical is https://anvisgroup.com/solutions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://anvisgroup.com/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://anvisgroup.com/purchasing/purchasing, https://anvisgroup.com/contact-us, https://anvisgroup.com/nos-apprentis-au-coeur-de-nos-projets and https://anvisgroup.com/2025-gender-equality-index 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    5 of 5 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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.

  • Thin social proof

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

  • No direct contact details

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

  • No form on the homepage

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

  • 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 859 words of copy

    The homepage carries about 859 words of visible text.

2 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Join Us”, “Contact” and “Learn more”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

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

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 anvisgroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Analytics
Google Analytics

Company

Founded
1978
Headquarters
Steinau an der Straße

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on anvisgroup.com, including 12 speed issues, 2 SEO issues and 3 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