vn.at website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

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

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

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

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

Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

Cookiebot costs a phone 222 ms of main-thread work and 344 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 31 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.

2 KiB JavaScript is shipped twice across bundles.

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 wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Strafmündigkeit ab zwölf? Experten setzen auf andere Wege”.

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 119 requests on a phone: scripts 2.7 MB (67), images 470 KiB (17) and fonts 145 KiB (6). Under 2 MB keeps phones on slow connections fast.

jv2jbkpgbnkco-IWI8aN-1-600x450.jpg 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).

6 images (282 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 (51 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 0.97 g of CO₂e: 116.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Some list items are not inside a list.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails 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.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Your meta description is only 9 characters: “undefined”. 70 to 160 characters is enough to sell the click.

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

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 68 pages on vn.at and 8 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://www.vn.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.

robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.vn.at/politik/2026/10/27/strafmuendigkeit-ab-zwoelf-experten-setzen-auf-andere-wege.vn, https://www.vn.at/vn/2026/10/27/austausch-und-anerkennung.vn, https://www.vn.at/markt/2026/10/27/depot-war-immer-ein-angenehmer-mieter-mit-attraktivem-angebot.vn, https://www.vn.at/gewalt-und-verbrechen/2026/10/27/mit-messer-und-drohanruf-raeubergeschichte-war-frei-erfunden.vn, https://www.vn.at/ohne-kategorie/2026/10/27/vorarlberger-apfelstrudel-fuer-barcelonas-naschkatzen.vn and https://www.vn.at/kultur/2026/10/27/waeldar-ka-nued-jedar-sin-2.vn and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.vn.at/politik/2026/10/27/strafmuendigkeit-ab-zwoelf-experten-setzen-auf-andere-wege.vn, https://www.vn.at/vn/2026/10/27/austausch-und-anerkennung.vn, https://www.vn.at/markt/2026/10/27/depot-war-immer-ein-angenehmer-mieter-mit-attraktivem-angebot.vn, https://www.vn.at/gewalt-und-verbrechen/2026/10/27/mit-messer-und-drohanruf-raeubergeschichte-war-frei-erfunden.vn, https://www.vn.at/ohne-kategorie/2026/10/27/vorarlberger-apfelstrudel-fuer-barcelonas-naschkatzen.vn and https://www.vn.at/kultur/2026/10/27/waeldar-ka-nued-jedar-sin-2.vn and 8 others use the same meta description. A description written for each page earns more clicks.

https://www.vn.at/sport/2026/10/24/sw-bregenz-verspielt-zweimal-fuehrung-in-salzburg.vn, https://www.vn.at/sport/2026/10/23/bregenzer-jagd-nach-der-mozartkugel.vn, https://www.vn.at/bregenz and https://www.vn.at/vn/2026/10/27/von-klopapiergeschichten-flashmobs-und-buchstabierliedern.vn took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Cannot use 'in' operator to search for 'getRegistrations' in undefined”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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