notablecap.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, px-cloud.net and website-files.com and others), adding 9.9 MB and 653 ms of main-thread time.

website-files.com costs a phone 154 ms of main-thread work and 9.3 MB 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.

Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

About 275 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 570 ms faster on a phone.

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

5 images could be 207 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

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

The layout shifts by 0.28 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We Back Founders Who Are Notable.”. Most of its time is element render delay (1.4 s).

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

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

Your homepage downloads 10.2 MB in 100 requests on a phone: media 8.6 MB (10), scripts 759 KiB (47) and fonts 536 KiB (14). Under 2 MB keeps phones on slow connections fast.

1 image (72 KiB) is 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your meta description is only 52 characters: “We invest in notable founders with global ambitions.”. 70 to 160 characters is enough to sell the click.

The homepage links to 41 pages on notablecap.com and 16 external pages.

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.

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

/companies, /blog/the-rise-of-workload-clouds, /blog/garrett-lord-went-all-in-on-handshake-ai-now-its-at-nearly-1b, /blog/from-exit-to-restart-how-torqs-repeat-founders-are-reimagining-the-future-of-security-operations and /blog/how-quince-built-a-better-retail-model-to-democratize-quality have no meta description, so Google writes the search snippet from whatever text it finds.

/approach and /n1 use the same meta description. A description written for each page earns more clicks.

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

19 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,076 words of visible text.

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.

Opening the homepage sets 6 cookies, 4 of them by other companies (measured from a US location before any click).

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.

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