Website review, no card needed

canaan.com logo

canaan.com website review

Visit site (opens in a new tab)Reviewed 26 October 202625 issues · 69 checks

This review found 25 issues worth fixing on canaan.com, 11 of them high impact, across 69 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

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

How it loaded on a phone

  1. canaan.com at 0.8 s0.8 s
  2. canaan.com at 1.5 s1.5 s
  3. canaan.com at 2.3 s2.3 s
  4. canaan.com at 3.0 s3.0 s
  5. canaan.com at 3.8 s3.8 s
  6. canaan.com at 4.5 s4.5 s
  7. canaan.com at 5.3 s5.3 s
  8. canaan.com at 6.0 s6.0 s

Speed

6 to fix55
  • Render-blocking requests

    5.6 s

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

  • Use efficient cache lifetimes

    3.1 s · 558 KiB

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

  • Reduce unused JavaScript

    2.8 s · 564 KiB

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

  • Improve image delivery

    5.5 MB

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

  • Mobile performance score: 55

    55/100

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

  • Font display

    550 ms

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

  • Legacy JavaScript

    200 ms · 41 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Unpkg and Amazon Web Services and others), adding 489 KiB and 177 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Document request latency

    26 KiB

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

  • Reduce unused CSS

    17 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

  • Server response: 91 ms

    91 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 17.9 s

    17.9 s

    Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Building Fast Planes, Fast”.

  • Speed Index: 14.1 s

    14.1 s

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

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 18.5 s

    18.5 s

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

  • 12 images without width and height

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

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

2 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 54 ms

    54 ms

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

Images and page weight

1 to fix33
  • Page weight: 7.3 MB in 52 requests

    7.3 MB

    Your homepage downloads 7.3 MB in 52 requests on a phone: images 6.1 MB (17), scripts 1.0 MB (7) and fonts 168 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 2.1 g of CO₂ per visit

    2.08 g

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

Accessibility

3 to fixGoogle 8995
  • 2 text elements with low contrast

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

  • Alternative text of images should not be repeated as text (12 elements)

    Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (13 characters)

    Your title is only 13 characters: “Home - Canaan”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“We back founders who make the impossible inevitab…” and “Portfolio Stories”). One clear main headline is easier for people and search engines.

  • No XML sitemap

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

  • Open Graph partly set

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

  • 28 internal links, 8 external

    The homepage links to 28 pages on canaan.com and 8 external pages.

4 checks passed
  • Meta description: 100 characters

    Your meta description is 100 characters: “Canaan is an early-stage venture capital firm that invests in visionaries with transformative ideas.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

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

Other pages

1 to fix98
  • 6 pages share a meta description

    https://canaan.com/team, https://canaan.com/companies, https://canaan.com/about, https://canaan.com/contact, https://canaan.com/resources and https://canaan.com/legal use the same meta description. A description written for each page earns more clicks.

  • 3 pages with very little text

    https://canaan.com/team, https://canaan.com/contact and https://canaan.com/resources 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.

  • 3 pages slow to respond

    https://canaan.com/companies, https://canaan.com/contact and https://canaan.com/resources took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

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

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9696
  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

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

  • Only about 118 words

    The homepage has only about 118 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 2 calls to action

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

  • 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 canaan.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
Tailwind CSS
Analytics
Google Analytics
Hosting
Akamai Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on canaan.com, including 11 speed issues, 3 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