gooddevil.com website review

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

8 third-party services load with your homepage (Shopify, rebuyengine.com and Attentive and others), adding 3.2 MB and 1.5 s of main-thread time.

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

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

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

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

Shopify costs a phone 572 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.

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

rebuyengine.com costs a phone 228 ms of main-thread work and 633 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.

Attentive costs a phone 166 ms of main-thread work and 488 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.

trypalomar.com costs a phone 100 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

36 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

Your homepage downloads 7.4 MB in 662 requests on a phone: images 2.8 MB (144), scripts 2.7 MB (233) and other files 1.3 MB (217). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Launch_Flaming_Fetishes_HOME_Mobile_1.jpg at 1,385 px wide, shown at 390 px. Resized copies would save about 37 KiB.

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

12 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 → h4 and 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.

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

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

The homepage links to 96 pages on gooddevil.com and 1 external page.

/collections/best-seller and /collections/vendors all use the title “Best Seller – Good Devil”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/best-seller, /collections/underwear-accessories and /collections/vendors have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /collections/vendors, whose canonical is /collections/best-seller. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/mens-bikinis and /collections/vendors took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 422 ()”.

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

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.

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

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

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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

DMARC is set to p=none, so mail pretending to be gooddevil.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, Google Tag Manager, Klaviyo 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 30 cookies, 1 of them by other companies (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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.