Website review, no card needed
3sindia.com website review
Visit site (opens in a new tab)Reviewed 21 October 202649 issues · 95 checks
This review found 49 issues worth fixing on 3sindia.com, 29 of them high impact, across 95 checks. The most urgent: improve image delivery. 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
65DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
31.6 s · 9.5 MB8 images could be 9.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 31.6 s faster on a phone.
Use efficient cache lifetimes
24.6 s · 11.7 MB66 files are served with short cache lifetimes, so returning visitors download them again (11.7 MB).
Render-blocking requests
2.2 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Reduce unused JavaScript
1.6 s · 250 KiBAbout 250 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Main-thread work: 17.9 s
A phone's processor spends 17.9 s on main-thread work while loading, 17.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 33
33/100Your mobile performance score is 33 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Reduce unused CSS
450 ms · 96 KiBAbout 96 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 287 ms
287 msGoogle Tag Manager costs a phone 287 ms of main-thread work and 344 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and jQuery CDN and others), adding 875 KiB and 347 ms of main-thread time.
Minify CSS
150 ms · 18 KiB18 KiB could be saved by minifying CSS.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 243 ms
243 msYour server sent the HTML in 243 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 90.5 s
90.5 sYour largest element takes 90.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 92.3 s
92.3 sThe page becomes fully interactive after 92.3 s. Good is under 3.8 s.
Speed Index: 15.2 s
15.2 sVisually, the page fills in at 15.2 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.769
0.769The layout shifts by 0.769 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
71 images without width and height
71 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Total Blocking Time: 134 ms
134 msScripts block the page for only 134 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 24.1 MB in 100 requests
24.1 MBYour homepage downloads 24.1 MB in 100 requests on a phone: images 22.9 MB (61), fonts 555 KiB (7) and scripts 541 KiB (13). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
3.1 MB3 images are downloaded at several times the size a phone draws them, for example con2.png at 832 px wide, shown at 130 px. Resized copies would save about 3.1 MB.
13 images in older formats
13 images (6.0 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.
3 images below the first screen load straight away
3 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.8 g of CO₂ per visit
6.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.83 g of CO₂e: 819.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Hidden but focusable
10 elements hidden from screen readers can still receive keyboard focus.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (5 elements)
ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.
ARIA progressbar nodes must have an accessible name (4 elements)
ARIA progressbar nodes must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
ARIA toggle fields must have an accessible name (1 element)
ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
[role]s are not contained by their required parent element
[role]s are not contained by their required parent element (4 elements).
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Elements marked as presentational should be consistently ignored (3 elements)
Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (9 elements).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 65 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 18 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to sara-plast.com, not 3sindia.com, so Google may credit that host instead.
Structured data has 1 problem
Structured data found (LocalBusiness) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token 'S', " SCHEMA COD"... is not valid JSO)”.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
64 internal links, 14 external
The homepage links to 64 pages on 3sindia.com and 14 external pages.
6 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “India’s leading provider of portable toilets, modular restrooms & cleaning systems. Affordable, eco-friendly sanitation…”.
One H1 headline
Your main headline reads: “India’s No. 1 Provider of Portable Sanitation and Hygiene Solutions”.
Title: 58 characters
Your title is a healthy 58 characters: “Portable Toilets & Sanitation Solutions | Sara Plast India”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://3sindia.com/sitemap.xml.
AI search readiness
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,800 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://3sindia.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
16 pages share a title
/, https://3sindia.com/contact.php, https://3sindia.com/careers.php, https://3sindia.com/faq.php, https://3sindia.com/about-us.php and https://3sindia.com/team.php and 10 others all use the title “Portable Toilets & Sanitation Solutions | Sara Plast India”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://3sindia.com/contact.php, https://3sindia.com/careers.php, https://3sindia.com/faq.php, https://3sindia.com/about-us.php, https://3sindia.com/team.php and https://3sindia.com/how-it-works.php and 9 others use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://3sindia.com/contact.php, https://3sindia.com/awards.php, https://3sindia.com/history.php, https://3sindia.com/cleaningservices.php, https://3sindia.com/containerised.php and https://3sindia.com/Titoilet.php and 2 others 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 37 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
6 small tap targets
6 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
3 distorted images
3 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,143 words of copy
The homepage carries about 1,143 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Click to open Saraplast contact options”.
2 calls to action
The homepage has 2 calls to action, for example “Contact Us” and “Submit Request”.
2 short forms
2 short forms (6 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 68 customer or partner logos, 68 trust badges and “10,500 + Happy Customers”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
12 other companies contacted
Loading the homepage contacts 12 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 3sindia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on 3sindia.com, including 15 speed issues and 3 SEO issues. 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.