succubus.com website review

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

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

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

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

6 third-party services load with your homepage (Shopify, shop.app and addons.business and others), adding 1.3 MB and 582 ms of main-thread time.

Shopify costs a phone 526 ms of main-thread work and 1.1 MB 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

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

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

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

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

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

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.

4 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “♥ Cosy Succubus Clothing knitwear ♥”.

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

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

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

Your homepage downloads 10.0 MB in 480 requests on a phone: media 5.8 MB (1), images 1.5 MB (15) and other files 1.3 MB (220). Under 2 MB keeps phones on slow connections fast.

Codex-afbeelding_21_sep_2026_13_22_45.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 tap target is too small or too close together to hit reliably with a finger.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

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

36 links have no real href, so search engines can't follow them.

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

Structured data found (Organization, ShoppingCenter and WebSite) but with 2 problems, for example “ShoppingCenter: url is not an absolute URL ("www.succubus.nl")”.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 506 pages on succubus.com and 17 external pages.

https://www.succubus.com/collections/new-in and https://www.succubus.com/en-us/collections/new-in all use the title “New In! – Succubus”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.succubus.com/en-us/collections/bestsellers and https://www.succubus.com/en-us/collections/nieuw-jurken have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.succubus.com/collections/new-in and https://www.succubus.com/en-us/collections/new-in use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.succubus.com/collections/new-in, whose canonical is https://www.succubus.com/en-us/collections/new-in. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.succubus.com/collections/new-in, https://www.succubus.com/en-us/collections/new-in, https://www.succubus.com/en-us/collections/nieuw-dames, https://www.succubus.com/en-us/collections/new-in-men, https://www.succubus.com/en-us/collections/succubus-clothing and https://www.succubus.com/en-us/collections/bestsellers 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 182 found) and read each the way a search engine does.

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 108 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

Opening the homepage sets 15 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.