lmitextiles.com website review

hcaptcha.com costs a phone 2.5 s of main-thread work and 3.3 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.

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

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

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

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

8 third-party services load with your homepage (hcaptcha.com, customerfields.com and Cloudflare CDN and others), adding 5.0 MB and 3.3 s of main-thread time.

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

About 1.0 MB of JavaScript is downloaded but never used on this page.

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

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

About 83 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.

customerfields.com costs a phone 311 ms of main-thread work and 441 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.

Cloudflare CDN costs a phone 173 ms of main-thread work and 357 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.

Shopify costs a phone 132 ms of main-thread work and 635 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.

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

41 KiB could be saved by minifying JavaScript.

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

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.

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

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “One partner for medical supplies, harm reduction, industria…”.

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

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

63 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.2 MB in 338 requests on a phone: scripts 3.3 MB (90), HTML 1.3 MB (8) and images 1.0 MB (74). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (378 KiB) 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 promotional-prodct-thumb_600x600.png at 556 px wide, shown at 157 px. Resized copies would save about 44 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

13 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 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“” and “LMI: Strategic Sourcing Partner Across Industries”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 127 pages on lmitextiles.com and 4 external pages.

There is no https://www.lmitextiles.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.lmitextiles.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lmitextiles.com/pages/about-us, https://www.lmitextiles.com/collections/all, https://www.lmitextiles.com/pages/makrite-fp-series, https://www.lmitextiles.com/pages/makrite-cfp-series and https://www.lmitextiles.com/pages/makrite-880-series have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.lmitextiles.com/.

3 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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

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

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

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