humaninterest.com website review

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

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

8 third-party services load with your homepage (hsappstatic.net, Google CDN and Google Tag Manager and others), adding 2.1 MB and 1.1 s of main-thread time.

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

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

hsappstatic.net costs a phone 293 ms of main-thread work and 711 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.

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

Google CDN costs a phone 269 ms of main-thread work and 742 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.

Google Tag Manager costs a phone 185 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.

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

About 95 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.

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

Polyfills for old browsers add 58 KiB JavaScript that modern phones do not need.

52 KiB JavaScript is shipped twice across bundles.

36 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Give your employees the highest-rated 401(k)”.

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

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

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

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

Your homepage downloads 3.8 MB in 134 requests on a phone: scripts 2.9 MB (69), other files 396 KiB (29) and fonts 191 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

The homepage links to 77 pages on humaninterest.com and 16 external pages.

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.

/payrolls and /partners use the same meta description. A description written for each page earns more clicks.

/features/audit-relief and /reviews have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=13017638&Ver=2&mid=ada63ca9-1db7-4a16-98c8-436a587bdb60&bo=1&sid=6d464c20d68311f1a3fc1b61f0be6e61&vid=6d4691e0d68311f197e6a17d991003fe&vids=1&msclkid=N&pi=918639831&lg.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=924632898.1793599538&gtm=45be6at0h2v9101040706za208zd91010…”.

Chrome logged issues while loading the page (“Cookie”).

1 link to other sites is dead, for example https://www.dalbar.com/Awards/ServiceAwardWinners (404).

X-XSS-Protection is set to “1”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

humaninterest.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

humaninterest.com 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.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,715 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 Amplitude, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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