Website review, no card needed

crouzet.com logo

crouzet.com website review

Visit site (opens in a new tab)Reviewed 26 October 202637 issues · 85 checks

This review found 37 issues worth fixing on crouzet.com, 15 of them high impact, across 85 checks. The most urgent: font display. 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
4.8 s3.0 sMay 9Oct 244.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.3 s
May 30, 20263.2 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.7 s
Aug 29, 20264.0 s
Sep 5, 20264.2 s
Sep 12, 20264.3 s
Sep 19, 20264.4 s
Sep 26, 20264.5 s
Oct 3, 20264.6 s
Oct 10, 20264.4 s
Oct 17, 20264.3 s
Oct 24, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
159 ms130 msMay 9Oct 24153 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026142 ms
May 16, 2026146 ms
May 23, 2026146 ms
May 30, 2026144 ms
Jun 6, 2026140 ms
Jun 13, 2026133 ms
Jun 20, 2026139 ms
Jun 27, 2026146 ms
Jul 4, 2026145 ms
Jul 11, 2026150 ms
Jul 18, 2026148 ms
Jul 25, 2026145 ms
Aug 1, 2026148 ms
Aug 8, 2026151 ms
Aug 15, 2026153 ms
Aug 22, 2026149 ms
Aug 29, 2026148 ms
Sep 5, 2026144 ms
Sep 12, 2026142 ms
Sep 19, 2026145 ms
Sep 26, 2026139 ms
Oct 3, 2026156 ms
Oct 10, 2026154 ms
Oct 17, 2026146 ms
Oct 24, 2026153 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 crouzet.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crouzet.com at 1.5 s1.5 s
  2. crouzet.com at 2.9 s2.9 s
  3. crouzet.com at 4.4 s4.4 s
  4. crouzet.com at 5.9 s5.9 s
  5. crouzet.com at 7.3 s7.3 s
  6. crouzet.com at 8.8 s8.8 s
  7. crouzet.com at 10.3 s10.3 s
  8. crouzet.com at 11.7 s11.7 s

Speed

11 to fix53
  • Font display

    3.0 s

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

  • Reduce unused JavaScript

    1.3 s · 681 KiB

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

  • Render-blocking requests

    1.8 s

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

  • 3,240 HTML elements

    The page has 3,240 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    5.4 MB

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

  • Mobile performance score: 53

    53/100

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    450 ms · 100 KiB

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

  • Google CDN adds 306 ms

    306 ms

    Google CDN costs a phone 306 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.

  • Google Tag Manager adds 243 ms

    243 ms

    Google Tag Manager costs a phone 243 ms of main-thread work and 309 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.6 s

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

  • 9 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 5 KiB

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

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 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.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 425 ms

    425 ms

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

Core Web Vitals

11 to fix67
  • 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 LCP: 5.2 s

    5.2 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Time to Interactive: 28.3 s

    28.3 s

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

  • Speed Index: 15.3 s

    15.3 s

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

  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Manufacturing the future with mechatronic products”. Most of its time is element render delay (6.7 s).

  • Largest content (LCP) got 28% slower for real visitors

    +28%

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

  • Total Blocking Time: 398 ms

    398 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

3 checks passed
  • Real-user INP: 182 ms

    182 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

3 to fix45
  • Page weight: 18.3 MB in 121 requests

    18.3 MB

    Your homepage downloads 18.3 MB in 121 requests on a phone: images 10.7 MB (64), media 4.7 MB (1) and scripts 1.4 MB (29). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (2.7 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.

  • 1 image below the first screen load straight away

    1 image further down the page (147 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.2 g of CO₂ per visit

    5.18 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9593
  • 7 text elements with low contrast

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

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

    All page content should be contained by landmarks: 24 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • Headings should not be empty (1 element)

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

2 checks passed
  • Every image has alt text

    All 149 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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

Google 100100
  • 196 internal links, 59 external

    The homepage links to 196 pages on crouzet.com and 59 external pages.

8 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Crouzet manufactures mechatronic components for the demanding transport, energy, building and machinery industries, to …”.

  • One H1 headline

    Your main headline reads: “Manufacturing the futurewith mechatronic products”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Manufacturing the future of mechatronic products - Crouzet”.

  • Canonical URL set

    The canonical URL is https://www.crouzet.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://www.crouzet.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.crouzet.com/worldwide-distribution-network, https://www.crouzet.com/news, https://www.crouzet.com/careers, https://www.crouzet.com/contact-us and https://www.crouzet.com/market-applications have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.crouzet.com/careers and https://www.crouzet.com/market-applications have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.crouzet.com/contact-us and https://www.crouzet.com/applications/airplanes took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 48 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

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    17 of 20 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: 9 customer or partner logos. 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 337 words of copy

    The homepage carries about 337 words of visible text.

2 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact”, “Careers Apply” and “Download our Aerospace brochure”.

  • Analytics in place

    Analytics detected: Google Analytics and Matomo.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 cookies set on arrival

    7

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

  • 13 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

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

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 crouzet.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
Framework
jQuery
Analytics
Google Analytics | Matomo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on crouzet.com, including 22 speed 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