fwp.at website review

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

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

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

Your mobile performance score is 67 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

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

About 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

9 KiB could be saved by minifying CSS.

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

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

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

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

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

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

7 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-17, real Chrome visitors' tap response (inp) went from 71 ms to 69 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 24.7 MB in 83 requests on a phone: images 24.3 MB (74), scripts 219 KiB (2) and fonts 141 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

7 images (2.0 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.

2 images are downloaded at several times the size a phone draws them, for example mountain.gif at 1,000 px wide, shown at 222 px. Resized copies would save about 372 KiB.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

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.

Elements with visible text labels do not have matching accessible names. (1 element).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“Kompetenz, Teamgeist, Zielorientierung.”, “Das Team” and “Finden Sie Ihre Rechtsanwältinnen und Rechtsanwäl…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

There is no robots.txt at fwp.at/robots.txt, the first file search crawlers ask for.

Open Graph is missing og:title, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 222 pages on fwp.at and 11 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /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.

/ and /en all use the title “fwp - Fellner Wratzfeld & Partner Rechtsanwälte”. Search engines can't tell which page to show for a search, so each competes with the others.

/news, /expertise, /newsletter, /jurist-innen/josef-peer, /jurist-innen/michael-froner and /jurist-innen/markus-kajaba and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

Large scripts ship without source maps.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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.