SpeedCurve

"Death by a thousand cuts." That's the cumulative impact of unoptimized and unnecessary JavaScript on your site. Every third-party script you add to your website should ADD value, not take it away. Too many scripts can turn into a #webperf and #ux nightmare — hurting important metrics like Largest Contentful Paint and Interaction to Next Paint. And slow LCP and INP directly correlate to worse bounce rates and conversion rates. I dug into this topic in a recent post, where I compared the performance of a handful of campaign landing pages for well-known sites, from Apple to Uber. 👉👉 See how these landing pages compared: https://lnkd.in/grzNXtDK I also did a deeper analysis of one landing page in particular. What I found was a bit terrifying... 😬 Largest Contentful Paint was more than 9s 😬 400 resource requests before LCP 😬 Total #JS weight was 4,176 KB 😬 330 JS files, including Google Tag Manager, Google Ads, Tiktok, Reddit, Facebook, Pinterest, Criteo & Amazon 😬 Most third-party calls happened before LCP — in other words, in the critical rendering path 😬 Some third parties, such as Google Tag Manager, incurred a huge performance penalty (GTM called 13 resources and had a total Long Tasks time of 497ms; any task greater than 50ms is a cause for concern) 👉👉 Learn how to audit the third parties on your pages, prevent regressions, and hold your vendors accountable: https://lnkd.in/dFFmtTVX 👉👉 Best practices for optimizing JS: https://lnkd.in/d-De7wcJ The landing page I analyzed is part of a #Shopify store. (To be clear, not all Shopify stores are slow! Scroll down for more on that.) They'd implemented a number of Shopify plugins that delayed rendering, including: • Klaviyo – 43 requests, total Long Tasks time of 432ms • Swish – 20 requests • Intelligems – 12 requests • Gladly – 9 requests • Friendbuy – 2 requests The irony is that many of these plugins are meant to INCREASE conversions. The issue isn't necessarily with the plugins themselves: it's with their implementation. If a service isn't needed early in the page's life cycle, it shouldn't be part of the critical rendering path. 👉👉 Not all Shopify stores are slow! check out Sia Karamalegos's roundup of the fastest Shopify themes in 2025: https://lnkd.in/dTuW-eG6 👉👉 Find out how to easily start monitoring the speed of your Shopify store, including measuring the impact of page speed on business metrics like conversion rate: https://lnkd.in/dAR_YURN 👉👉 And learn how to build fast pages that stay fast: https://lnkd.in/grzNXtDK

I've been exploring SpeedCurve's new Vitals Overview dashboard with some customers for a week or so now, and all I can say is WOW. Not only is this dashboard fun to play with, I'm already finding that it cuts down the time it takes to investigate issues by at least half. 👉👉 Take a quick dashboard tour – https://lnkd.in/gyVFfTbU Some highlights... 🔥 High-level overview showing 75p performance across all your Vitals: TTFB, FCP, LCP, INP, TBD, and CLS 👈 Spot the non-TLA in this list! 🔥 Heatmaps that break down performance across dimensions: page, device, browser, and location 🔥 From the heatmap, you can quickly drill down into hotspots to get deeper page-specific waterfalls and diagnostics 🔥 More signal, less noise! You'll see a low-sample data warning that flags when sample sizes are small, so you don't waste time chasing red herrings Questions? Want your own guided dashboard tour? Let me know!

We’re excited to announce the launch of the Vitals Overview dashboard in SpeedCurve — your new starting point for exploring the performance of your site. When it comes to improving web performance, the journey usually looks like this: Our new overview...

One of the most common things I hear every fall is FOMO from all the folks who missed out on attending performance.now() conference. 😢 Don't let this happen to you! We have an AMAZING speaker lineup who will be covering all the #webperf topics you should care about these days: ✅ JavaScript & CSS ✅ the newest performance APIs ✅ best practices, tools & workflows ✅ making performance allies throughout your company ✅ measuring perceived performance ✅ teaching LLMs to interpret data ✅ performance & accessibility ✅ Core Web Vitals (and beyond) Get your tickets soon! 👉 https://perfnow.nl/

A Smarter Way to Spot Performance Issues

Retail ad campaigns are expensive! If you've ever done media buying for a retail site, you know how much it costs to buy all those Google ads, print ads, and other promotions. You're putting a lot of money into getting people to your landing page. Yet all too often, those landing pages are the slowest pages on your site. 😢 And that slowness has a direct impact on conversions. 💸 So the question is: Why does this keep happening? And more important: How do you fix it? 🔎 I recently tracked the rendering times of campaign landing pages for 19 leading sites — including brands like Apple, IKEA, Nike, Casper, Nordstrom, and REI — to see how they compare. Find out who’s fast, who's slow, and what's causing their page speed bottlenecks. This post covers: 👉 Why the speed of your campaign landing page matters 👉 Why performance issues on landing pages often go unnoticed 👉 Common performance issues on landing pages 👉 A deep dive into the landing page for one of the sites I tracked 👉 Who should be responsible for the performance of landing pages on your site? 👉 How to make sure your pages stay fast https://lnkd.in/grzNXtDK

How do the campaign landing pages of leading websites compare? Who's fast, who's slow, and what's causing their page speed bottlenecks?

🔥 Quick site speed tip! Is your page a SPA? Then the biggest issue slowing down your site is probably #JavaScript. Here's how to fix it. Single-page apps (SPAs) have unique page speed challenges. SPAs usually require the user to download more #JS on the initial page load. Not only do they need the JS for the current page, they also need the JS that handles *transitioning* between pages. ⚡REDUCE the amount of JS on your pages — Remove unused JS. Code-split and/or minify the rest. ⚡⚡ RENDER page content on the server where possible — This can improve important metrics like Largest Contentful Paint (LCP). ⚡⚡⚡ PRELOAD resources the user is likely to need — For example, you could start loading resources when the user hovers over a link or button, rather than waiting for them to click it. 👉 Get more SPA optimization tips: https://lnkd.in/gYEEDtGn

What do the most successful websites have in common? They all have a strong culture of web performance and usability. But it can be a challenge to educate, incentivize, and empower everyone in your organization. That's why #webperf is more than just a technical challenge — it's a cultural challenge. (In other words, it doesn't matter how awesome your tools — e.g. SpeedCurve — are. Awesome tools are just the beginning. You need shared goals and consistent processes.) Having a strong performance culture is virtually the only way to stop page speed regressions from creeping in. The most common causes of regressions: 😕 No front-end measurement 😟 Constant feature development 😧 Badly implemented third-parties 😢 Waiting too long to tackle performance problems 😭 Relying on performance sprints Solutions? 👀 Make performance visible throughout your organization 📈 Tie site speed to business outcomes ⚖️ Collaborate on performance budgets 🎊 Score some easy early wins to increase buy-in 🔁 Repeat! 👉👉 Proven best practices to help you create a healthy, happy performance culture: https://lnkd.in/g5aD-GQH

Progressive enhancement design for the UI is one of the critical points in making "page onboarding" smooth and enjoyable. Critical CSS and good CSS bundling in general can push the boundaries of what's possible. I've made some 10K versions of pages that show up quickly, give users visual hints to orient themselves on the page and get ready to consume the content once it finally arrives. Here's an article for skeletal designs that Alex Chernyshev and I wrote for Speed Patterns site: https://lnkd.in/euFQXd79