personetics.com website review

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

A phone's processor spends 6.7 s on main-thread work while loading, 3.6 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.9 MB and 1.6 s of main-thread time.

About 1.4 MB of JavaScript is downloaded but never used on this page.

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

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

Google CDN costs a phone 723 ms of main-thread work and 1.5 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.

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

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

Hubspot costs a phone 324 ms of main-thread work and 312 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 306 ms of main-thread work and 341 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.

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

Vimeo costs a phone 40 ms of main-thread work and 514 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.

30 KiB could be saved by minifying JavaScript.

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

15 KiB could be saved by minifying CSS.

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

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 7.6 MB in 358 requests on a phone: images 3.0 MB (241), scripts 2.8 MB (46) and other files 715 KiB (15). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (164 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 dropdown has no label.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

All page content should be contained by landmarks: 8 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.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is 77 characters, so Google will cut it off around 60: “Cognitive Banking | Money Management for Banks | AI Banking | Personetics.com”.

There are 2 <h1> headlines (“The Cognitive Banking Platform” and “One platform. One shared financial context. Stand…”). One clear main headline is easier for people and search engines.

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

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

Structured data found (ImageObject, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://cognitivebanking.ai/)”.

Your hreflang tags are invalid, so Google may show the wrong language version.

The homepage links to 190 pages on personetics.com and 6 external pages.

There is no https://personetics.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://personetics.com/personetics-partners is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://personetics.com/atomic-partnership, https://personetics.com/fiserv-partnership and https://personetics.com/solutions/q2 have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: e.indexOf is not a function”.

3 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, LinkedIn Insight and Meta Pixel (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, 2 of them by other companies (measured from a US location before any click).

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