How well do you know common #webperf metrics? For example, did you know...
💡 INP is only available in RUM and not supported in Safari?
💡 LCP is not reliable in SPAs?
💡 User Timing is available across all browsers?
Test your knowledge: https://www.speedcurve.com/web-performance-guide/glossary-of-web-performance-metrics/
Page Speed Benchmarks tracks top travel sites in the EU and UK, including Trivago, Airbnb, TripAdvisor, Priceline, Skyscanner, and more.
While it was great to see our friends at Trivago with a 2.5s LCP time, many other sites struggled with:
🐌 Slow/blocking JS & CSS
🐌 Non-performant custom fonts
🐌 Excessive JS before the LCP element
https://app.speedcurve.com/benchmarks/europe/travel/slow/largest-contentful-paint/
The latest issue of Speed Matters is out! If you're not a subscriber yet, you can read it in its entirety here (and if you like it, sign up to receive next month's edition in your inbox).
We ❤️ this new open‑source Magento module from @jesperingels and the team at Bluebird Day! Integrate real user monitoring into your Magento project in minutes:
https://github.com/bluebirdday/speedcurve-magento
🚀 Enter SpeedCurve RUM ID & the script loads automatically
🚀 Insert RUM script only after the visitor accepts cookies (privacy‑proof!)
🚀 Track Core Web Vitals & other RUM metrics
🚀 Measure impact of #webperf on your business
🚀 Fight regressions with budgets & alerts
🚀 Get diagnostics
Hey friends! I'm so stoked to be talking about the intersection of site speed, user experience, and business outcomes at @webexpo in Prague later this month!
Use the promo code TAMMY25 to get a 15% discount on your pass.
Info + tickets: https://webexpo.net/prague2025/sessions/connecting-the-dots-between-site-speed-user-happiness-business-success/
Is CrUX the same as RUM? We get this question a lot!
This short article breaks down the differences. (The biggest distinction: CrUX is only collected from Chrome browsers, so you could be missing a lot of traffic.)
https://support.speedcurve.com/docs/speedcurve-rum-vs-crux-data
0.52% of Chrome users use versions that are between 5-10 years old. Doesn't sound like much? There are an estimated 3.5 billion Chrome users worldwide, so 0.52% of that is more than 18 million people. That's a lot!
Learn more about this and five other factors – which you have no control over – that slow down user-perceived performance of your site: https://www.speedcurve.com/blog/six-things-page-speed-user-experience/
Delivering a fast, consistent online experience boosts every metric retailers care about – from conversions and revenue to retention and brand perception. This guide covers how to...
💰 Measure the impact of page speed on your business
💸 Benchmark your site speed against competitors
🛠️ Find and fix what's slowing down your pages
https://www.speedcurve.com/web-performance-guide/web-performance-for-retailers/
Ever wondered why your business and engagement metrics didn't improve after you sped up your pages? You need correlation charts.
👍 Validate your #webperf & #UX metrics
👍 Identify your site's "performance plateau"
👍 Spot performance-blocking trends on your pages
https://www.speedcurve.com/blog/site-speed-business-correlation/
We ❤️ our customers! Check out these case studies and find out how companies like Pinterest, Trivago, Airbnb, Zillow, BBC, GOV.UK, and The Guardian have used us to monitor their #UX and #webperf, speed up their sites, increase user happiness, and improve their business!
www.speedcurve.com/customers/
Byte for byte, no resource affects page speed more than JavaScript. This guide walks you through essential techniques for reducing the negative impact of JS on your pages.
https://www.speedcurve.com/web-performance-guide/best-practices-for-optimizing-javascript/
Slow-loading pages could have 2X more impact on revenue than site outages. Are you at risk of prioritizing one performance issue (downtime) over another equally critical issue (slowness)?
This post covers how to:
👉 Calculate losses due to site slowdowns
👉 Compare those losses to downtime losses
👉 Estimate lost customer lifetime value
Users will abandon your page if it appears empty and inactive for more than 3 seconds. If they see content rendering or the skeleton of a page loading, you'll buy more time and patience.
Here's how to do it: https://www.speedcurve.com/web-performance-guide/using-critical-css-for-faster-rendering/
The median web page is 8% bigger than it was a year ago. How does this affect your page speed, your Core Web Vitals, your search rank, your business, and most important – your users?
Latest page bloat trends and analysis: https://www.speedcurve.com/blog/page-bloat-2025/
Some key findings:
Median page ⬆️ 8%
Median JS ⬆️ 10%
Median image ⬆️ 5%
Median video ⬆️ 17%
#webperf #webperformance #ux #sitespeed #pagespeed #javascript #js
We ❤️ our customers! Check out these case studies and find out how companies like Pinterest, Trivago, Airbnb, Zillow, BBC, GOV.UK, and The Guardian have used us to monitor their #UX and #webperf, make their sites faster, and improve their business!
Few things frustrate me more than feeling like I've done everything right, but nothing got better.
Say you've done all the right things. You've lazy-loaded and compressed and minified. You've seen improvements to Start Render or LCP or INP. But bounce rate didn't improve. Neither did conversion rate or any other business metric you care about. WHY???
The answer might lie on the performance plateau.
"I made my pages faster, but my business and user engagement metrics didn't change. WHY???"
https://www.speedcurve.com/blog/web-performance-plateau/
(I just realized my original post about why – and how – to measure the performance plateau for your site was a couple of years old, so I've refreshed it with new info!)
After I shared the latest results from SpeedCurve's Industry Page Speed Benchmarks, a number of folks asked me how to create their own competitive benchmarking leaderboards. The good news: you can do that very easily in @speedcurve!
Here's a quick demo: https://support.speedcurve.com/docs/competitive-benchmarking
Why did The Guardian take top spot in our Media Page Speed Benchmarks? Because the main image was the fifth request on the page.
Calling the LCP element early seems like a no-brainer, right? Yet too often, I see it called MUCH too late.
Page Speed Benchmarks: https://app.speedcurve.com/benchmarks/europe/media/slow/largest-contentful-paint/
The Guardian's test details: https://app.speedcurve.com/benchmark/media-eu/test/250409_0T_8f9f8f17b7462666b1e6fe8f04d444c2/?share=freljsuj6913s9s5an29pktz92alec
Yesterday we shared the Media Page Speed Benchmarks for the US, so now we're sharing the latest results for the EU/UK. While it's great to see our friends at The Guardian had an LCP time of just over 2 seconds, unfortunately 12 out of 14 sites failed to meet Google's 2.5 second threshold.
👉 Explore the benchmarks: https://app.speedcurve.com/benchmarks/europe/media/slow/largest-contentful-paint/
