personalify.de website review

20 images could be 485 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

About 1.1 MB of JavaScript is downloaded but never used on this page.

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 2.6 MB and 740 ms of main-thread time.

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

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

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

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

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

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

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

teeinblue.com costs a phone 108 ms of main-thread work and 435 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.

72 KiB could be saved by minifying JavaScript.

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

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

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

5 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The page becomes fully interactive after 21.8 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 “tcF3tIe6fc_orig_web.jpg__PID:3f2d4174-6a44-4af1-8fe7-cc6cac…”.

Real visitors wait 288 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Visually, the page fills in at 4.1 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.

Your homepage downloads 4.4 MB in 374 requests on a phone: scripts 2.0 MB (126), images 1.1 MB (32) and other files 956 KiB (152). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Us_Shipping_converted.webp at 1,902 px wide, shown at 310 px. Resized copies would save about 75 KiB.

9 images (392 KiB) are 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.

1 image further down the page (92 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

5 images have no alt text, which hurts accessibility and image search.

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

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.

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

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

There are 2 <h1> headlines (“” and “Give personally.Smile together.”). One clear main headline is easier for people and search engines.

The homepage links to 53 pages on personalify.de and 1 external page.

https://personalify.com/pages/happy-customers is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://personalify.com/collections/bestseller, https://personalify.com/pages/happy-customers, https://personalify.com/pages/kontakt, https://personalify.com/pages/uber-uns, https://personalify.com/pages/hilfe-kontakt and https://personalify.com/policies/refund-policy and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://personalify.com/pages/hilfe-kontakt, https://personalify.com/products/personalized-dad-hoodie-kids-portrait-retro-style and https://personalify.com/products/personalized-dad-hoodie-with-kids-photo-vintage-style have no <h1> headline, so visitors and search engines get no clear main topic.

https://personalify.com/products/personalized-dad-hoodie-kids-portrait-retro-style and https://personalify.com/products/personalized-dad-hoodie-with-kids-photo-vintage-style have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://personalify.com/collections/bestseller took over 3 s to send its HTML from our server.

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

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Clarity and Pinterest Tag and 1 more (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 11 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.