ratnamani.com website review

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

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

14 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

About 112 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 800 ms faster on a phone.

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

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

27 KiB could be saved by minifying JavaScript.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 177 KiB and 102 ms of main-thread time.

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

7 KiB could be saved by minifying CSS.

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

Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “× We have been certified as Great Place to Work …”.

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

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

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

9 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 4.2 MB in 54 requests on a phone: images 3.8 MB (35), scripts 292 KiB (7) and stylesheets 51 KiB (8). Under 2 MB keeps phones on slow connections fast.

21 images (3.5 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 further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example banner1.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 97 KiB.

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

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

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

<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 29 characters: “Ratnamani Metals & Tubes Ltd.”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://ratnamani.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at ratnamani.com/robots.txt, the first file search crawlers ask for.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 41 pages on ratnamani.com and 4 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 https://ratnamani.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.

/, https://ratnamani.com/company_profile.html, https://ratnamani.com/product_lines.html, https://ratnamani.com/quality_certifications.html, https://ratnamani.com/international_presence.html and https://ratnamani.com/disclosures.html and 9 others all use the title “Ratnamani Metals & Tubes Ltd.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ratnamani.com/company_profile.html, https://ratnamani.com/product_lines.html, https://ratnamani.com/quality_certifications.html, https://ratnamani.com/international_presence.html, https://ratnamani.com/investors_relations.html and https://ratnamani.com/disclosures.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ratnamani.com/company_profile.html, https://ratnamani.com/product_lines.html, https://ratnamani.com/quality_certifications.html, https://ratnamani.com/international_presence.html, https://ratnamani.com/investors_relations.html and https://ratnamani.com/disclosures.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'top')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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 351 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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