clearpani.com website review

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

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

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

About 480 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.

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

Your mobile performance score is 38 (desktop: 30). 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, ContentSquare and Facebook and others), adding 1.2 MB and 1.0 s of main-thread time.

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

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

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

Polyfills for old browsers add 12 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.

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.

Real visitors wait 10.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 10.2 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 78.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hrithik Roshan holding a CLEAR bottle beside the Pani Ho To…”.

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

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

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

Real visitors wait 353 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 13.3 MB in 88 requests on a phone: images 6.5 MB (35), scripts 6.1 MB (18) and stylesheets 510 KiB (3). Under 2 MB keeps phones on slow connections fast.

5 images weigh 5.5 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example 3.png at 1,669 px wide, shown at 248 px. Resized copies would save about 4.3 MB.

15 images (6.4 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.

9 images further down the page (547 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

A phone browser shows 674 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97237688&tm=gtm002&Ver=2&mid=840d0117-5c9f-416d-8c33-b5df61e946d6&bo=1&sid=b7d91c30cfee11f18494358f8c5840d8&vid=b7d941b0cfee11f198e0edaf482a3ee5&vids=1&msclkid=N&gtm_t.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

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

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