Website review, no card needed

chiron-group.com logo

chiron-group.com website review

Visit site (opens in a new tab)Reviewed 19 November 202641 issues · 84 checks

This review found 41 issues worth fixing on chiron-group.com, 8 of them high impact, across 84 checks. The most urgent: page weight: 26.2 MB in 50 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
6.6 s3.0 sMay 30Nov 143.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20266.1 s
Jun 6, 20266.1 s
Jun 13, 20266.2 s
Jun 20, 20266.2 s
Jun 27, 20265.7 s
Jul 4, 20264.2 s
Jul 11, 20264.0 s
Jul 18, 20263.5 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.4 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.4 s
Oct 3, 20263.6 s
Oct 10, 20263.4 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.4 s
Nov 7, 20263.5 s
Nov 14, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
348 ms62 msMay 30Nov 14103 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026314 ms
Jun 6, 2026315 ms
Jun 13, 2026306 ms
Jun 20, 2026287 ms
Jun 27, 2026180 ms
Jul 4, 2026113 ms
Jul 11, 2026113 ms
Jul 18, 2026110 ms
Jul 25, 2026105 ms
Aug 1, 2026103 ms
Aug 8, 202698 ms
Aug 15, 2026102 ms
Aug 22, 2026103 ms
Aug 29, 2026103 ms
Sep 5, 2026103 ms
Sep 12, 2026100 ms
Sep 19, 202696 ms
Sep 26, 202695 ms
Oct 3, 202695 ms
Oct 10, 202696 ms
Oct 17, 202699 ms
Oct 24, 2026103 ms
Oct 31, 2026105 ms
Nov 7, 2026104 ms
Nov 14, 2026103 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 chiron-group.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix91
  • Use efficient cache lifetimes

    300 ms · 6.7 MB

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

  • Improve image delivery

    1.1 MB

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

  • Render-blocking requests

    900 ms

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

  • Reduce initial server response time

    508 ms

    Reduce initial server response time. Google estimates savings of 508 ms on a phone.

  • Document request latency

    500 ms

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

  • Reduce unused JavaScript

    416 KiB

    About 416 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 264 ms

    264 ms

    Google Tag Manager costs a phone 264 ms of main-thread work and 314 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.

  • Server response: 608 ms

    608 ms

    Your server takes 608 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Cloudflare and Fathom Analytics and others), adding 450 KiB and 281 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    10 KiB

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

  • 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
  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.1 s

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

Core Web Vitals

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

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s 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.

  • 25 images without width and height

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

  • Speed Index: 3.8 s

    3.8 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Learning from established fields of knowledge and adopting …”. Most of its time is element render delay (1.5 s).

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Total Blocking Time: 206 ms

    206 ms

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

7 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 119 ms

    119 ms

    Real visitors wait 119 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.5 s

    1.5 s

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

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

    -67%

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

  • Largest content (LCP) got 43% faster for real visitors

    -43%

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

5 to fix28
  • Page weight: 26.2 MB in 50 requests

    26.2 MB

    Your homepage downloads 26.2 MB in 50 requests on a phone: media 21.9 MB (8), images 3.4 MB (27) and scripts 652 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    presse_amb_2026_newskachel.png weighs 490 KiB. On a phone connection a single image that size takes seconds.

  • 21 images in older formats

    21 images (2.5 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.

  • 24 images below the first screen load straight away

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

  • 1 image far larger than shown

    52 KiB

    1 image is downloaded at several times the size a phone draws it, for example cg_web_start_2023_9.jpg at 1,160 px wide, shown at 342 px. Resized copies would save about 52 KiB.

  • About 7.4 g of CO₂ per visit

    7.43 g

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

Accessibility

6 to fixGoogle 8390
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 21 images without alt text

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

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

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

  • No main landmark

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

  • 15 links without text

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

  • 2 form fields without a label

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

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

4 to fixGoogle 8587
  • No structured data

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://chiron-group.com/sitemap.xml, so Google discovers your pages only by following links.

  • 10 links crawlers can't follow

    10 links have no real href, so search engines can't follow them.

  • 165 internal links, 13 external

    The homepage links to 165 pages on chiron-group.com and 13 external pages.

5 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “The CHIRON Group is a professional provider of machining centers for milling & mill-turn, automation, turnkey, services…”.

  • One H1 headline

    Your main headline reads: “Our expertise – your added value”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Performance meets precision | CHIRON Group SE”.

  • Canonical URL set

    The canonical URL is https://chiron-group.com/.

  • robots.txt in place

    robots.txt is in place.

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://chiron-group.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 (855 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix62
  • 1 page without a title

    https://chiron-group.com/company/sustainability has no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://chiron-group.com/set-language/en declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://chiron-group.com/set-language/en and https://chiron-group.com/set-language/zh//cn all use the title “Performance meets precision | CHIRON Group SE”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://chiron-group.com/expertises/outlet and https://chiron-group.com/company/sustainability have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://chiron-group.com/set-language/en and https://chiron-group.com/set-language/zh//cn use the same meta description. A description written for each page earns more clicks.

  • 7 pages slow to respond

    https://chiron-group.com/consent, https://chiron-group.com/locations, https://chiron-group.com/set-language/zh//cn, https://chiron-group.com/company/corporate-culture, https://chiron-group.com/company/group-executive-committee and https://chiron-group.com/company/compliance and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 582 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Fathom and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 1 of them by other companies (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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 chiron-group.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
Tailwind CSS
Analytics
Google Tag Manager | Fathom
Hosting
Cloudflare

Company

Employees
90
Headquarters
Charlotte

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on chiron-group.com, including 16 speed issues, 4 SEO issues and 2 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