Website review, no card needed
silworld.in website review
Visit site (opens in a new tab)Reviewed 17 November 202638 issues · 84 checks
This review found 38 issues worth fixing on silworld.in, 15 of them high impact, across 84 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 6.4 s |
| Jun 6, 2026 | 6.3 s |
| Jun 13, 2026 | 6.5 s |
| Jun 20, 2026 | 6.5 s |
| Jun 27, 2026 | 6.5 s |
| Jul 4, 2026 | 6.5 s |
| Jul 11, 2026 | 6.4 s |
| Jul 18, 2026 | 6.5 s |
| Jul 25, 2026 | 6.5 s |
| Aug 1, 2026 | 6.6 s |
| Aug 8, 2026 | 6.7 s |
| Aug 15, 2026 | 6.8 s |
| Aug 22, 2026 | 6.9 s |
| Aug 29, 2026 | 6.9 s |
| Sep 5, 2026 | 6.9 s |
| Sep 12, 2026 | 7.0 s |
| Sep 19, 2026 | 7.0 s |
| Sep 26, 2026 | 7.0 s |
| Oct 3, 2026 | 6.8 s |
| Oct 10, 2026 | 7.0 s |
| Oct 17, 2026 | 6.7 s |
| Oct 24, 2026 | 6.7 s |
| Oct 31, 2026 | 6.6 s |
| Nov 7, 2026 | 6.5 s |
| Nov 14, 2026 | 6.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 176 ms |
| Jun 13, 2026 | 171 ms |
| Jun 20, 2026 | 165 ms |
| Jun 27, 2026 | 168 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 164 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 165 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 176 ms |
| Aug 22, 2026 | 174 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 174 ms |
| Sep 12, 2026 | 164 ms |
| Sep 19, 2026 | 174 ms |
| Sep 26, 2026 | 166 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 161 ms |
| Oct 24, 2026 | 166 ms |
| Oct 31, 2026 | 173 ms |
| Nov 7, 2026 | 176 ms |
| Nov 14, 2026 | 184 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.9 s
4.3 s
5.8 s
7.2 s
8.7 s
10.1 s
11.5 s
Speed
Render-blocking requests
3.8 s52 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 173 KiBAbout 173 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Use efficient cache lifetimes
262 KiB9 files are served with short cache lifetimes, so returning visitors download them again (262 KiB).
5 third-party services on the page
5 third-party services load with your homepage (Facebook, Google Tag Manager and Bootstrap CDN and others), adding 415 KiB and 260 ms of main-thread time.
Reduce unused JavaScript
177 KiBAbout 177 KiB of JavaScript is downloaded but never used on this page.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 2 KiB2 KiB could be saved by minifying CSS.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
Improve image delivery
12 KiB2 images could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 632 ms of it running JavaScript. That is comfortably low.
Server response: 212 ms
212 msYour server sent the HTML in 212 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: 7.0 s
7.0 sReal visitors wait 7.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.8 s
6.8 sReal visitors see the first content after 6.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.0 s
5.0 sReal visitors wait 5.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.2 s
12.2 sThe page becomes fully interactive after 12.2 s. Good is under 3.8 s.
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.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.4 s).
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 162 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 6.4 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 192 ms
192 msReal visitors wait 192 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Total Blocking Time: 135 ms
135 msScripts block the page for only 135 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.016
0.016The layout barely moves while loading (CLS 0.016, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 148 requests
3.2 MBYour homepage downloads 3.2 MB in 148 requests on a phone: scripts 1.1 MB (53), images 1.1 MB (27) and stylesheets 518 KiB (54). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (27 characters)
Your title is only 27 characters: “Sahyadri Industries Limited”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Home”, “Creating sustainable and eco-friendly solutions” and “Creating sustainable andeco-friendly solutions”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
3 links with vague text
3 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 incomplete here.
69 internal links, 8 external
The homepage links to 69 pages on silworld.in and 8 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.silworld.in/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.silworld.in/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.silworld.in/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (969 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://www.silworld.in/about, https://www.silworld.in/infrastructure, https://www.silworld.in/swastik-gold, https://www.silworld.in/businesses, https://www.silworld.in/investors and https://www.silworld.in/csr and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://www.silworld.in/about, https://www.silworld.in/infrastructure, https://www.silworld.in/swastik-gold, https://www.silworld.in/businesses, https://www.silworld.in/investors and https://www.silworld.in/investor-presentations and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.silworld.in/independent-directors took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 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.
Titles are unique
Every page we checked has its own title.
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 11 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 “ErrorUtils caught an error: Async request failed with error 404: Something went wrong. We're working on getting this fi…”.
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.
Thin social proof
Social proof on the homepage: “0 + Customers”. Pairing it with named testimonials or customer logos makes it far more convincing.
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 334 words of copy
The homepage carries about 334 words of visible text.
2 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Earning Call Transcripts” and “Intimation of Earning call”.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
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.
11 other companies contacted
Loading the homepage contacts 11 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 silworld.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Dreamhost
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on silworld.in, including 14 speed issues, 6 SEO issues and 4 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.