Barry Pollard

@tunetheweb.com

2991 Followers 434 Following

Web Performance Developer Advocate at Google Chrome helping to make the web go faster! All opinions my own.

Barleycove beach under a beautiful bright blue sky.
Your Results 73% Woke - 27% Chud 53% Techbro - 47% Neo-Luddite 78% Hopepilled - 22% Doomer 83% Davos - 17% Dubai Your Closest Match: Mark Carney
Firefox’s serial permission prompt picker. Asking the user which Serial Port to give access to.
What does rolldown's `minModuleSize` option do? In the context of Rolldown (the Rust-based bundler used by Vite), the minModuleSize option is a strategy used to prevent the creation of many tiny, inefficient files during the code-splitting process. It effectively sets a minimum threshold (in bytes) for how large a module must be to qualify for being split into its own independent chunk. How it Works When a bundler analyzes your dependency graph, it often identifies shared code that is used by multiple entry points. Usually, it would pull that shared code into a separate "vendor" or "shared" chunk. However, if that shared piece of code is extremely small (e.g., a 100-byte utility function), the overhead of the browser making an extra HTTP request to fetch that tiny file often outweighs the benefit of caching it separately. Below the threshold: If a module's size is less than minModuleSize, Rolldown will likely "inline" or merge that module into a larger chunk rather than letting it sit alone. Above the threshold: The module is allowed to be split into its own chunk if other conditions (like minChunks) are met.
Table of Core Web Vitals geographic breakdown ordered by number of origins showing how Core Web Vitals differ by country for a particular technology. For many technologies countries like Japan Germany, and the UK have much better Core Web Vitals than other countries like India and Brazil.
Screenshot of Chrome DevTools with a "Request #" column added
A slide with title: What's the future? And underneath: If you use a polyfill, do you have a removal strategy when the feature becomes part of your Baseline? If using an experimental feature, how are you tracking potential changes to it?
Block announced the layoffs in conjunction with its fourth-quarter earnings results. The payments company reported adjusted earnings per share of 65 cents on revenue of $6.25 billion, while analysts estimated 65 cents per share and $6.24 billion, according to LSEG. Gross profit increased 24% from a year earlier to $2.87 billion. For the full year, the company said it sees adjusted earnings per share of $3.66. Analysts anticipated $3.22 per share, according to LSEG.
// get all resources window.performance.getEntriesByType('resource') // only consider the blocking ones .filter(({renderBlockingStatus}) => renderBlockingStatus === 'blocking') // log their names .forEach(({name}) => console.log(name)) // Logs: https://your-site.com/styles.css
Screenshot of a performance trace in Chrome DevTools with a few additional "Nav*" and "LCP*" markers. Hovering over the "LCP*" shows this is a "Soft LCP" and in the Summary panel when you click on it you see "Soft Largest Contentful Paint" and a "Learn more about Soft Largest Contentful Paint" link.
Open Link in New Tab is now the 1st option again, the new Open Link in Split View is 2nd as sometimes you do want to see pages side by side to compare, and the rarer options of New Window and Incognito are 3rd and 4th respectively. As it should be.
Screenshot from HTTP Archive graph with notes on major changes showing URL corpus changes.
We usually see a high variability with the December data—we have seen the same every year since CrUX launched. Given the high variability it's difficult to attribute any of these moves to any particular causes and we expect most numbers to revert back next month (again as they mostly have in previous years). Therefore, we won't try to explain these movements this month.
70% Proportion of respondents having used lazy loading, the most-used feature among those with the “Newly Available” Baseline status.
Screenshot of Chrome DevTools performance panel with the 56ms INP event hovered showing the breakdown of that 56ms into 1ms Input Delay, 0ms processing duration, and 54ms presentation delay. Below, in the interactions log, you can expand any single interaction to see a similar breakdown.
An AI-generated abomination of an ice lolly with a wrapper with the React logo and "Modern Web Development" written on it, covering a Neapolitan ice cream ice lolly, with the bottom chocolate layer leaking out to a gooey puddle with the letters "RSC" written in sprinkles on top of the puddle. 11 extra lollypops sticks with AI written on them, have been shoved in, seemingly at random and for no real purpose.
A Christmas tree. With lights correctly placed on horizontally. And an ungodly amount of bubbles.
Chrome Canary includes paintTime and presentationTime are as part of LCP entries
Public transport option with Start and Save
Cloudflare's system status page appears to be served by AtlassianEdge in Amazon cloudfront according to their HTTP Headers
Save performance trace options: - Include annotations - Include resource content - Include script source maps - Compress with gzip
https://downforeveryoneorjustme.com/ is unavilable
Detail of the Chrome address bar with an AI Mode button that is rounded and it DOES match the padding of inline and block. Looks great.
Chrome with a split tab of BlueSky and Example.com, along with additional tabs for Google and bbc news
Chrome will also prevent speculations being used in certain conditions including: Save-Data. Energy saver when enabled and on low battery. Memory constraints. When the "Preload pages" setting is turned off (which is also explicitly turned off by Chrome extensions such as uBlock Origin). Pages opened in background tabs. Chrome also does not render cross-origin iframes on prerendered pages until activation. All of these conditions aim to reduce the impact of over-speculation when it would be detrimental to users.
3.2.1 is far and away the most popular with 786,512 origins, way about the next version (2.8.0 with 40,819)
Firefox now supports PerformanceEventTiming.interactionId, allowing developers to group related input events. This enables support for the Interaction to Next Paint (INP) responsiveness metric.
“Those who cannot remember the past are condemned to repeat it.” George Santayana
Chrome DevTools performance trace showing some custom tracks. Scheduler Custom Track including Blocking, Transition, Suspense, and Idle sub tracks. And Components custom track.
Screenshot of Core Web Vitals graph in Google Search Console, with the URLs greyed out. The Group LCP is 2.6 seconds and so the group is in amber and saying there is an issue as it's longer than the 2.5 seconds "good" threshold. Yet all the examples have green LCPs of 1.7 seconds, 2.4 seconds, 1.2 seconds...etc. which is confusing.
The Gartner Hype cycle staring with Technology trigger, quickly ramping up to the Peak of inflated expectations before crashing down in the Trough of disillusionment before raising back up in the Slope of enlightenment and then settling in a more realistic Plateau of productivity. We are here is marked WAY, WAY, WAY ABOVE the Peak of inflated expectations
Spice level drop down with: “Friendly (Unavailable)”, “Irritated (Default)”, “Monty Python (Silly)”, and “Scathing (Nuclear)” options.
Cookie banner which doesn’t claim they value my privacy but explains why they use cookies and offers “Accept All”, “Customize” and “Deny” buttons.
Join us in Google I/O Connect China white text on a black background with some imagery including a Panda and The Oriental Pearl Tower
Voss Gondola
Pretty little boat houses in Flåm
Snow on the mountains!
View of green fields under a blue sky framed by a train window.
Nyhavn canal area in Copenhagen
A laptop top with a slide deck, next to a cup of Barry’s tea.
Video showing the crowd goes back and back and back…
MASSIVE crowd at JSNation 2025 watching the opening talk by Sasha Greif
Sign for helvetia - without a ‘c’.
On July 8, 2025 Glitch project hosting and user profiles will be shut down. Your Glitch dashboard will remain available as usual through the end of 2025, with access to download all of your code for your projects, as well as a new feature to set up redirects for your project subdomains so your URLs keep working.
SEO failing audits show a lack of a meta description and a link without a descriptive text.
Up close to the Google I/O stage in Shoreline Amphitheatre
CLS of 0 in PageSpeed Insights
Google I/O logo
CrUX Vis graph showing CLS jumping up to “needs improvement” shortly after launch, and spiking recently, before plummeting back to near zero in last couple of weeks. A great result!
LCP for Duda sites outpacing the ALL line in last few months.
Cork being unnaturally sunny!
The rain in Spain falls mainly… where I am. For the whole weekend. 😔
Breaking down INP time into buckets of script, style & layout, paint, and unattributed.
The Chrome User Experience Report does not have sufficient real-world speed data for this page.
Live metrics screen from the Chrome DevTools Performance panel.
Teeny, tiny, history link in PageSpeed Insights.