mollyogmy.dk website review

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

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

26 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

8 third-party services load with your homepage (Klaviyo, cookiebot.eu and Shopify and others), adding 675 KiB and 369 ms of main-thread time.

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

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

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

19 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 4.6 MB in 306 requests on a phone: images 2.4 MB (113), scripts 1.1 MB (77) and other files 786 KiB (96). Under 2 MB keeps phones on slow connections fast.

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

5 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: 7 elements on the page fail this check, rated moderate by axe-core.

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

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

There are 2 <h1> headlines (“Mollyogmy.dk” and “Molly&My - det bedste udvalg af modetøj til kvind…”). One clear main headline is easier for people and search engines.

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

The homepage links to 1,422 pages on mollyogmy.dk and 23 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://www.mollyogmy.dk/collections/sale-kvinder, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.mollyogmy.dk/collections/det-her-hitter and https://www.mollyogmy.dk/collections/molly-mys-favoritter-1 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.mollyogmy.dk/products/decoy-tights-fleece-280-denier-16959-77-1150-multifarvet, https://www.mollyogmy.dk/collections/det-her-hitter and https://www.mollyogmy.dk/collections/molly-mys-favoritter-1 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mollyogmy.dk/products/decoy-tights-fleece-280-denier-16959-77-1100-black, https://www.mollyogmy.dk/products/decoy-tights-fleece-280-denier-16959-77-1150-multifarvet, https://www.mollyogmy.dk/products/pieces-pcjoline-lace-sock-4984897-black-lace, https://www.mollyogmy.dk/products/sandstone-x-molly-my-shade-shifter-lipstick, https://www.mollyogmy.dk/products/black-colour-bccheckie-sock-8562-dk-grey and https://www.mollyogmy.dk/collections/det-her-hitter and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mollyogmy.dk/products/decoy-tights-fleece-280-denier-16959-77-1100-black, https://www.mollyogmy.dk/products/decoy-tights-fleece-280-denier-16959-77-1150-multifarvet, https://www.mollyogmy.dk/products/pieces-pcjoline-lace-sock-4984897-black-lace, https://www.mollyogmy.dk/products/sandstone-x-molly-my-shade-shifter-lipstick, https://www.mollyogmy.dk/collections/det-her-hitter and https://www.mollyogmy.dk/collections/molly-mys-favoritter-1 and 1 other took over 3 s to send their HTML from our server.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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.

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

Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

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.

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,013 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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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