sociallyin.com website review

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

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

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

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

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

Google CDN costs a phone 402 ms of main-thread work and 730 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 373 ms of main-thread work and 531 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.

Hubspot costs a phone 375 ms of main-thread work and 364 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

Facebook costs a phone 251 ms of main-thread work and 252 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.

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

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

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

2 images could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

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 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

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

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

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

Your homepage downloads 11.8 MB in 113 requests on a phone: media 8.7 MB (2), scripts 2.3 MB (53) and other files 371 KiB (23). Under 2 MB keeps phones on slow connections fast.

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

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

1 dropdown has no label.

ARIA input fields must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

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

ARIA toggle fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

1 element hidden from screen readers can still receive keyboard focus.

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

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

9 links have no real href, so search engines can't follow them.

The homepage links to 62 pages on sociallyin.com and 7 external pages.

We fetched 15 pages linked from your homepage (of 42 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”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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

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 1,139 words of visible text.

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

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