mountaindrop.com.au website review

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

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

8 third-party services load with your homepage (Shopify, rebuyengine.com and Clarity and others), adding 1.8 MB and 1.5 s of main-thread time.

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

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

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

rebuyengine.com costs a phone 357 ms of main-thread work and 501 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.

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

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

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

3 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 3.4 MB in 342 requests on a phone: scripts 1.7 MB (169), other files 794 KiB (128) and images 471 KiB (16). Under 2 MB keeps phones on slow connections fast.

1 image (49 KiB) is 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.

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

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

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

Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 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.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your title is 94 characters, so Google will cut it off around 60: “Mountaindrop Shilajit - The #1 Shilajit in Australia With 6 Lab Tests – Mountaindrop Aust…”.

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

The homepage links to 53 pages on mountaindrop.com.au and 3 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://mountaindrop.com.au/collections/all-products and https://mountaindrop.com.au/collections/all all use the title “All Products – Mountaindrop Australia”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mountaindrop.com.au/pages/mountaindrop-premium-bundles-save-up-to-28, https://mountaindrop.com.au/pages/about-page-sep-2-08-50-10, https://mountaindrop.com.au/pages/contact-page-sep-2-17-20-24, https://mountaindrop.com.au/pages/lab-results, https://mountaindrop.com.au/pages/how-to-use and https://mountaindrop.com.au/collections/all and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://mountaindrop.com.au/products/mountaindrop%C2%AE-original-shilajit-altai, whose canonical is https://mountaindrop.com.au/products/mountaindrop%c2%ae-original-shilajit-altai. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mountaindrop.com.au/collections/all-products, https://mountaindrop.com.au/pages/mountaindrop-premium-bundles-save-up-to-28, https://mountaindrop.com.au/pages/about-page-sep-2-08-50-10, https://mountaindrop.com.au/pages/lab-results, https://mountaindrop.com.au/pages/how-to-use and https://mountaindrop.com.au/collections/all and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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