softude.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and jQuery CDN and others), adding 1.4 MB and 918 ms of main-thread time.

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

About 563 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

About 92 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

Google Tag Manager costs a phone 437 ms of main-thread work and 680 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 2.9 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

kommunicate.io costs a phone 94 ms of main-thread work and 497 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

1 image could be 38 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

2 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We Innovate. Let's Talk”. Most of its time is element render delay (3.2 s).

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

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

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

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

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

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

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

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

Your homepage downloads 9.9 MB in 149 requests on a phone: media 7.4 MB (5), scripts 1.5 MB (50) and fonts 531 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

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

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

8 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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.

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

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

The homepage links to 92 pages on softude.com and 11 external pages.

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

5 of 17 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 “Failed to load resource: net::ERR_FAILED”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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 homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Clarity (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 23 cookies, 2 of them by other companies (measured from a US location before any click).

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