stonexglobal.com website review

About 689 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.

7 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.2 MB and 1.0 s of main-thread time.

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

Google Tag Manager costs a phone 832 ms of main-thread work and 1,016 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.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 650 ms.

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

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

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

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

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

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

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 see the first content after 3.1 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MASTERY”.

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

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

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

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

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

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

Your homepage downloads 33.6 MB in 105 requests on a phone: media 30.4 MB (14), images 1.6 MB (24) and scripts 1.4 MB (27). Under 2 MB keeps phones on slow connections fast.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Some lists contain elements other than list items, which screen readers announce wrongly.

Your title is 74 characters, so Google will cut it off around 60: “StoneX: Create Your Imprint on Time | Elevating the Value of Natural Stone”.

There are 5 <h1> headlines (“Mastery”, “Stone” and “Art”). One clear main headline is easier for people and search engines.

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 17 pages on stonexglobal.com and 4 external pages.

There is no https://www.stonexglobal.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://www.stonexglobal.com/refinery/kishangarh, https://www.stonexglobal.com/corporate-governance-communications and https://www.stonexglobal.com/contact-us have no <title>, so Google invents the link text in results.

https://www.stonexglobal.com/refinery/kishangarh, https://www.stonexglobal.com/corporate-governance-communications and https://www.stonexglobal.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.stonexglobal.com/mastery, whose canonical is https://www.stonexglobal.com/page-url. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.stonexglobal.com/mastery, https://www.stonexglobal.com/art, https://www.stonexglobal.com/stone, https://www.stonexglobal.com/experience, https://www.stonexglobal.com/blogs and https://www.stonexglobal.com/refinery/kishangarh have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.stonexglobal.com/mastery, https://www.stonexglobal.com/art, https://www.stonexglobal.com/stone, https://www.stonexglobal.com/experience, https://www.stonexglobal.com/blogs and https://www.stonexglobal.com/corporate-governance-communications and 1 other 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 8 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Requests the notification permission on page load.

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

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

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.

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