kotn.supply website review

4 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 18.1 s faster on a phone.

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

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

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

5 third-party services load with your homepage (envato-static.com, Cloudflare and Bing Ads and others), adding 4.9 MB and 74 ms of main-thread time.

kilat.digital costs a phone 0 ms of main-thread work and 4.6 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 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 330 ms faster on a phone.

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

9 KiB could be saved by minifying CSS.

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 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Popup Banner”.

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

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

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

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

2 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.

3 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 4.9 MB in 24 requests on a phone: images 4.7 MB (9), scripts 88 KiB (9) and stylesheets 77 KiB (3). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example b72352e7ac87f712678ab18786ee0b39.gif at 900 px wide, shown at 120 px. Resized copies would save about 2.6 MB.

3 images (4.6 MB) 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 1.39 g of CO₂e: 167.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is 80 characters, so Google will cut it off around 60: “BANDARBOLA855 ♨️ PREDIKAT BANDAR SLOT GACOR 5000 TERPERCAYA LAYANAN TERBAIK 2026”.

There are 3 <h1> headlines (“BANDARBOLA855 ♨️ PREDIKAT BANDAR SLOT GACOR 5000 …”, “BANDARBOLA855 ♨️ PREDIKAT BANDAR SLOT GACOR 5000 …” and “BANDARBOLA855 ♨️ PREDIKAT BANDAR SLOT GACOR 5000 …”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 151 pages on kotn.supply and 46 external pages.

There is no https://slothunter-dutch.nl/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

Your homepage links to https://slothunter-dutch.nl/nl-nl1//licenses/standard and https://slothunter-dutch.nl/item_support/what_is_item_support/8988002, which answer with an error. Visitors hit a dead end and search engines drop them.

/ and https://slothunter-dutch.nl/nl-nl1 all use the title “BANDARBOLA855 ♨️ PREDIKAT BANDAR SLOT GACOR 5000 TERPERCAYA LAYANAN T…”. Search engines can't tell which page to show for a search, so each competes with the others.

We fetched 3 pages linked from your homepage and read each the way a search engine does.

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

3 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute viewBox: Unexpected end of attribute. Expected number, "0 0 1414".”.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Before a visitor clicks anything, the page loads Microsoft Ads (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 1 cookie, 1 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.