redpoint.com website review

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

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

10 images could be 361 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

5 third-party services load with your homepage (termly.io, Google Fonts and sanity.io and others), adding 2.5 MB and 70 ms of main-thread time.

sanity.io costs a phone 0 ms of main-thread work and 2.2 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.

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

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

18 KiB JavaScript is shipped twice across bundles.

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

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.

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

Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use essential cookies to make our site work. With your c…”.

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

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

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

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

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

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

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

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

Your homepage downloads 3.9 MB in 76 requests on a phone: images 2.2 MB (38), scripts 1.3 MB (19) and fonts 180 KiB (6). Under 2 MB keeps phones on slow connections fast.

9 images (1.6 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.

1a157f0903e253b699be572d1ad6501563007722-892x1002.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

5 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

The homepage links to 38 pages on redpoint.com and 26 external pages.

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

https://www.redpoint.com/reports/the-infrared-report-2026 has no <title>, so Google invents the link text in results.

https://www.redpoint.com/reports/the-infrared-report-2026 has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.redpoint.com/companies, https://www.redpoint.com/content-hub/written/a-step-towards-predicting-the-future-our-investment-in-aaru-, https://www.redpoint.com/content-hub/video/leading-flora-s-usd42m-series-a-the-ai-native-creative-platform-rethinking-how-design-works, https://www.redpoint.com/content-hub/video/sam-altman-talks-gpt-4o-and-predicts-the-future-of-ai, https://www.redpoint.com/content-hub/category/ai and https://www.redpoint.com/content-hub/category/funding-news and 1 other use the same meta description. A description written for each page earns more clicks.

https://www.redpoint.com/companies, https://www.redpoint.com/content-hub, https://www.redpoint.com/reports/the-infrared-report-2026, https://www.redpoint.com/content-hub/category/ai, https://www.redpoint.com/content-hub/category/funding-news and https://www.redpoint.com/content-hub/category/consumer have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.redpoint.com/companies, https://www.redpoint.com/content-hub/category/ai, https://www.redpoint.com/content-hub/category/funding-news and https://www.redpoint.com/content-hub/category/consumer 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.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 280 words of visible text.

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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