joinform.com website review

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

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

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

8 third-party services load with your homepage (Klaviyo, Clarity and JSDelivr CDN and others), adding 1.4 MB and 618 ms of main-thread time.

About 503 KiB of JavaScript is downloaded but never used on this page.

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

Klaviyo costs a phone 265 ms of main-thread work and 671 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.

azurefd.net costs a phone 25 ms of main-thread work and 320 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.

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

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

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

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

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

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

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

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

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “50% Off Annual Memberships”.

Visually, the page fills in at 4.3 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.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 421 requests on a phone: scripts 1.6 MB (134), other files 1.4 MB (259) and images 246 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

6 buttons have no accessible name, so screen readers announce just “button”.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

Your meta description is 227 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 61 pages on joinform.com and 78 external pages.

https://joinform.com/collections/shopform, https://joinform.com/pages/programs, https://joinform.com/pages/mindfulness, https://joinform.com/pages/form-community, https://joinform.com/pages/about-us and https://joinform.com/pages/shop-by-collection and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://joinform.com/products/core-leggings-crush and https://joinform.com/products/capri-leggings-espresso use the same meta description. A description written for each page earns more clicks.

https://joinform.com/collections/shopform, https://joinform.com/pages/programs, https://joinform.com/pages/mindfulness, https://joinform.com/pages/form-community and https://joinform.com/pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 17 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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.

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