dreizack.at website review

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

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

6 images could be 598 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

1 third-party service load with your homepage (supabase.co), adding 1.2 MB and 0 ms of main-thread time.

supabase.co costs a phone 0 ms of main-thread work and 1.2 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.

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

About 62 KiB of JavaScript is downloaded but never used 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.

Real visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

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

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Weihnachtlicher Holztisch vor Christbaum und Lichterkette: …”. Most of its time is resource load delay (5.0 s).

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

4 images are downloaded at several times the size a phone draws them, for example weihnachtsornament-mit-wunschnamen-3-farben-waehlbar-schneef at 1,184 px wide, shown at 147 px. Resized copies would save about 536 KiB.

Your homepage downloads 2.2 MB in 159 requests on a phone: images 1.5 MB (15), scripts 465 KiB (132) and HTML 123 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image (204 KiB) is 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.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 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).

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

No XML sitemap at https://www.dreizack.at/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 265 pages on dreizack.at and 8 external pages.

https://www.dreizack.at/favoriten and https://www.dreizack.at/warenkorb are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.dreizack.at/geschenk-berater, https://www.dreizack.at/favoriten, https://www.dreizack.at/anlass/weihnachten, https://www.dreizack.at/anlass/nikolo, https://www.dreizack.at/anlass/weihnachtsfeier and https://www.dreizack.at/anlass/geburtstag and 1 other took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

Large scripts ship without source maps.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Opening the homepage sets 2 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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.