January Is the Performance Month, Whether You Planned It or Not
The new year is when websites get honest attention: holiday campaigns are over, budgets reset, and the analytics from December's traffic surge are sitting there, full of evidence about where your site struggled under load. Before that evidence goes stale, here are the performance priorities we are setting with clients for January 2026, in the order we would spend the month.
Priority One: Read December Before You Touch Anything
Holiday traffic is a free stress test. Pull the field data now: which pages slowed under real load, where mobile visitors bounced, which templates failed their Core Web Vitals when it mattered. December's Search Console and analytics are this January's work list, and they expire from memory faster than from the reports.
Priority Two: INP, the Metric Still Being Ignored
Nearly two years after INP replaced the old responsiveness metric, it remains the vital most sites fail and least sites work on, because the fix list is JavaScript discipline rather than image compression. Audit what runs on interaction: bloated event handlers, chat widgets, and the tag-manager payload that grew all year. The marketing-tag audit belongs to this priority: January is the natural moment to delete the pixels nobody claimed.
Priority Three: Ship the Modern Formats Everywhere
AVIF and WebP are universally supported and still not universally used. A format-and-sizing pass over your image library, plus dimensions reserved on everything, remains the highest ratio of Core Web Vitals improvement per hour of work available on most sites. If it has been on the someday list all year, it is a one-week project with permanent returns.
Priority Four: Re-Verify the Delivery Layer
Caching configurations drift: plugins update, rules expire, and the CDN and object cache that were tuned in 2024 may be silently misconfigured in 2026. Verify cache hit rates and test from a phone on cellular, not the office fiber, because that is where your customers live. Trust the instruments, not the impressions.
Priority Five: Set the Budget Before the Year Spends It
Performance decays by default, because every year adds features, tags, and content weight. The January move that protects the other four: set the page-weight and script budgets now, per template, and gate the year's additions against them. Sites with budgets end December fast. Sites without them end December with a familiar work list.
That is the month, honestly scoped. If you would rather hand it to a maintenance team that does this every January, ours is ready, and the December evidence is best read while it is fresh.
