fleshlight.pt website review

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

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

8 third-party services load with your homepage (Signyfyd, loox.io and Klaviyo and others), adding 1.4 MB and 1.3 s of main-thread time.

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

Signyfyd costs a phone 777 ms of main-thread work and 283 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.

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

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

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

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

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

Hexton costs a phone 73 ms of main-thread work and 306 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.

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

44 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

29 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 23 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.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.7 MB in 366 requests on a phone: images 1.7 MB (110), scripts 1.4 MB (141) and other files 653 KiB (64). Under 2 MB keeps phones on slow connections fast.

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

54 tap targets are too small or too close together to hit reliably with a finger.

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is 77 characters, so Google will cut it off around 60: “Fleshlight.com - Shop Adult Sex Toys & Male Pleasure Products – Fleshlight EU”.

Your canonical URL points to fleshlight.eu, not fleshlight.pt, so Google may credit that host instead.

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

Your <h1> is empty.

The homepage links to 179 pages on fleshlight.pt and 23 external pages.

https://fleshlight.pt/collections/all, https://fleshlight.pt/collections/flight-and-go and https://fleshlight.pt/collections/fleshjack-boy-dildos have no meta description, so Google writes the search snippet from whatever text it finds.

https://fleshlight.pt/collections/fleshlight-girls, https://fleshlight.pt/collections/birthday-girls, https://fleshlight.pt/pages/stamina-training-unit-products, https://fleshlight.pt/pages/quickshot-product-line and https://fleshlight.pt/pages/manga-anime-fantasy-series have no <h1> headline, so visitors and search engines get no clear main topic.

https://fleshlight.pt/pages/stamina-training-unit-products, https://fleshlight.pt/collections/turbo, https://fleshlight.pt/pages/quickshot-product-line, https://fleshlight.pt/pages/manga-anime-fantasy-series, https://fleshlight.pt/collections/fleshjack-boys and https://fleshlight.pt/collections/fleshjack-boy-dildos and 1 other took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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