nu3.at website review

14 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.9 s faster on a phone.

32 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).

sa-tech.de costs a phone 1.0 s of main-thread work and 971 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 1.1 s.

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (sa-tech.de, Usercentrics CMP and sae-conversational.com and others), adding 1.7 MB and 1.2 s of main-thread time.

About 468 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 660 ms faster on a phone.

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

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

redcare.it costs a phone 0 ms of main-thread work and 376 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 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

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.

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

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

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

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

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

The layout shifts by 0.169 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 173 ms to 167 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 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.9 MB in 141 requests on a phone: images 4.0 MB (32), scripts 1.5 MB (75) and fonts 232 KiB (6). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example SAE_nu3-Produkte_Header-Image_nature_mobile_500x500px.png at 1,500 px wide, shown at 338 px. Resized copies would save about 1,003 KiB.

3 images (1.8 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.

SAE_nu3-Produkte_Header-Image_nature_mobile_500x500px.png 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).

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

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

There are 8 <h1> headlines (“nu3 bei Shop Apotheke. Jetzt Willkommensbonus sic…”, “Exklusiv:” and “nu3 bei Shop Apotheke”). One clear main headline is easier for people and search engines.

The homepage links to 270 pages on nu3.at and 17 external pages.

There is no https://www.shop-apotheke.at/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.shop-apotheke.at/neu-im-sortiment and https://www.shop-apotheke.at/gratis-aktionen are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.shop-apotheke.at/about and / all use the title “Online Apotheke für Österreich ▷ Shop Apotheke”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.shop-apotheke.at/nx/newsletter has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.shop-apotheke.at/nx/newsletter, https://www.shop-apotheke.at/neu-im-sortiment and https://www.shop-apotheke.at/gratis-aktionen have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.shop-apotheke.at/beautyprodukte-und-pflegeprodukte, https://www.shop-apotheke.at/sanitaetshaus, https://www.shop-apotheke.at/markenshops/redcare, https://www.shop-apotheke.at/neu-im-sortiment, https://www.shop-apotheke.at/angebote and https://www.shop-apotheke.at/gratis-aktionen and 1 other took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

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 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 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 1,694 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

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

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