kenect.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Wistia and website-files.com and others), adding 2.6 MB and 1.4 s of main-thread time.

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

Wistia costs a phone 389 ms of main-thread work and 1.1 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.

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

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

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

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

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

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

7 KiB could be saved by minifying CSS.

4 images could be 73 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.

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

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

The page becomes fully interactive after 13.9 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 466 ms in total while the page loads. Good is under 200 ms.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.9 MB in 103 requests on a phone: scripts 1.5 MB (35), media 793 KiB (3) and fonts 299 KiB (14). Under 2 MB keeps phones on slow connections fast.

699ddd25419f47c072fd769c_date-expand-thumbnail-p-500.webp 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).

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Structured data found (Corporation and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: url is not an absolute URL ("/")”.

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

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

The homepage links to 89 pages on kenect.com and 11 external pages.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187266841&tm=gtm002&Ver=2&mid=dba524bb-b162-4092-b6c5-0155a7b2de63&bo=1&sid=cd0baa00d8a111f182bcdf8408517ef1&vid=cd0bd160d8a111f1b97c45a606aedd50&vids=1&msclkid=N&gtm_.

1 error was logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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