Website review, no card needed

mountaindrop.nl logo

mountaindrop.nl website review

Visit site (opens in a new tab)Reviewed 16 November 202627 issues · 78 checks

This review found 27 issues worth fixing on mountaindrop.nl, 6 of them high impact, across 78 checks. The most urgent: 2 images over 500 KB. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.5 s928 msMay 30Nov 141.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 2026991 ms
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Nov 14, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
156 ms69 msMay 30Nov 7138 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202679 ms
Aug 1, 2026108 ms
Aug 8, 2026116 ms
Aug 15, 2026124 ms
Aug 22, 2026127 ms
Aug 29, 2026129 ms
Sep 5, 2026137 ms
Sep 12, 2026137 ms
Sep 19, 2026146 ms
Nov 7, 2026138 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mountaindrop.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mountaindrop.nl at 0.4 s0.4 s
  2. mountaindrop.nl at 0.8 s0.8 s
  3. mountaindrop.nl at 1.1 s1.1 s
  4. mountaindrop.nl at 1.5 s1.5 s
  5. mountaindrop.nl at 1.9 s1.9 s
  6. mountaindrop.nl at 2.3 s2.3 s
  7. mountaindrop.nl at 2.6 s2.6 s
  8. mountaindrop.nl at 3.0 s3.0 s

Speed

6 to fix77
  • Mobile performance score: 77

    77/100

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

  • Render-blocking requests

    750 ms

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

  • Improve image delivery

    300 ms · 241 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and Google CDN and others), adding 1.2 MB and 161 ms of main-thread time.

  • 2,193 HTML elements

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

  • Shopify adds 53 ms

    53 ms

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

  • Reduce unused JavaScript

    151 KiB

    About 151 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    19 KiB

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

  • Reduce unused CSS

    12 KiB

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

  • Use efficient cache lifetimes

    8 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 360 ms of it running JavaScript. That is comfortably low.

  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 6.1 s

    6.1 s

    Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mountaindrop Shilajit – De Puurste Shilajit in de Wereld”.

  • Tap response (INP) got 63% slower for real visitors

    +63%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 87 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Time to Interactive: 6.1 s

    6.1 s

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

  • 15 images without width and height

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 391 ms

    391 ms

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

  • Speed Index: 2.9 s

    2.9 s

    Visually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.005

    0.005

    The layout barely moves while loading (CLS 0.005, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix40
  • 2 images over 500 KB

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

  • 3 images far larger than shown

    2.0 MB

    3 images are downloaded at several times the size a phone draws them, for example Homepage_Hero_Slika_Mountaindrop_Shilajit.webp at 2,880 px wide, shown at 390 px. Resized copies would save about 2.0 MB.

  • 3 images in older formats

    3 images (3.2 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.

  • Page weight: 2.3 MB in 233 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 233 requests on a phone: other files 775 KiB (94), images 693 KiB (28) and scripts 596 KiB (76). Under 2 MB keeps phones on slow connections fast.

  • 5 images below the first screen load straight away

    5 images further down the page (110 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.66 g

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

Accessibility

2 to fixGoogle 9096
  • 3 text elements with low contrast

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

  • 5 images without alt text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9285
  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “Shilajit kopen – Himalaya & Altai | 100% Pure & Premium | Mountaindrop.nl”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Ontgrendel de EnergieDie Je Mistmet De Puurste Sh…”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 72 internal links, 2 external

    The homepage links to 72 pages on mountaindrop.nl and 2 external pages.

5 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Koop gecertificeerde Shilajit uit de Himalaya en Altai. 100% puur, lab-getest en direct uit voorraad leverbaar. Voor fo…”.

  • Canonical URL set

    The canonical URL is https://www.mountaindrop.nl/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mountaindrop.nl/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.mountaindrop.nl/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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,186 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.mountaindrop.nl/collections/all, https://www.mountaindrop.nl/policies/shipping-policy and https://www.mountaindrop.nl/collections/all-products have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.mountaindrop.nl/collections/all and https://www.mountaindrop.nl/collections/all-products have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 distorted images

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

2 checks passed
  • Tap targets are thumb-sized

    11 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

    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 detected

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

  • No direct contact details

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,783 words of copy

    The homepage carries about 1,783 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop” and “SHOP NOW”.

  • 11 short forms

    11 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks, a star rating and 9 trust badges.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 21 other companies contacted

    Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mountaindrop.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Upsell Kit · Gempages Builder · Klaviyo Email Marketing Sms · Gempages Cro · Appstle Bundles

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on mountaindrop.nl, including 10 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25