raptive.com website review

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Facebook and consentmanager.net and others), adding 711 KiB and 580 ms of main-thread time.

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

About 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Polyfills for old browsers add 13 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.

2 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “$Building$ what’s next in media”.

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

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

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

Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

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

5 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 135 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

3 images (282 KiB) 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.

2 images further down the page (164 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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 (h1 → h4), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“Building what’s next in media” and “Building what’s next in media”). One clear main headline is easier for people and search engines.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 56 pages on raptive.com and 15 external pages.

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

robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://raptive.com/media-companies and https://raptive.com/enterprise all use the title “Media Companies — Raptive”. Search engines can't tell which page to show for a search, so each competes with the others.

https://raptive.com/creators, https://raptive.com/creator-levels, https://raptive.com/community, https://raptive.com/advertisers, https://raptive.com/team and https://raptive.com/newsroom and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://raptive.com/media-companies and https://raptive.com/enterprise use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://raptive.com/community, whose canonical is https://raptive.com/community/creators. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 error was logged to the browser console while the page loaded, for example “Error: [Ashby] Could not find container for iframe. Container ID = ashby_embed”.

Large scripts ship without source maps.

Social proof on the homepage: 52 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

Opening the homepage sets 7 cookies (measured from a US location before any click).

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