crunchbase.com website review

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

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

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

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

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

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

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

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

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

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

Your largest element renders in 1.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Before It's News, It's In Crunchbase”.

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

The page is fully interactive after 1.0 s.

Your homepage downloads 202 KiB in 16 requests on a phone: scripts 112 KiB (2), fonts 27 KiB (1) and other files 26 KiB (5). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

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

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

All 28 images in the HTML carry an alt attribute.

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

Your meta description is 92 characters: “Discover private company data, funding insights, and AI-powered predictions with Crunchbase.”.

Your main headline reads: “Before It's News, It's In Crunchbase”.

Your title is a healthy 59 characters: “Crunchbase | Private Company Data & Predictive Intelligence”.

robots.txt is in place and points crawlers to your sitemap.

Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

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

1 page of 8 loaded without an error (the rest turned automated requests away).

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

All 1 page that loaded have a meta description.

Every page we checked has its own title.

None of the pages we checked carries a noindex tag.

All 1 page that loaded have a <title>.

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

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

The page declares a mobile viewport.

The homepage is served over HTTPS (crunchbase.com).

The certificate from Let's Encrypt · YE2 verifies for crunchbase.com and is valid for another 70 days.

X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

http://crunchbase.com redirects to the secure version.

The server speaks HTTP/2, so browsers load many files over one connection.

All 33 links checked from your homepage (13 internal, 20 external) answered without errors.

A security.txt file tells researchers how to report a problem with your site.

crunchbase.com was registered in May 2007 through Gandi SAS. An established domain carries more trust with email providers and search engines.

CAA records allow only digicert.com, comodoca.com, pki.goog and globalsign.com to issue certificates for crunchbase.com, so a mis-issued certificate from anyone else is refused.

crunchbase.com is registered until May 2027.

On a phone, the first screen shows a clear next step: “Start Free Trial” and “Talk to Sales”.

The homepage has 10 calls to action, for example “Contact Us”, “Pricing” and “Start Free Trial”.

3 short forms (4 fields at most) are right on the homepage, asking for an email.

Social proof on the homepage: 4 testimonial or review blocks, a star rating, 15 trust badges and “80M+ users”.

Analytics detected: Google Tag Manager.

DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 mx include:sendgrid.net include:_spf.google.com include:mail.zendesk.com include:spf.mandrillapp.com include:mkt…”.

A DKIM key is published (selector “google”, “s1” and “s2”), so receivers can verify mail really came from you.

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

No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).