Web Platform Baseline in 2026 added a handful of smaller but genuinely useful features to the “safe to use” list: the lh and rlh units, the image-rendering property, and the SharedWorker API. None of them is a revolution on its own, but together they let you write less JavaScript and end up with faster, cleaner code.
lh and rlh units: no more manually calculating line height
The lh unit corresponds to the computed line-height value of the element it’s used on. That makes life easier whenever you need an icon, badge, or background to line up exactly with the height of a single line of text — a classic case is a badge next to a heading, or a highlight wrapped around a line. The rlh unit works the same way but refers to the root element’s line-height, similar to how rem relates to the root font size.
In practice, things that used to require JavaScript or pixel guesswork followed by fine-tuning can now be done in pure CSS: height: 1lh on an icon next to text will automatically adapt when typography changes. Less code, fewer re-renders, fewer layout shifts — a direct, measurable win for Core Web Vitals, which we covered when Google tightened its performance scoring.
image-rendering: crisp pixel art and QR codes, no blur
The image-rendering property controls the scaling algorithm used when an image is resized. By default, browsers smooth images, which is fine for photos but hurts pixel art, low-resolution icons, or QR codes, where blurred edges make things harder to read or scan. Setting it to pixelated keeps edges sharp even when scaled up — handy for stores selling retro game assets, generated payment QR codes, or thumbnails in an admin panel.
SharedWorker: shared state across tabs without a server round-trip
SharedWorker is a specialized background worker accessible from multiple browsing contexts at once — different windows, tabs, or iframes on the same origin. Unlike a regular Web Worker, which belongs to a single page, SharedWorker lets you coordinate state and tasks across multiple open tabs of the same app.
A typical use case: a store open in two tabs should keep cart contents in sync without hitting the server every time or relying on localStorage and polling. SharedWorker lets you keep a single source of truth in memory and push updates to every open window instantly — also useful for real-time notifications or a shared WebSocket connection you don’t want duplicated per open tab.
Why it matters for site performance
The common thread across all three features is that they replace JavaScript libraries or workaround solutions with native, browser-optimized functionality. Fewer downloaded libraries means a smaller JS bundle, faster parsing, and less main-thread work — exactly what metrics like INP, which we covered alongside WordPress performance and PHP 8.4, are designed to measure. “Baseline 2026” also means these features work across current versions of Chrome, Edge, Firefox, and Safari, so you can ship them without polyfills.
Where to start
The easiest entry point is wherever you’re currently using a JavaScript workaround purely for line-height matching or cross-tab state, and testing whether pure CSS or SharedWorker can replace it. For production projects, verify support via caniuse.com or web.dev/baseline directly, and phase out workaround solutions gradually as part of normal refactoring rather than all at once.
What this means for real projects
A concrete example: a cart-count badge next to an icon, which used to require recalculating in JavaScript on every font-size change or breakpoint, can now just be styled with width: 1lh; height: 1lh; and you’re done — responsiveness is built in. Similarly, in a store’s internal admin panel showing thumbnails of product codes or generated payment QR codes, adding image-rendering: pixelated to enlarged previews instantly improves readability without generating separate higher-resolution files.
With SharedWorker, it’s worth remembering that cross-browser support has historically been uneven — Baseline 2026 status means current versions of all four major engines now support the API, but sites with a very conservative audience (older enterprise browsers) should verify real penetration among their visitors before relying on SharedWorker as the sole solution.
Conclusion
Baseline 2026 reinforces a trend that’s been building for years: browsers keep taking over work that used to require JavaScript libraries. For developers, that means smaller, faster, more maintainable code. Want to find out where your site is carrying unnecessary JavaScript weight? We’d be happy to run a performance audit.
