royaletouche.com website review

About 685 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

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

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

Google Tag Manager costs a phone 1.0 s of main-thread work and 733 KiB 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.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.3 MB and 1.9 s of main-thread time.

19 images could be 858 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

Facebook costs a phone 576 ms of main-thread work and 372 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 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

35 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 30.7 MB in 270 requests on a phone: media 18.7 MB (3), images 9.2 MB (92) and scripts 2.1 MB (88). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.2 MB together. On a phone connection a single image that size takes seconds.

40 images (8.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.

8 images are downloaded at several times the size a phone draws them, for example CRYSTAL-Z-CV-2228-A4-600x775.jpg at 600 px wide, shown at 133 px. Resized copies would save about 279 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 8.70 g of CO₂e: 1044.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.

1 button has no accessible name, so screen readers announce just “button”.

[role="img"] and [role="image"] elements must have alternative text: 15 elements on the page fail this check, rated serious by axe-core.

2 elements hidden from screen readers can still receive keyboard focus.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

12 images have 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.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is 81 characters, so Google will cut it off around 60: “Royale Touche Laminates: Best Decorative Laminate Brand and Manufacturer in India”.

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

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

The homepage links to 455 pages on royaletouche.com and 38 external pages.

https://royaletouche.com/about-us has no <h1> headline, so visitors and search engines get no clear main topic.

https://royaletouche.com/design-ideas/kitchen-cabinets-design, https://royaletouche.com/design-ideas/bedroom-design and https://royaletouche.com/design-ideas/living-room-design took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136028415&tm=gtm002&Ver=2&mid=954ac662-0779-4825-be0c-d7960014fe78&bo=1&sid=556a54d0ceb911f18079259872cfd9fa&vid=556a6b80ceb911f19db00df4d2fc012b&vids=1&msclkid=N&pi=9.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

A form field blocks pasting, which frustrates password managers and people on phones.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Your longest form asks for 8 fields (4 required). Every extra field lowers completion.

The homepage shows no opening hours. If customers visit or call, show when.

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

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 571 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 2 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 20 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.