Performance Tools

Analyze local image dimensions and file size, minify CSS and JavaScript, and observe public website response-header timing with clear limitations.

A practical website performance workflow

Separate asset size from server response delay. Inspect a local image's bytes and dimensions, compact CSS and JavaScript with parsers, and use the existing TTFB checker for one Worker-to-target response-header observation. Local file/code tools send no input to the API. The remote timing check still needs its API connection; none of these tools measures full browser rendering or Core Web Vitals.

  1. Inspect image dimensions and byte budgets locally before choosing an actual encoder elsewhere.
  2. Minify CSS/JavaScript conservatively, review measured UTF-8 savings and test output in your application.
  3. If investigating server delay, compare TTFB observations under similar conditions and review redirect/cache headers separately from browser rendering.

When to use these tools

  • A large image dominates the browser waterfall: compare its encoded dimensions with the display slot before producing smaller variants.
  • A release adds script weight: compare original and minified bytes, then verify behavior and measure transfer in the application.