Web performance report every week in your inbox.. ⚡ Sponsored by: @Catchpoint - @RealWebPageTest

Joined May 2021
WebPerformance Report retweeted
We enabled streaming for @Shopify storefronts. The layout head reaches the browser before the template finishes rendering. Median-store TTFB down 29% at p75, 21% at p90. FCP and LCP down 2–6%. No theme changes needed*. performance.shopify.com/blog…
13
12
5
77
9,177
WebPerformance Report retweeted
Announcing skillzero: save tokens by keeping skill names + descriptions out of agent context for skills you only use as /-commands. Experts like @addyosmani & @mattpocockuk all have mentioned this in the past: Don't accumulate skills you never use. You pay for them, they pollute context and make agents less reliable in actually using the ones you want it to use. skillzero changes this, as it allows you to split skills into: - 👻 hidden skills (the /-cmds) - 📚 collections (bundled by topic) - regular skills (stay in context) Of course open-source.
1
1
1
13
959
WebPerformance Report retweeted
Big one today — Tailwind is joining Shopify 🛍️
1,266
1,119
527
15,808
1,202,524
WebPerformance Report retweeted
By popular demand, I added a capabilities page to What PWA Can Do Today, which lists all capabilities on one page and indicates for each one if it's supported on your device. You can filter by support and search for capabilities. whatpwacando.today/capabilit…
2
5
71
5,875
WebPerformance Report retweeted
My Pixel Pioneers talk is on Youtube now! I give a brief introduction to page speed and then dive into different network throttling methods in Lighthouse, DevTools, and other tools. youtube.com/watch?v=KO02JZn_…
1
2
7
917
WebPerformance Report retweeted
I just added three new tools to the PWA Today MCP server 🚀 - list_pwa_audits - compare_pwa_audits - get_pwa_audit_entitlement You can now let your agent retrieve a list of your audits, compare two audits, and see the status of your plan. The PWA Today Runtime Audit tests your PWA under real-world conditions and finds issues before your users do 🧵1/2 pwa.today
1
3
12
791
WebPerformance Report retweeted
Software fundamentals still matter with agents because tradeoffs still exist. Agents will pick a tradeoff. Expertise is knowing the menu - latency, consistency, cost etc - and steering the agent to the one that's right for your system.
How have software engineering fundamentals changed with agentic coding? Here is our AI Engineering Skills map for software engineering fundamentals.
30
43
3
543
83,785
WebPerformance Report retweeted
Can recommend. I've made the switch at Framer: • Paint: 127ms → 0ms • RasterTask: 440ms → 0ms • Main-thread time: 276ms → 6ms • Compositor thread: 146ms → 351ms → work moves off main thread. this can improve INP too!
Text shimmer animations are usually very CPU intensive (~20% for one line of text). Animating background-position is not GPU accelerated, so the browser re-paints every frame. I found an alternative using a CSS mask which only animates a transform. Reduces CPU usage to < 2%. codepen.io/editor/devongovet…
5
8
1
292
48,772
WebPerformance Report retweeted
I’m thinking about banning Claude code at Shopify until they change their mind and read AGENTS.md and .agents/skills etc. Insisting on only reading CLAUDE.md sometimes leads to split brain problems when different team members use different tools. Just unnecessary.
978
911
491
19,451
2,296,715
WebPerformance Report retweeted
I launched pwa.today 🚀 The PWA Runtime Audit checks your PWA and finds runtime failures under real-world conditions. It checks installability, offline support, service worker lifecycle and makes sure you ship a PWA your users can trust. Check it out and let me know what you think! pwa.today
2
9
29
1,636
WebPerformance Report retweeted
CrUX data isn't 28 days old. It's two days old What takes 28 days is for the window to fully turn over, and that's why p75 sits still for two weeks and then drops all at once I wrote about it, with two interactive demos joanleon.dev/en/crux-28-day-… #WebPerf #CoreWebVitals #CrUX
2
4
543
WebPerformance Report retweeted
Want to access your page speed data with Claude Code? We've just published a guide on how to connect Claude Code to our MCP server. debugbear.com/docs/claude-co…
2
5
313
WebPerformance Report retweeted
He migrado un proyecto de Next.js a Astro. La diferencia de rendimiento de salida es importante.
38
38
6
1,112
176,910
WebPerformance Report retweeted
We enabled automatic addition of loading="lazy" for shopify.dev/docs/api/liquid/… 🚀 On pages using videos, we're seeing 75% reduction in downloaded files and 1.23MB/78% less data transferred! For now only in Chrome, but support in other browsers is coming.
1
1
8
578
WebPerformance Report retweeted
Every time a marketing pixel, growth experiment, or third-party script gets pushed into production without a clear performance budget, your company is effectively budgeting for slowness. Performance is a structural constraint every department must respect, not a downstream cleanup task for engineering. Stop accepting the drag: crystallize.com/blog/fronten…
1
3
84
WebPerformance Report retweeted
Elon Musk
@elonmuskJun 20
So true
Many people think any given ML project is 99% training. In reality, it’s 50% evaluation, 40% data cleaning, 8% integration, and 2% training. The first two set the noise floor for learning. No ML magic matters; the model cannot lower the noise floor, as that’s the optimal bound of Shannon encoding of your data. Thus, not a single day goes by without me thinking about ontology. Even the old labels have to be constantly reviewed.
2,105
3,441
124
39,327
17,095,357
WebPerformance Report retweeted
Pretty excited for our upcoming histogram upgrade!
1
3
134
WebPerformance Report retweeted
YoY growth rate of the top 10 websites in the world
1
4
2
24
3,954
WebPerformance Report retweeted
🆕 Introducing the MDN MCP server! Bring MDN's docs and browser compat data straight into your AI agent or IDE for accurate, up-to-date answers about the web platform. No more outdated guesses from training data. Learn more 👇 developer.mozilla.org/en-US/…
15
189
13
1,101
58,170
WebPerformance Report retweeted
Watch out! Chrome has a huge bug with <input type="number"> which causes values to change unexpectedly. It's fixed in Chrome 150, but that won't land until the end of June.
33
110
19
955
302,780