maven.co website review

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

Your mobile performance score is 16 (desktop: 41). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.6 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

7 third-party services load with your homepage (elfsightcdn.com, Google Tag Manager and ZenDesk and others), adding 1.3 MB and 1.4 s of main-thread time.

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

elfsightcdn.com costs a phone 722 ms of main-thread work and 466 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 704 KiB of JavaScript is downloaded but never used on this page.

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

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

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

ZenDesk costs a phone 321 ms of main-thread work and 413 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.

The page has 1,930 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

6 KiB could be saved by minifying CSS.

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.

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.

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

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

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Human Intelligence. On Demand. At Scale. Discover, acquire,…”.

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

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

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

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

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

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

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

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

Your homepage downloads 2.7 MB in 178 requests on a phone: scripts 1.6 MB (69), images 383 KiB (21) and fonts 340 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“Home” and “Maven exists to make that possible.”). One clear main headline is easier for people and search engines.

Structured data found (Article, ImageObject, Organization and Person) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("https:/www.facebook.com/MavenRes")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 75 pages on maven.co and 11 external pages.

Your Organization JSON-LD is missing url, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/expert-interviews and /online-surveys use the same meta description. A description written for each page earns more clicks.

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

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

2 images are served at too low a resolution for sharp phone screens.

2 links from your homepage to your own site are broken, for example https://www.maven.co/aimr (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example http://maven.co/project.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

maven.co has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Social proof on the homepage: 18 customer or partner logos. 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.

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.

The homepage carries about 469 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 15 cookies (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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.