kurlon.com website review

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

22 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Shopify costs a phone 7 ms of main-thread work and 322 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 third-party services load with your homepage (gokwik.co, Google Tag Manager and Shopify and others), adding 756 KiB and 171 ms of main-thread time.

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

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

About 106 KiB of JavaScript is downloaded but never used on this page.

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

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.

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

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

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

Real visitors wait 866 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 4.1 MB in 135 requests on a phone: images 2.9 MB (70), scripts 727 KiB (31) and fonts 313 KiB (8). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example shutterstock_1740104054_957d94ec-e025-4e79-8799-abdd69ab1cb0 at 5,760 px wide, shown at 360 px. Resized copies would save about 1.5 MB.

shutterstock_1740104054_957d94ec-e025-4e79-8799-abdd69ab1cb0 weighs 503 KiB. On a phone connection a single image that size takes seconds.

Artboard_2.png 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).

13 images (864 KiB) 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.17 g of CO₂e: 140.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“” and “Discover Comfort with Kurlon – India's Premier Ma…”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: potentialAction.target is not an absolute URL ("{search_term_string}")”.

2 links have no real href, so search engines can't follow them.

The homepage links to 205 pages on kurlon.com and 16 external pages.

https://kurlon.com/collections/additional-discounted-products and https://kurlon.com/pages/bulk-order-new have no meta description, so Google writes the search snippet from whatever text it finds.

https://kurlon.com/collections/additional-discounted-products, https://kurlon.com/pages/wishlist, https://kurlon.com/pages/bulk-order-new and https://kurlon.com/collections/mattresses have no <h1> headline, so visitors and search engines get no clear main topic.

https://kurlon.com/pages/wishlist and https://kurlon.com/pages/bulk-order-new 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 72 found) and read each the way a search engine does.

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

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

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