avif
for web devs, front-end engineers
Why this scored 59
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity'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)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 175
JPEG XL vs AVIF for web use-cases
Compares JPEG XL and AVIF for web image performance and compatibility. · for web devs, front-end engineers
lobstersHeatingweb1h ago - 239
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. · for web devs, front-end engineers
devtoSteady 3 · nextjsweb60d ago