Website review, no card needed
cera-india.com website review
Visit site (opens in a new tab)Reviewed 27 October 202652 issues · 90 checks
This review found 52 issues worth fixing on cera-india.com, 20 of them high impact, across 90 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 118 ms |
| May 16, 2026 | 118 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 132 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 152 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 159 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 184 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 169 ms |
| Oct 3, 2026 | 158 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 148 ms |
| Oct 24, 2026 | 156 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.4 s
2.7 s
4.1 s
5.5 s
6.8 s
8.2 s
9.6 s
10.9 s
Speed
Render-blocking requests
2.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Use efficient cache lifetimes
1.4 s · 436 KiB12 files are served with short cache lifetimes, so returning visitors download them again (436 KiB).
Reduce unused JavaScript
1.2 s · 569 KiBAbout 569 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Font display
1.4 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 48). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
300 ms · 2.8 MB16 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.1 MB and 975 ms of main-thread time.
Google Tag Manager adds 658 ms
658 msGoogle Tag Manager costs a phone 658 ms of main-thread work and 729 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.
Reduce unused CSS
600 ms · 128 KiBAbout 128 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 501 ms. During a long task the page ignores taps.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 191 ms
191 msFacebook costs a phone 191 ms of main-thread work and 295 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.
1,559 HTML elements
The page has 1,559 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 248 ms
248 msYour server sent the HTML in 248 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 4.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.6 s
2.6 sReal visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 12.0 s
12.0 sYour largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Card image”.
Time to Interactive: 23.1 s
23.1 sThe page becomes fully interactive after 23.1 s. Good is under 3.8 s.
Speed Index: 13.2 s
13.2 sVisually, the page fills in at 13.2 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 118 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 497 ms
497 msScripts block taps and scrolling for 497 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 172 ms
172 msReal visitors wait 172 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.084
0.084The layout barely moves while loading (CLS 0.084, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 100 requests
6.0 MBYour homepage downloads 6.0 MB in 100 requests on a phone: images 4.4 MB (47), scripts 1.4 MB (19) and fonts 133 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Factory-top-image.jpg weighs 1.8 MB. On a phone connection a single image that size takes seconds.
21 images in older formats
21 images (4.1 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.
12 images below the first screen load straight away
12 images further down the page (3.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 205.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (59 elements)
All page content should be contained by landmarks: 59 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h3 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (78 characters)
Your title is 78 characters, so Google will cut it off around 60: “Sanitaryware, Faucets and Tiles Manufacturers - Bathroom & Kitchen accessories”.
Meta description is long (218 characters)
Your meta description is 218 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
284 internal links, 7 external
The homepage links to 284 pages on cera-india.com and 7 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Exceptionally Designed Products For Your Home”.
Canonical URL set
The canonical URL is https://www.cera-india.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.cera-india.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.cera-india.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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,262 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.cera-india.com/brand/isvea declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.cera-india.com/brand/isvea all use the title “Sanitaryware, Faucets and Tiles Manufacturers - Bathroom & Kitchen ac…”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://www.cera-india.com/brand/cera-luxe, https://www.cera-india.com/brand/polipluz, https://www.cera-india.com/cerastylestudio, https://www.cera-india.com/dealer and https://www.cera-india.com/international-sales have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.cera-india.com/brand/cera-luxe, https://www.cera-india.com/brand/polipluz and https://www.cera-india.com/cera-care have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 95 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
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…”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 316 words of copy
The homepage carries about 316 words of visible text.
5 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Service Request”, “Apply” and “Book Match”.
5 short forms
5 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 4 phone links and 4 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
No consent tool detected
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.
19 other companies contacted
Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at cera-india.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on cera-india.com, including 24 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.