rupyz.com website review

About 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 14.9 s faster on a phone.

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

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

Google CDN costs a phone 1.9 s of main-thread work and 4.1 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.

About 195 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 5.4 MB and 2.9 s of main-thread time.

16 images could be 396 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

Google Tag Manager costs a phone 412 ms of main-thread work and 463 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.

Other Google APIs/SDKs costs a phone 388 ms of main-thread work and 164 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.

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

Google Fonts costs a phone 3 ms of main-thread work and 405 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.

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

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

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.

Real visitors wait 6.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.

Real visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 32.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “B2B Commerce Storefront”.

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

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

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

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

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

16 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-31, real Chrome visitors' tap response (inp) went from 182 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.5 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.7 MB in 196 requests on a phone: scripts 5.3 MB (64), other files 1.7 MB (15) and images 1.3 MB (27). Under 2 MB keeps phones on slow connections fast.

Accelerate-B2B-sales--e1714801651602.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

9 images (1,015 KiB) 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.

2 images are downloaded at several times the size a phone draws them, for example Homepage-₹-First-feature-pic-e1717137329553-1024x914.png at 1,024 px wide, shown at 330 px. Resized copies would save about 39 KiB.

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

8 tap targets are too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

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

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 70 pages on rupyz.com and 16 external pages.

https://rupyz.com/ecommerce-b2b-storefront, https://rupyz.com/field-sales-management-software-fmcg-india, https://rupyz.com/order-management, https://rupyz.com/exhibition-lead-management-tool, https://rupyz.com/rupyz-toys and https://rupyz.com/rupyz-for-agarbatti and 9 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://rupyz.com/ecommerce-b2b-storefront, https://rupyz.com/field-sales-management-software-fmcg-india, https://rupyz.com/order-management, https://rupyz.com/exhibition-lead-management-tool, https://rupyz.com/rupyz-toys and https://rupyz.com/rupyz-for-agarbatti and 9 others use the same meta description. A description written for each page earns more clicks.

https://rupyz.com/field-sales-management-software-fmcg-india, https://rupyz.com/exhibitions-and-trade-fairs and https://rupyz.com/book-a-demo have no <h1> headline, so visitors and search engines get no clear main topic.

https://rupyz.com/ecommerce-b2b-storefront, https://rupyz.com/field-sales-management-software-fmcg-india, https://rupyz.com/order-management, https://rupyz.com/exhibition-lead-management-tool, https://rupyz.com/rupyz-toys and https://rupyz.com/rupyz-for-agarbatti and 6 others took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://reallyfreegeoip.org/json/' from origin 'https://rupyz.com' has been blocked by COR…”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Mixed content”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

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

The homepage has only about 103 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.