distalogistics.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and omnisnippet1.com and others), adding 905 KiB and 589 ms of main-thread time.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

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

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

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

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

About 99 KiB of CSS is downloaded but never applied on this page.

16 KiB could be saved by minifying JavaScript.

1 image could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 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.

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

Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop authentic Indian products with faster delivery, lower …”.

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

54 images have no width and height attributes, so the layout jumps as each one loads.

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

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

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 3.1 MB in 270 requests on a phone: scripts 1.1 MB (49), other files 1.1 MB (167) and images 448 KiB (42). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your page has no <title>, so Google has to invent the blue link in search results.

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.

Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://distausa.com/)”.

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

The homepage links to 232 pages on distalogistics.com and 17 external pages.

https://www.distalogistics.com/pages/shipping, https://www.distalogistics.com/pages/suggest-a-product, https://www.distalogistics.com/pages/about-us and https://www.distalogistics.com/pages/contact have no <title>, so Google invents the link text in results.

https://www.distalogistics.com/collections/vitamins-and-supplements, https://www.distalogistics.com/collections/makeup, https://www.distalogistics.com/collections/eye-makeup, https://www.distalogistics.com/collections/face-makeup, https://www.distalogistics.com/collections/lips-makeup and https://www.distalogistics.com/collections/makeup-tools-brushes and 4 others all use the title “list [#fff1497]”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.distalogistics.com/pages/shipping, https://www.distalogistics.com/pages/suggest-a-product, https://www.distalogistics.com/pages/about-us, https://www.distalogistics.com/pages/contact, https://www.distalogistics.com/collections/vitamins-and-supplements and https://www.distalogistics.com/collections/makeup and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

4 images failed to load on a phone, for example https://www.distalogistics.com/.

4 errors were logged to the browser console while the page loaded, for example “updateBackButtonVisibility is not defined”.

Requests the notification permission on page load.

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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 742 words of visible text.

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

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