Skip to content
Signalcrest
Back to feed
devtoweb

Next.js Image Optimization in 2026: `next/image` v4, AVIF by Default, and the Config Changes Teams Miss

Next.js v4 makes AVIF default and changes image config, impacting performance tuning.

Steady
Signal score
39
as of 56d ago
Sources
3
agreeing on nextjs
Trajectory
⏳ Too early
needs a few more snapshots

Why this scored 39

every term, weighted
Velocity+0.0 / 40

Engagement gained per hour since the last capture, against the fastest item on its own source

Acceleration+12.5 / 25

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+16.7 / 25

How many independent communities are talking about the same entity

Recency+9.9 / 10

Decays to zero over 14 days

Saturation penalty+0.0 / 30

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite39.1

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology

Signal history

7-day window (free)
Not enough history yet — the trend line fills in as snapshots accrue (every 30 min).

Entities

nextjsavif
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/dev%3A4401581)](https://www.signalcrest.app/topic/dev%3A4401581)

Drop this in a README or blog post — it updates automatically as the score moves.