aruhat.com website review

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

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

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

12 images could be 732 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

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

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

Google CDN costs a phone 1.5 s of main-thread work and 2.2 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 24 (desktop: 41). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

7 third-party services load with your homepage (Google CDN, zohocdn.com and Other Google APIs/SDKs and others), adding 3.3 MB and 2.1 s of main-thread time.

zohocdn.com costs a phone 282 ms of main-thread work and 726 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.

38 KiB could be saved by minifying CSS.

67 KiB could be saved by minifying JavaScript.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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.

Your largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “[email protected] DATACROPS WEB DATA EXTRACTIO…”.

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

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

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

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

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

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

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.

Your homepage downloads 7.0 MB in 137 requests on a phone: scripts 2.9 MB (44), images 1.9 MB (32) and fonts 749 KiB (11). Under 2 MB keeps phones on slow connections fast.

home-banners-a-09-08-14.jpg weighs 547 KiB. On a phone connection a single image that size takes seconds.

9 images (1.1 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.

1 image is downloaded at several times the size a phone draws it, for example SiliconIndia-Aruhat-Best-Company-to-Work-for-July20151.jpg at 1,900 px wide, shown at 395 px. Resized copies would save about 85 KiB.

6 images further down the page (192 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

3 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is 74 characters, so Google will cut it off around 60: “Technology Enabling Business | Web Data Extraction | VAS Platform - Aruhat”.

There are 3 <h1> headlines (“LATEST NEWS”, “FROM ARTICLES” and “Say Hello!”). One clear main headline is easier for people and search engines.

10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 117 pages on aruhat.com and 9 external pages.

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.

There is no /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.

Your homepage links to /solutions/online-market-intelligence, which answers with an error. Visitors hit a dead end and search engines drop it.

/sms-gateway and /teleoss/messaging-suite all use the title “SMS Gateway Software with API & Dynamic Routing | TeleOSS”. Search engines can't tell which page to show for a search, so each competes with the others.

/sms-gateway and /teleoss/messaging-suite use the same meta description. A description written for each page earns more clicks.

/news-events, /alliances-affiliations-aruhat-technologies-pvt-ltd, /quality-policy-aruhat-technologies-pvt-ltd, /datacrops, /teleoss and /datacrops/datacrops-portfolio and 3 others took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://aruhat.com/.

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

2 errors were logged to the browser console while the page loaded, for example “reCAPTCHA has already been rendered in this element”.

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

1 image is served at too low a resolution for sharp phone screens.

1 link from your homepage to your own site is broken, for example https://aruhat.com/datacrops/online-market-intelligence (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

10 links go through two or more redirects, for example https://aruhat.com/datacrops/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

aruhat.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

aruhat.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads (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 11 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.