unreasonablegroup.com website review

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

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

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

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

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

cloudfront.net costs a phone 446 ms of main-thread work and 225 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.

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

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

6 third-party services load with your homepage (cloudfront.net, Cloudflare and Fathom Analytics and others), adding 513 KiB and 465 ms of main-thread time.

Polyfills for old browsers add 68 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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.

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

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

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text ““The reasonable person adapts themselves to the world; the …”. Most of its time is element render delay (2.4 s).

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

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

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

Your homepage downloads 2.9 MB in 65 requests on a phone: images 1.8 MB (34), scripts 542 KiB (6) and other files 430 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example hunter-lovins-5ec30705e6ba0edc40d5724cf380df6f619cc4f3bdb466 at 600 px wide, shown at 195 px. Resized copies would save about 3 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.3 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.

Some list items are not inside a list.

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

1 link inside paragraphs relies on colour alone to stand out.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 18 characters: “Unreasonable Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 73 pages on unreasonablegroup.com and 5 external pages.

https://unreasonablegroup.com/investors and https://unreasonablegroup.com/collective all use the title “Unreasonable Investors”. Search engines can't tell which page to show for a search, so each competes with the others.

https://unreasonablegroup.com/ventures, https://unreasonablegroup.com/mentors, https://unreasonablegroup.com/fellowship, https://unreasonablegroup.com/team, https://unreasonablegroup.com/press and https://unreasonablegroup.com/connect use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://unreasonablegroup.com/collective, whose canonical is https://unreasonablegroup.com/investors. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://unreasonablegroup.com/ventures, https://unreasonablegroup.com/mentors, https://unreasonablegroup.com/fellowship, https://unreasonablegroup.com/investors, https://unreasonablegroup.com/partners and https://unreasonablegroup.com/team and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: window.navigation.addEventListener is not a function”.

Large scripts ship without source maps.

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

Opening the homepage sets 1 cookie (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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.