ireneneuwirth.com website review

8 third-party services load with your homepage (Google Tag Manager, Lucky Orange and Klaviyo and others), adding 1.1 MB and 1.1 s of main-thread time.

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

Google Tag Manager costs a phone 425 ms of main-thread work and 499 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.

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

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

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

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

Lucky Orange costs a phone 278 ms of main-thread work and 106 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.

About 62 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.

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

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

1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 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 12.4 s. Good is under 3.8 s.

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

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

Your largest element takes 3.6 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 4.2 s (Speed Index). Good is under 3.4 s.

Your homepage downloads 2.7 MB in 244 requests on a phone: scripts 1.2 MB (88), other files 903 KiB (124) and images 335 KiB (20). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.1 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.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 317 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 142 pages on ireneneuwirth.com and 5 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.

/pages/stores, /pages/wishlist and /collections/studs have no meta description, so Google writes the search snippet from whatever text it finds.

/collections has no <h1> headline, so visitors and search engines get no clear main topic.

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

9 of 26 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 “Access to XMLHttpRequest at 'https://dvbv96fvxd6o6.cloudfront.net/assets/css/shopify.min.css' from origin 'https://iren…”.

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.

ireneneuwirth.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

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

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

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