funfactory.com website review

About 274 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

8 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and 506.io and others), adding 1.1 MB and 338 ms of main-thread time.

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

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

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

1 long task block the main thread while loading, the longest for 82 ms. During a long task the page ignores taps.

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

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.

5 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

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

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

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

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

5 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' tap response (inp) went from 79 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.7 MB in 293 requests on a phone: other files 1,017 KiB (142), scripts 961 KiB (83) and images 516 KiB (27). Under 2 MB keeps phones on slow connections fast.

VIM-Header-neu-mobil_cec5bfc0-bfb1-4b90-882e-775156e521a7.jp 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).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your <h1> is empty.

The homepage links to 103 pages on funfactory.com and 9 external pages.

Your homepage links to /products/fun-cup, which answers with an error. Visitors hit a dead end and search engines drop it.

/collections/bestseller, /collections/neuheiten, /collections/alle-sextoys and /collections/vibratoren have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/bestseller, /collections/neuheiten, /collections/alle-sextoys, /collections/pulsatoren and /collections/zubehoer took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.funfactory.com/.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

Opening https://funfactory.com goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

funfactory.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

funfactory.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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

DMARC is set to p=none, so mail pretending to be funfactory.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).

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