side.com website review

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

8 third-party services load with your homepage (clym-sdk.net, Vidyard and Google Tag Manager and others), adding 11.0 MB and 1.4 s of main-thread time.

Vidyard costs a phone 410 ms of main-thread work and 9.9 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.

Your mobile performance score is 59 (desktop: 88). Pages that score under 90 lose visitors before the first paint.

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

clym-sdk.net costs a phone 422 ms of main-thread work and 567 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.

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

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

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

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

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

28 KiB JavaScript is shipped twice across bundles.

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

Desktop scores 88 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Side Homepage Video Poster”.

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

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

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

The layout shifts by 0.172 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your homepage downloads 11.6 MB in 175 requests on a phone: media 4.6 MB (1), images 4.6 MB (22) and scripts 2.1 MB (101). Under 2 MB keeps phones on slow connections fast.

1 image (31 KiB) is 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.

1 image further down the page (31 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.27 g of CO₂e: 392.9 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”.

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

15 elements have a tabindex above 0, which scrambles the keyboard order.

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

2 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

31 visible links have no text or label, so screen readers cannot say where they go.

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

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

The homepage links to 120 pages on side.com and 9 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), Claude search (Claude-SearchBot) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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.

/about/press/sides-partner-success-organization-named-team-of-the-year-by-customer-success-collective is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/become-a-partner/high-potential-agents, /about/press/sides-partner-success-organization-named-team-of-the-year-by-customer-success-collective and /success-stories/unbelievable-growth-unlimited-potential have no meta description, so Google writes the search snippet from whatever text it finds.

/become-a-partner has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your longest form asks for 13 fields (11 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar, HubSpot and LinkedIn Insight and 1 more (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 7 cookies (measured from a US location before any click).

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