emmi-pet.com website review

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

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

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

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

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

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

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

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

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

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

Facebook costs a phone 251 ms of main-thread work and 226 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.

Klaviyo costs a phone 211 ms of main-thread work and 321 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 22 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.

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

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

13 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 19.6 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 4.1 MB in 327 requests on a phone: scripts 1.6 MB (121), images 1.3 MB (40) and other files 816 KiB (126). Under 2 MB keeps phones on slow connections fast.

11 images (1.4 MB) 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.

emmi_pet_NEO_mit_Badge_EN.webp 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).

7 images further down the page (741 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example Bild_Zahnfleischerkrankungen.webp at 500 px wide, shown at 160 px. Resized copies would save about 15 KiB.

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

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

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

All page content should be contained by landmarks: 7 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

There are 3 <h1> headlines (“SEO TEXT H1 emmi-pet”, “” and “Explanation video”). One clear main headline is easier for people and search engines.

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

Structured data found (BreadcrumbList, FAQPage, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://emmi-pet.de)”.

The homepage links to 234 pages on emmi-pet.com and 11 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://emmi-pet.com/pages/b2b, https://emmi-pet.com/collections/animal-requirement, https://emmi-pet.com/collections/discover, https://emmi-pet.com/collections/novelties and https://emmi-pet.com/collections/offers have no meta description, so Google writes the search snippet from whatever text it finds.

https://emmi-pet.com/pages/b2b, https://emmi-pet.com/products/geruchsentferner-mit-probiotika-500ml, https://emmi-pet.com/products/dental-spray-happydent, https://emmi-pet.com/products/emmizyme-zahnpflege-gel, https://emmi-pet.com/collections/ultrasonic-toothbrushes and https://emmi-pet.com/collections/dental-care and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://emmi-pet.com/collections/animal-requirement took over 3 s to send its HTML from our server.

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

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=149001528&Ver=2&mid=92b5e51e-d503-4852-81db-9ed6621afcd7&bo=4&sid=fa0d2a20dd8e11f1a18cd1bede188561&vid=fa0d54e0dd8e11f1b3e9457dfab27f0e&vids=0&msclkid=N&pi=918639831&l.

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'children') https://emmi-pet.com/:8381:48”.

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 1,456 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 Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 2 mores (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 24 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 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.