Testing Image Processing

Introduction

This post exists to validate and demonstrate HTS’s image processing defaults.

Images referenced in Markdown are processed automatically at build time, without requiring shortcodes, manual resizing, or author-side configuration.

Example Image

Here’s an image referenced directly from the project:

What Happens Automatically

When this post is built, the image above is:

• Resized into multiple responsive variants
• Converted to modern formats (WebP / AVIF where supported)
• Lazy-loaded with explicit dimensions to prevent layout shift
• Served through the global CDN

All of this happens by default and applies uniformly across posts and pages.

Why This Matters

Automatic image processing ensures:

• predictable performance characteristics
• consistently good Core Web Vitals
• simple authoring workflows
• no need for per-image decisions or plugins

The goal is to make the correct behavior the default behavior.