joinheard.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, elfsightcdn.com and website-files.com and others), adding 11.6 MB and 1.2 s of main-thread time.

website-files.com costs a phone 212 ms of main-thread work and 10.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.

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

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

elfsightcdn.com costs a phone 213 ms of main-thread work and 322 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.

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

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

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

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.

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

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

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

Your largest element takes 26.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Real visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 135 ms to 258 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 12.0 MB in 127 requests on a phone: media 7.9 MB (2), scripts 2.1 MB (60) and images 1.8 MB (15). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example 6aa1e08a8842a0e15fe8a89d_heard-daily_1.webp at 1,064 px wide, shown at 262 px. Resized copies would save about 754 KiB.

6 images further down the page (1.6 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 3.41 g of CO₂e: 408.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

9 tap targets are too small or too close together to hit reliably with a finger.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 33 elements on the page fail this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Structured data found (FAQPage, Organization, SoftwareApplication and WebPage) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

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

The homepage links to 88 pages on joinheard.com and 20 external pages.

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

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

2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "inherit".”.

1 link from your homepage to your own site is broken, for example https://www.joinheard.com/welcome-form-old (404).

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

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.

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

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

Your longest form asks for 15 fields (1 required). Every extra field lowers completion.

The homepage carries about 934 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be joinheard.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Heap and 5 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 26 cookies, 1 of them by other companies (measured from a US location before any click).

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