agravis.de website review

Not measured in this review.

• Tap response (INP) got 20% slower for real visitors

  +20%

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

• Real-user TTFB: 939 ms

  939 ms

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

• 5 images far larger than shown

  498 KiB

  5 images are downloaded at several times the size a phone draws them, for example f,j at 920 px wide, shown at 130 px. Resized copies would save about 498 KiB.

  Elements (5)

• Page weight: 2.8 MB

  2.8 MB

  Your homepage downloads 2.8 MB on a phone, 1.0 MB of it images (37%). Under 2 MB keeps phones on slow connections fast.

• 8 images in older formats

  8 images (941 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.

  Elements (5)

• 2 images below the first screen load straight away

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

  Elements (2)

• About 0.8 g of CO₂ per visit

  0.80 g

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

• Invalid ARIA attributes

  16 elements use ARIA attributes their role does not allow, which confuses screen readers.

  Elements (3)

• Required ARIA attributes must be provided (3 elements)

  Required ARIA attributes must be provided: 3 elements on the page fail this check, rated critical by axe-core.

  Elements (3)

• Certain ARIA roles must contain particular children (1 element)

  Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• ARIA attributes must conform to valid values (1 element)

  ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• All page content should be contained by landmarks (14 elements)

  All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• Heading levels should only increase by one (7 elements)

  Heading levels should only increase by one: 7 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• Banner landmark should not be contained in another landmark (2 elements)

  Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

  Elements (2)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  Elements (2)

• Document should not have more than one banner landmark (1 element)

  Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Document should not have more than one contentinfo landmark (1 element)

  Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 2 form fields without a label

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

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• No canonical URL

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

• Structured data has 4 problems

  Structured data found (BreadcrumbList, CollectionPage, FAQPage and Organization) but with 4 problems, for example “Service: no offers (price) block”.

  View source

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• Most text only appears after JavaScript runs

  0%

  A phone browser shows 1,073 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

• No llms.txt

  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.

• 1 broken image

  1 image failed to load on a phone, for example https://www.agravis.de/.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• No clickjacking protection

  Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

• Short HSTS lifetime

  HSTS is set, but max-age is 0 days; one year is the recommended minimum.

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• 2 redirects before the homepage

  Opening https://agravis.de goes through 2 redirects before the homepage loads.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  agravis.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• No call to action on the first screen

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

• No calls to action

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

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• No form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 1,073 words of copy

  The homepage carries about 1,073 words of visible text.

• Email authentication score: 100/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 4 cookies set on arrival

  4

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

• No consent tool detected

  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.

• 4 other companies contacted

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