maxoxo.me website review

10 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.0 s faster on a phone.

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

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

7 third-party services load with your homepage (Stripe, JSDelivr CDN and posthog.com and others), adding 6.2 MB and 1.2 s of main-thread time.

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

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

Stripe costs a phone 510 ms of main-thread work and 281 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.

JSDelivr CDN costs a phone 385 ms of main-thread work and 1.1 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.

maxos.dev costs a phone 0 ms of main-thread work and 4.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.

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

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

rsms.me costs a phone 1 ms of main-thread work and 338 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.

17 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “邮件订阅 首页 产品 读书 文章 关于 maxOS Eventually everything connects - …”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 6.2 MB in 59 requests on a phone: images 4.3 MB (24), scripts 1.0 MB (16) and other files 555 KiB (9). Under 2 MB keeps phones on slow connections fast.

genius-makers.png weighs 830 KiB. On a phone connection a single image that size takes seconds.

11 images are downloaded at several times the size a phone draws them, for example genius-makers.png at 600 px wide, shown at 180 px. Resized copies would save about 784 KiB.

17 images (2.8 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.

18 images further down the page (2.7 MB) 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 1.76 g of CO₂e: 211.6 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”.

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

Alternative text of images should not be repeated as text: 22 elements on the page fail this check, rated minor by axe-core.

Your meta description is only 56 characters: “Eventually everything connects - people, ideas, objects.”. 70 to 160 characters is enough to sell the click.

The homepage links to 74 pages on maxoxo.me and 0 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 https://maxoxo.me/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://maxoxo.me/tag/design, https://maxoxo.me/tag/books, https://maxoxo.me/tag/articles, https://maxoxo.me/about, https://maxoxo.me/page/2 and https://maxoxo.me/thinking-in-bets and 9 others use the same meta description. A description written for each page earns more clicks.

https://maxoxo.me/tag/design, https://maxoxo.me/tag/books, https://maxoxo.me/tag/articles, https://maxoxo.me/about, https://maxoxo.me/page/2 and https://maxoxo.me/antifragile-things-that-gain-from-disorder and 2 others 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 54 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.

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

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