kando.eco website review

YouTube costs a phone 2.8 s of main-thread work and 4.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Calendly costs a phone 1.3 s of main-thread work and 2.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (YouTube, Calendly and Google Tag Manager and others), adding 9.2 MB and 5.6 s of main-thread time.

About 4.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 920 ms faster on a phone.

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

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

Facebook costs a phone 269 ms of main-thread work and 210 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.

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

About 96 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 23 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.

3 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Introducing Kando’s Solution: A comprehensive wastewater in…”. Most of its time is element render delay (3.1 s).

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

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

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 10.4 MB in 245 requests on a phone: scripts 7.8 MB (116), stylesheets 1.6 MB (31) and fonts 468 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 43 pages on kando.eco and 12 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.kando.eco/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.

Your homepage links to https://www.kando.eco/www.kando.eco/solution, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.kando.eco/contact-kando-wastewater-intelligence-solutions and https://www.kando.eco/contact-us all use the title “Contact Us Kando”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kando.eco/people, https://www.kando.eco/clients, https://www.kando.eco/partners, https://www.kando.eco/blog, https://www.kando.eco/media and https://www.kando.eco/events and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kando.eco/contact-kando-wastewater-intelligence-solutions and https://www.kando.eco/contact-us use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.kando.eco/contact-us, whose canonical is https://www.kando.eco/contact-kando-wastewater-intelligence-solutions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.kando.eco/about-kando-wastewater-intelligence-company and https://www.kando.eco/people have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kando.eco/contact-kando-wastewater-intelligence-solutions and https://www.kando.eco/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Invalid form id provided: ”.

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

Social proof on the homepage: 15 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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