Search results
  1. How to rock your performance? 🔥 Largest Contentful Pain(t) (LCP) is a metric that measures loading time. It's one of three Core Web Vitals and affects SEO so it's important to have it under control! Here's everything you need to know about it!

    Show this thread
  2. You can use this code to quickly find image optimization quick wins in your app! The below snippet will show a red border around images without width and height that cause layout shifts and around the ones that are not loaded lazily.

  3. 15 Oct 2021

    - Afficher une image sur le web VS - Bien afficher une image sur le web

    Show this thread
  4. Mar 17

    📢 We are excited to announce that will be our next guest on WebPageTest LIVE! Join us for an interactive deep dive into sites, hosted by our own . RT! ⚡️ 📆: March 24th ⏰: 1PM EST ⏰: 🌐 📺:

    a picture of two developers' avatars.
WebPageTest LIVE!, March 24th, 1PM EST
twitch.tv/WebPageTest
  5. Mar 18

    ✨ Next Tuesday! (an hour earlier than usual) ✨ CI creator is joining the stream to show off best practices for debugging our ! 📍 ⏰ Tue, March 22 at 1pm Central 📅 Add to calendar:

    Debugging Web Performance, with Patrick Hulce and Ben Myers. Tuesday, March 22 at 1pm Central.
  6. Mar 18

    Put your hands up if you are not surprised by this 🙋 See how Key Medium can help avoid the pain at ---

  7. Mar 2

    Today's pro tip: don't lazy load LCP images! This one crept in on one of my client's sites, discovered because LCP started creeping up on a key template.

  8. Feb 10

    How much JavaScript is your app adding the Shopify merchants' storefronts? We added a size limit test to Incentivize's bundle. We're committed to under 15kB 🚀 is important. Stay fast.

  9. Do you have performance checks in your CI/CD pipeline? If you do - what checks do you have?

  10. Mar 9

    🆕 Introducing support for responsiveness metric! It's the next step to measure interactivity on the web. Check how well your website handles user inputs: Thread with details & examples ↓

    Show this thread
  11. Mar 11

    Week 1 done onboarding Thanks to everyone 4 making me feel so welcome and looking forward to getting started at making commerce fast for everyone! If anyone in my network is interested in doing some really meaningful work in reach out, I'm hiring!

  12. Feb 16

    Survivorship bias in - why your data may be lying to you and why FCP is a key metric to optimise for. Slow users are more likely to abandon a visit, biasing your analytics towards fast experiences.

  13. 🚀 tip: A common cause of too high CLS (Cumulative Layout Shift) is the silly mistake of not setting "width" and "height" for your images. Always set both for <img> tags and see how your CLS is improving!

  14. Feb 4

    same exact video after ~40s of watch time. ~3x less CPU (19% vs 7%), ~4x less heap size (200mb vs 60) and DOM nodes (8k vs 2,5k). I can't wait to release the new video player!

    video player performance screenshot from chrome, before/after
CPU 19% vs 7%
JS heap size 200mb vs 60mb
dom nodes 8k vs 2,5k
  15. 6 Oct 2021

    Welcome to my TED talk

  16. Mar 3

    We love 💍 too Gatsby! Now let's see who shines! awarded prizes from two jewellers, so we had them side by side comparing their SPEED INDEX aka their visual progression. This is what it looked like: mobile, 4G. (thread 🧵)

    Show this thread
  17. Feb 8
  18. Mar 18

    Keeping an eye on Core Web Vitals is well... vital. Did you know you can access your Web Vitals data in several ways using WebPageTest?? here's a QUIC CLIP on how you can. Sign up for a free account:

  19. Jan 10

    question for my chums: is there a threshold below which it generally makes sense for a stylesheet to be a <style> instead of a <link>? obviously 'it depends' but in the 90% case, if a page needs 5kb.css, 50kb.css and 500kb.css, should you inline the first? the first two?

  20. Mar 5

    A good tip of fetching only critical resources can be to minimize the impact of media queries by modularizing specific styles for particular screen size in a separate file and only load when required like so:

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.