Website review, no card needed
stonesearch.co.in website review
Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 73 checks
This review found 37 issues worth fixing on stonesearch.co.in, 12 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. 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
72C- #97,745 of 126,442 reviewed websitesbeats 20%
- #59,778 of 70,471 online storesbeats 12%
- #55,592 of 63,972 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.7 s |
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
0.6 s
1.1 s
1.6 s
2.2 s
2.8 s
3.3 s
3.9 s
4.4 s
Speed
Use efficient cache lifetimes
23.8 s · 17.5 MB55 files are served with short cache lifetimes, so returning visitors download them again (17.5 MB).
Improve image delivery
18.9 s · 15.4 MB16 images could be 15.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 18.9 s faster on a phone.
Render-blocking requests
2.5 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused JavaScript
1.1 s · 202 KiBAbout 202 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 120 KiBAbout 120 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Shopify and others), adding 215 KiB and 174 ms of main-thread time.
Minify CSS
150 ms · 23 KiB23 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 347 ms of it running JavaScript. That is comfortably low.
Server response: 279 ms
279 msYour server sent the HTML in 279 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 46.7 s
46.7 sYour largest element takes 46.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We Make Diamond Trading Easy Stone Search is a fully-automa…”.
Time to Interactive: 48.6 s
48.6 sThe page becomes fully interactive after 48.6 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.11
0.11The layout shifts by 0.11 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 82 ms
82 msScripts block the page for only 82 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 17.8 MB in 61 requests
17.8 MBYour homepage downloads 17.8 MB in 61 requests on a phone: images 17.1 MB (20), scripts 440 KiB (26) and stylesheets 148 KiB (11). Under 2 MB keeps phones on slow connections fast.
9 images over 500 KB
9 images weigh 16.1 MB together. On a phone connection a single image that size takes seconds.
17 images in older formats
17 images (16.6 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.
14 images below the first screen load straight away
14 images further down the page (13.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
267 KiB1 image is downloaded at several times the size a phone draws it, for example dashboard-07.png at 1,150 px wide, shown at 366 px. Resized copies would save about 267 KiB.
About 5.0 g of CO₂ per visit
5.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.03 g of CO₂e: 603.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails 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.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
26 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (12 characters)
Your title is only 12 characters: “STONE SEARCH”. 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.
Meta description is short (55 characters)
Your meta description is only 55 characters: “OLMO - Software, App, SaaS & Startup Landing Pages Pack”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://stonesearch.co.in/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at stonesearch.co.in/robots.txt, the first file search crawlers ask for.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
13 internal links, 12 external
The homepage links to 13 pages on stonesearch.co.in and 12 external pages.
1 checks passed
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://stonesearch.co.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (971 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages share a title
/, https://stonesearch.co.in/Master/Index, https://stonesearch.co.in/Master/AboutUs, https://stonesearch.co.in/Master/FAQs, https://stonesearch.co.in/Master/ContactUs and https://stonesearch.co.in/Master/PrivacyPolicy and 1 other all use the title “STONE SEARCH”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://stonesearch.co.in/Master/Index, https://stonesearch.co.in/Master/AboutUs, https://stonesearch.co.in/Master/FAQs, https://stonesearch.co.in/Master/ContactUs, https://stonesearch.co.in/Master/PrivacyPolicy and https://stonesearch.co.in/Master/TermAndCond use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://stonesearch.co.in/Master/Index, https://stonesearch.co.in/Master/AboutUs, https://stonesearch.co.in/Master/FAQs, https://stonesearch.co.in/Master/ContactUs, https://stonesearch.co.in/Master/PrivacyPolicy and https://stonesearch.co.in/Master/TermAndCond have no <h1> headline, so visitors and search engines get no clear main topic.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
6 pages of 7 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 6 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 6 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “$(...).imagesLoaded is not a function”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 869 words of copy
The homepage carries about 869 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get Started” and “Register”.
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Get Started” and “Register”.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
5 other companies contacted
Loading the homepage contacts 5 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 stonesearch.co.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
- The footer still says © 2021.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Ncinspl In Ntt Communications India Network Services Private Limited
Hiring
- Hiring
- 1 open role
- Job board
- smartrecruiters
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on stonesearch.co.in, including 13 speed issues and 8 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.