gomonta.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Hubspot and others), adding 2.4 MB and 1.8 s of main-thread time.

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

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

Google CDN costs a phone 483 ms of main-thread work and 734 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.

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

13 images could be 127 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.

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

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

Desktop scores 87 but mobile only 41. 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.

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.

Your largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We gebruiken cookies om content en advertenties te personal…”.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.8 MB in 144 requests on a phone: scripts 2.3 MB (46), other files 632 KiB (24) and images 508 KiB (42). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Magento-Monta.svg at 1,600 px wide, shown at 24 px. Resized copies would save about 180 KiB.

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

1 image (41 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 1.07 g of CO₂e: 128.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Structured data found (ImageObject, LocalBusiness, Organization and Place) but with 1 problem, for example “Service: no offers (price) block”.

The homepage links to 249 pages on gomonta.com and 7 external pages.

/fulfillment, /fulfillment/goods-receipt, /fulfillment/warehousing, /fulfillment/packaging, /fulfillment/e-fulfillment and /fulfillment/pricing and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 image is served at too low a resolution for sharp phone screens.

6 links from your homepage to your own site are broken, for example https://gomonta.com/?page_id=381 (404).

X-XSS-Protection is set to “1”; the header is deprecated and can introduce bugs. Use 0 or remove it.

gomonta.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

gomonta.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

gomonta.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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