kaloud.com website review

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.

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

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

8 third-party services load with your homepage (zapier.com, route.com and rebuyengine.com and others), adding 3.5 MB and 1.7 s of main-thread time.

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

zapier.com costs a phone 600 ms of main-thread work and 1.4 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.

9 images could be 304 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.

route.com costs a phone 388 ms of main-thread work and 545 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.

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

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

rebuyengine.com costs a phone 257 ms of main-thread work and 683 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.

fwcdn3.com costs a phone 92 ms of main-thread work and 469 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.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

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

45 KiB could be saved by minifying JavaScript.

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

2 KiB JavaScript is shipped twice across bundles.

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 21.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two icons. One Kaloud standard.”.

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

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

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

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

For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 123 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.6 MB in 430 requests on a phone: scripts 3.4 MB (212), images 1.4 MB (22) and other files 969 KiB (164). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example [email protected] at 3,072 px wide, shown at 307 px. Resized copies would save about 139 KiB.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 66 characters, so Google will cut it off around 60: “Kaloud: Lotus HMDs, Premium Hookahs and Shisha Bowls – Kaloud Inc.”.

The homepage links to 74 pages on kaloud.com and 5 external pages.

https://kaloud.com/collections/new-arrivals, https://kaloud.com/collections/kaloud-krysalis, https://kaloud.com/collections/shop-all and https://kaloud.com/products/gift-card have no <h1> headline, so visitors and search engines get no clear main topic.

https://kaloud.com/collections/new-arrivals, https://kaloud.com/collections/hookah-sets, https://kaloud.com/collections/kaloud-krysalis, https://kaloud.com/collections/kaloud-samsaris and https://kaloud.com/collections/shop-all 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 31 found) and read each the way a search engine does.

9 of 42 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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 4 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 27 cookies (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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.