rangde.org website review

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.0 s).

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 36 (desktop: 63). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 5.7 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

16 files are served with short cache lifetimes, so returning visitors download them again (5.8 MB).

8 third-party services load with your homepage (Google Tag Manager, chatra.io and Cloudflare CDN and others), adding 1.8 MB and 2.4 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page.

chatra.io costs a phone 553 ms of main-thread work and 370 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.

6 images could be 553 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

16 long tasks block the main thread while loading, the longest for 304 ms. During a long task the page ignores taps.

The page has 1,503 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 43 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

Desktop scores 63 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

The page becomes fully interactive after 23.2 s. Good is under 3.8 s.

Visually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.

The layout shifts by 0.454 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.

The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A simple loan can spark a lifetime of growth. Empower a rur…”.

3 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 138 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.2 MB in 149 requests on a phone: media 5.4 MB (4), scripts 2.2 MB (33) and images 1.1 MB (29). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 2.60 g of CO₂e: 311.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

45 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

7 form fields have no label, so screen readers announce an empty box and autofill guesses.

6 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

There are 3 <h1> headlines (“Get Started”, “Some of our success stories” and “Interested but unsure? Talk to our founders every…”). One clear main headline is easier for people and search engines.

6 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 36 pages on rangde.org and 17 external pages.

https://rangde.in/invest, https://rangde.in/invest/individuals, https://rangde.in/partner-with-us, https://rangde.in/pricing-structure-policy and https://rangde.in/protection-policy all use the title “Rang De”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rangde.in/loan-terms-and-conditions has no meta description, so Google writes the search snippet from whatever text it finds.

https://rangde.in/invest, https://rangde.in/invest/individuals, https://rangde.in/partner-with-us, https://rangde.in/pricing-structure-policy and https://rangde.in/protection-policy use the same meta description. A description written for each page earns more clicks.

https://rangde.in/invest, https://rangde.in/faqs, https://rangde.in/contact, https://rangde.in/invest/individuals, https://rangde.in/partner-with-us and https://rangde.in/terms and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://rangde.in/invest, https://rangde.in/invest/individuals, https://rangde.in/partner-with-us, https://rangde.in/pricing-structure-policy and https://rangde.in/protection-policy 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.

We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.

7 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 915 words of visible text.

Before 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.

Opening the homepage sets 10 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.