Website review, no card needed

cadre.com logo

cadre.com website review

Visit site (opens in a new tab)Reviewed 27 October 202629 issues · 72 checks

This review found 29 issues worth fixing on cadre.com, 8 of them high impact, across 72 checks. The most urgent: 5 tap targets too small. 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

Full-page screenshot of cadre.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix87
  • Mobile performance score: 87

    87/100

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

  • 5 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Reduce unused JavaScript

    93 KiB

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

  • Improve image delivery

    32 KiB

    1 image could be 32 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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: 1.0 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

2 to fix86
  • Total Blocking Time: 508 ms

    508 ms

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

  • Time to Interactive: 3.9 s

    3.9 s

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

  • Not enough real-visitor data yet

    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.

4 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

  • First Contentful Paint: 0.8 s

    0.8 s

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

  • Largest Contentful Paint: 1.5 s

    1.5 s

    Your largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • Speed Index: 1.1 s

    1.1 s

    Visually, the page fills in at 1.1 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.21 g

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

4 checks passed
  • Page weight: 746 KiB in 15 requests

    746 KiB

    Your homepage downloads 746 KiB in 15 requests on a phone: scripts 284 KiB (1), fonts 222 KiB (2) and other files 130 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

7 to fixGoogle 9089
  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

9 to fixGoogle 6340
  • Page is set to noindex

    The robots meta tag says “noindex”: Google is told not to list this page at all.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (5 characters)

    Your title is only 5 characters: “Cadre”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (18 characters)

    Your meta description is only 18 characters: “Created with Figma”. 70 to 160 characters is enough to sell the click.

  • 8 H1 headlines

    There are 8 <h1> headlines (“A new era in”, “private markets” and “A new era in”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at cadre.com/robots.txt, the first file search crawlers ask for.

  • 12 internal links, 0 external

    The homepage links to 12 pages on cadre.com and 0 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://www.cadre.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://www.cadre.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix85
  • 1 linked page hidden from search

    https://www.cadre.com/privacy-and-cookies is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://www.cadre.com/privacy-and-cookies all use the title “Cadre”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 internal page checked

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

5 checks passed
  • Linked pages load

    All 1 page we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 analytics detected

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

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

    The homepage carries about 302 words of visible text.

1 checks passed
  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

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

Upkeep, stack and company

Stack

Hosting
Cloudflare

Company

Founded
2014
Headquarters
New York City

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on cadre.com, including 4 speed issues, 9 SEO issues and 6 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