Imageworker

What Dr Urls found on imageworker.de

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

• high
  Slow server response time (TTFB > 3s)

  Page speed is a confirmed Google ranking factor, and TTFB is the foundational component.

• high
  Time to First Byte (TTFB) is slow

  TTFB directly impacts all subsequent loading metrics.

• 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.

• medium
  Scripts without async or defer

  Synchronous scripts halt HTML parsing while the browser downloads and executes them.

• low
  Below-the-fold images not lazy loaded

  Loading all images immediately increases initial page weight and competes with critical resources for bandwidth.

• low
  Broken heading hierarchy

  Heading hierarchy provides a semantic outline of the page content.

• low
  Duplicate heading text on same page

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

• low
  ETag header missing on resources

  Without ETags, browsers cannot efficiently validate whether cached resources have changed.

• 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 missing responsive srcset

  Without srcset, a 1200px wide image is downloaded on a 375px wide mobile screen, wasting bandwidth and slowing load times.

• low
  Images not using modern format

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

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