humankindorders.com website review

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

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

Unpkg costs a phone 1.2 s of main-thread work and 688 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

4 third-party services load with your homepage (Unpkg, Google Tag Manager and JSDelivr CDN and others), adding 864 KiB and 1.3 s of main-thread time.

3 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

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

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

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

10 KiB could be saved by minifying CSS.

10 KiB could be saved by minifying JavaScript.

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

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 5.3 s on a phone. Good is under 1.8 s.

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Odeko is the distributor designed with your shop in mind — …”. Most of its time is element render delay (2.3 s).

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

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

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

Visually, the page fills in at 5.6 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.

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

Your homepage downloads 7.6 MB in 40 requests on a phone: media 5.9 MB (4), scripts 880 KiB (9) and images 377 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example getty-images-hZsk4tmPE84-unsplash-4a8e22ee.webp at 1,400 px wide, shown at 340 px. Resized copies would save about 53 KiB.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

A phone browser shows 873 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

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

odeko.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

humankindorders.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

humankindorders.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

humankindorders.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

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.

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