orangemantra.com website review

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

Your mobile performance score is 53 (desktop: 85). Pages that score under 90 lose visitors before the first paint.

About 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.

5 third-party services load with your homepage (Cloudflare, Google Fonts and fontshare.com and others), adding 499 KiB and 8 ms of main-thread time.

Desktop scores 85 but mobile only 53. 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.

3 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Real visitors wait 223 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

client-logos14.svg weighs 507 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.6 MB in 115 requests on a phone: images 2.8 MB (75), fonts 628 KiB (11) and stylesheets 109 KiB (18). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example m3mlogo.png at 1,212 px wide, shown at 169 px. Resized copies would save about 143 KiB.

1 image (174 KiB) is 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.

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

8 elements use ARIA attributes their role does not allow, which confuses screen readers.

2 buttons have no accessible name, so screen readers announce just “button”.

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

Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Structured data found (BreadcrumbList, ImageObject, LocalBusiness and Person) but with 2 problems, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 556 pages on orangemantra.com and 7 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

1 error was logged to the browser console while the page loaded, for example “jQuery is not defined”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

The homepage carries about 1,581 words of visible text.

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