envyo | Webdesign aus München - Samuel Ohonin

What Dr Urls found on envyo.de

From the audit of their public home page on 25/10/2026, worst first. Each links to what it means and how it is fixed.

• medium
  Image file too large (>500 KB)

  Images typically account for 50-75% of a page's total weight.

• medium
  Render-blocking CSS or JavaScript

  Render-blocking resources directly impact First Contentful Paint (FCP) and Largest Contentful Paint (LCP), both Core Web Vitals metrics.

• low
  CSS files are not minified

  Unminified CSS files are larger than necessary, increasing download time and delaying rendering.

• low
  Duplicate heading text on same page

  Duplicate headings reduce the uniqueness and semantic clarity of the page structure.

• low
  Excessive inline CSS

  Inline CSS cannot be cached separately by the browser, so it is re-downloaded with every page load.

• low
  Excessive inline JavaScript

  Inline JavaScript cannot be cached by the browser and must be parsed and executed every time the page loads.

• low
  Images not using modern format

  WebP images are 25-35% smaller than equivalent JPEG images, and AVIF offers even greater savings.

• low
  JavaScript files are not minified

  JavaScript is the most expensive resource type per byte because it must be downloaded, parsed, compiled, and executed.

• low
  Related form controls not grouped with fieldset

  Without fieldset and legend, screen reader users hear individual radio buttons or checkboxes without understanding what group they belong to.

• low
  Too many on-page links

  PageRank is divided among all links on a page, so more links means less equity passed to each destination.

• low
  X-Content-Type-Options header missing

  Without this header, browsers may interpret files as a different content type than intended, which can lead to XSS attacks when a malicious file is interpreted as executable scrip…

6 security findings are not listed on this public page; the site's owner sees them in a full audit after claiming it.