reclinersindia.com website review

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

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

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

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

Google CDN costs a phone 2.4 s of main-thread work and 3.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.

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

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

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

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

8 third-party services load with your homepage (Google CDN, exei.ai and Other Google APIs/SDKs and others), adding 5.8 MB and 4.4 s of main-thread time.

exei.ai costs a phone 798 ms of main-thread work and 1.2 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.

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

Other Google APIs/SDKs costs a phone 451 ms of main-thread work and 133 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.

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

Clarity costs a phone 325 ms of main-thread work and 34 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 50 ms).

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

Desktop scores 42 but mobile only 11. A gap that wide usually means heavy scripts and images that hit phones hardest.

6 KiB could be saved by minifying JavaScript.

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.

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 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 63.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “best recliner manufacturer in Delhi (NCR), recliner sofa, r…”.

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

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

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

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

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

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

Your homepage downloads 13.6 MB in 418 requests on a phone: scripts 5.4 MB (129), images 4.8 MB (90) and other files 1.7 MB (77). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

4 images (2.7 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 3.87 g of CO₂e: 464.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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.

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

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

autocomplete attributes are not used correctly (2 elements).

Your title is 97 characters, so Google will cut it off around 60: “Best Recliner Manufacturer in India | Luxury Recliner Chair, Sofa | Motion Furniture Manu…”.

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

The homepage links to 262 pages on reclinersindia.com and 53 external pages.

There is no https://www.reclinersindia.com/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.

https://www.reclinersindia.com/cart-3 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.reclinersindia.com/wishlist and https://www.reclinersindia.com/cart-3 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.reclinersindia.com/wishlist, https://www.reclinersindia.com/cart-3, https://www.reclinersindia.com/product-category/cinema-seats-sliders, https://www.reclinersindia.com/product-category/cinema-recliner-home-theater-recliners, https://www.reclinersindia.com/product-category/recliner-smart-bed and https://www.reclinersindia.com/product-category/work-from-home-recliners and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.reclinersindia.com/wishlist and https://www.reclinersindia.com/cart-3 took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “pintrk is not defined”.

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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,328 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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