kognitiv.com website review

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

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

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

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

8 third-party services load with your homepage (Hubspot, website-files.com and Google Tag Manager and others), adding 2.2 MB and 433 ms of main-thread time.

website-files.com costs a phone 149 ms of main-thread work and 1.2 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.

Hubspot costs a phone 191 ms of main-thread work and 513 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 227 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. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 2.4 MB in 91 requests on a phone: scripts 1.1 MB (22), images 926 KiB (43) and fonts 236 KiB (8). Under 2 MB keeps phones on slow connections fast.

6824a959da3c7880abe07479_Kognitiv_Cap_WebsiteHeader_Graphic is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images (103 KiB) are 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.

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

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: 23 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.

1 visible link has no text or label, so screen readers cannot say where it goes.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 73 pages on kognitiv.com and 2 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.kognitiv.com/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.

https://www.kognitiv.com/company/leadership declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.kognitiv.com/company/leadership all use the title “Customer Loyalty Platform for Marketing & Management”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kognitiv.com/articles-insights/ultimate-loyalty-101-guide, https://www.kognitiv.com/articles-insights/20-loyalty-kpis-guide and https://www.kognitiv.com/articles-insights/loyalty-program-roi-calculator have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kognitiv.com/resources/blog and https://www.kognitiv.com/resources/resources use the same meta description. A description written for each page earns more clicks.

https://www.kognitiv.com/articles-insights/ultimate-loyalty-101-guide, https://www.kognitiv.com/articles-insights/20-loyalty-kpis-guide and https://www.kognitiv.com/articles-insights/loyalty-program-roi-calculator have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 of 8 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 “Access to XMLHttpRequest at 'https://i.tryinteract.com/promotions/style.css' from origin 'https://www.kognitiv.com' has…”.

Large scripts ship without source maps.

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

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

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