Website review, no card needed
ritams.com website review
Visit site (opens in a new tab)Reviewed 13 November 202627 issues · 66 checks
This review found 27 issues worth fixing on ritams.com, 10 of them high impact, across 66 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
74C- #76,694 of 108,858 reviewed websitesbeats 26%
- #48,393 of 61,765 online storesbeats 18%
- #1,372 of 2,512 WooCommerce storesbeats 39%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
3.4 s · 7.6 MB10 images could be 7.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.4 s faster on a phone.
Render-blocking requests
3.4 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 106 KiBAbout 106 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 249 KiB and 0 ms of main-thread time.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 106 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.9 s
6.9 sYour largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ऋतम् The Pulse of Bharat”. Most of its time is resource load delay (3.7 s).
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.9 s
6.9 sThe page becomes fully interactive after 6.9 s. Good is under 3.8 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
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.
2 checks passed
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 11.2 MB in 61 requests
11.2 MBYour homepage downloads 11.2 MB in 61 requests on a phone: images 10.7 MB (14), fonts 246 KiB (10) and stylesheets 141 KiB (16). Under 2 MB keeps phones on slow connections fast.
8 images over 500 KB
8 images weigh 9.5 MB together. On a phone connection a single image that size takes seconds.
11 images in older formats
11 images (10.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.
11 images below the first screen load straight away
11 images further down the page (10.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.2 g of CO₂ per visit
3.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.17 g of CO₂e: 380.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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 1 more 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 (28 characters)
Your title is only 28 characters: “Ritams – The Indic Super App”. 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.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
53 internal links, 2 external
The homepage links to 53 pages on ritams.com and 2 external pages.
4 checks passed
One H1 headline
Your main headline reads: “ऋतम्”.
Canonical URL set
The canonical URL is https://ritams.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://ritams.com/wp-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://ritams.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.
1 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.
Other pages
15 pages without a meta description
https://ritams.com/store-listing, https://ritams.com/%e0%a4%86%e0%a4%9a%e0%a4%be%e0%a4%b0%e0%a5%8d%e0%a4%af-%e0%a4%8f%e0%a4%b5%e0%a4%82-%e0%a4%aa%e0%a4%82%e0%a4%a1%e0%a4%bf%e0%a4%a4-%e0%a4%ac%e0%a5%81%e0%a4%95%e0%a4%bf%e0%a4%82%e0%a4%97, https://ritams.com/%e0%a4%b5%e0%a5%88%e0%a4%a6%e0%a4%bf%e0%a4%95-%e0%a4%a7%e0%a4%b0%e0%a5%8d%e0%a4%ae-%e0%a4%b8%e0%a5%87%e0%a4%b5%e0%a4%be%e0%a4%8f%e0%a4%81-hindu-services, https://ritams.com/%e0%a4%9c%e0%a5%88%e0%a4%a8-%e0%a4%a7%e0%a4%b0%e0%a5%8d%e0%a4%ae-%e0%a4%b8%e0%a5%87%e0%a4%b5%e0%a4%be%e0%a4%8f%e0%a4%81-jain-services, https://ritams.com/buddhist-services and https://ritams.com/%e0%a4%a6%e0%a5%88%e0%a4%a8%e0%a4%bf%e0%a4%95-%e0%a4%aa%e0%a4%82%e0%a4%9a%e0%a4%be%e0%a4%82%e0%a4%97 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages with very little text
https://ritams.com/store-listing, https://ritams.com/%e0%a4%86%e0%a4%9a%e0%a4%be%e0%a4%b0%e0%a5%8d%e0%a4%af-%e0%a4%8f%e0%a4%b5%e0%a4%82-%e0%a4%aa%e0%a4%82%e0%a4%a1%e0%a4%bf%e0%a4%a4-%e0%a4%ac%e0%a5%81%e0%a4%95%e0%a4%bf%e0%a4%82%e0%a4%97, https://ritams.com/%e0%a4%b5%e0%a5%88%e0%a4%a6%e0%a4%bf%e0%a4%95-%e0%a4%a7%e0%a4%b0%e0%a5%8d%e0%a4%ae-%e0%a4%b8%e0%a5%87%e0%a4%b5%e0%a4%be%e0%a4%8f%e0%a4%81-hindu-services, https://ritams.com/%e0%a4%9c%e0%a5%88%e0%a4%a8-%e0%a4%a7%e0%a4%b0%e0%a5%8d%e0%a4%ae-%e0%a4%b8%e0%a5%87%e0%a4%b5%e0%a4%be%e0%a4%8f%e0%a4%81-jain-services, https://ritams.com/buddhist-services and https://ritams.com/%e0%a4%a6%e0%a5%88%e0%a4%a8%e0%a4%bf%e0%a4%95-%e0%a4%aa%e0%a4%82%e0%a4%9a%e0%a4%be%e0%a4%82%e0%a4%97 and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
2 pages slow to respond
https://ritams.com/%e0%a4%b5%e0%a5%88%e0%a4%a6%e0%a4%bf%e0%a4%95-%e0%a4%a7%e0%a4%b0%e0%a5%8d%e0%a4%ae-%e0%a4%b8%e0%a5%87%e0%a4%b5%e0%a4%be%e0%a4%8f%e0%a4%81-hindu-services and https://ritams.com/%e0%a4%9c%e0%a5%88%e0%a4%a8-%e0%a4%a7%e0%a4%b0%e0%a5%8d%e0%a4%ae-%e0%a4%b8%e0%a5%87%e0%a4%b5%e0%a4%be%e0%a4%8f%e0%a4%81-jain-services took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
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
4 small tap targets
4 of 9 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 “Cannot read properties of undefined (reading 'register')”.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 103 words
The homepage has only about 103 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
1 call to action
The homepage has 1 call to action, for example “Get in Touch”.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ritams.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
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Hosting
- Hostycare As In Srmak Technological System Private Limited
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on ritams.com, including 8 speed issues, 4 SEO issues and 5 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.