mindit.io website review

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

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Cookiebot and lfeeder.com and others), adding 786 KiB and 1.3 s of main-thread time.

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

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

Cookiebot costs a phone 447 ms of main-thread work and 169 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.

14 long tasks block the main thread while loading, the longest for 254 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.

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.

Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

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

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

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

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

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

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

Your homepage downloads 2.7 MB in 220 requests on a phone: scripts 1.1 MB (67), fonts 802 KiB (9) and images 548 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

14 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: 53 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

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

The homepage links to 150 pages on mindit.io and 6 external pages.

/real-estate, /telco, /enterprise-applications, /product-engineering and /data-analytics took over 3 s to send their HTML from our server.

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

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

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

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.

mindit.io 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.

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

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

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

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 Google Ads, Google Analytics, Google Tag Manager, HubSpot and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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