mudrex.com website review

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

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

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

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

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

25 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Amazon Web Services and JSDelivr CDN and others), adding 3.1 MB and 1.1 s of main-thread time.

18 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

JSDelivr CDN costs a phone 189 ms of main-thread work and 1.4 MB 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.

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

Amazon Web Services costs a phone 198 ms of main-thread work and 585 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.

Unpkg costs a phone 154 ms of main-thread work and 496 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,701 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

158 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

Desktop scores 61 but mobile only 29. 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

2 KiB JavaScript is shipped twice across bundles.

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 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 29.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hero”.

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

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

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

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

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

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

15 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-17, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 14.4 MB in 186 requests on a phone: images 7.0 MB (96), scripts 5.4 MB (54) and other files 1.9 MB (25). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

17 images (3.3 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.

hero.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).

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

2 images are downloaded at several times the size a phone draws them, for example what-is-commodities-hero.webp at 3,425 px wide, shown at 350 px. Resized copies would save about 192 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 204 pages on mudrex.com and 8 external pages.

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

Your homepage links to https://mudrex.com/blog/security-advisory-from-mudrex, which answers with an error. Visitors hit a dead end and search engines drop it.

https://mudrex.com/rwa-tokenization-report, https://mudrex.com/help-and-support and https://mudrex.com/diwali-gold-rush have no <title>, so Google invents the link text in results.

https://mudrex.com/futures/10000SATSUSDT/0196f295-88f7-70c2-a579-2a16df910dbe, https://mudrex.com/futures/1000PEPEUSDT/0196f295-8dd1-7b56-aa18-289da3ecc955, https://mudrex.com/futures/PUMPFUNUSDT/019816f5-0ec2-7a93-b7ff-04675b7b6b87, https://mudrex.com/futures/NOTUSDT/01920efc-a3f9-79a4-b1d2-d04b8dd593e0, https://mudrex.com/futures/PIXELUSDT/01920efc-92f0-7841-bf44-5f9dea278c31 and https://mudrex.com/futures/MEMEUSDT/01920efc-7723-777a-8513-0d5d34a4c479 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://mudrex.com/rwa-tokenization-report, https://mudrex.com/help-and-support and https://mudrex.com/diwali-gold-rush have no meta description, so Google writes the search snippet from whatever text it finds.

https://mudrex.com/help-and-support, https://mudrex.com/diwali-gold-rush, https://mudrex.com/futures/10000SATSUSDT/0196f295-88f7-70c2-a579-2a16df910dbe, https://mudrex.com/futures/1000PEPEUSDT/0196f295-8dd1-7b56-aa18-289da3ecc955, https://mudrex.com/futures/PUMPFUNUSDT/019816f5-0ec2-7a93-b7ff-04675b7b6b87 and https://mudrex.com/futures/NOTUSDT/01920efc-a3f9-79a4-b1d2-d04b8dd593e0 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://mudrex.com/futures/10000SATSUSDT/0196f295-88f7-70c2-a579-2a16df910dbe, https://mudrex.com/futures/1000PEPEUSDT/0196f295-8dd1-7b56-aa18-289da3ecc955, https://mudrex.com/futures/PUMPFUNUSDT/019816f5-0ec2-7a93-b7ff-04675b7b6b87, https://mudrex.com/futures/NOTUSDT/01920efc-a3f9-79a4-b1d2-d04b8dd593e0, https://mudrex.com/futures/PIXELUSDT/01920efc-92f0-7841-bf44-5f9dea278c31 and https://mudrex.com/futures/MEMEUSDT/01920efc-7723-777a-8513-0d5d34a4c479 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 15 pages linked from your homepage (of 133 found) and read each the way a search engine does.

5 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

Large scripts ship without source maps.

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: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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

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