Why is lazy loading important for mobile?

🔥 Firefox now supports the Interaction to Next Paint metric! INP measures how quickly websites respond to user input. Previously it was only available in Chromium-based browser like Chrome and Edge. Check it out in our real user monitoring data: https://lnkd.in/e4b7YQRp

Browsers are getting way smarter! 🧠 https://lnkd.in/eUyV-zkS And one of these 5 might just become your new default. In our latest video, we break down what each browser does well (and where it falls short), so that you can figure out if one of these is worthy of becoming your go-to.

Running statistics comparing when a browser extension is reported malicious/suspicious compared to when it is removed from the Chrome Web Store. Here is the breakdown: Still active: 68.8% 91-365 days: 19.1% 31-90 days: 5.8% Same day or 1 day: 2.9% 8-30 days: 2.3% 2-7 days: 1.2%

Handy little Tool in the Devtools of Google Google Chrome, Firefox, Brave and all the others based on Chromium. I showed it yesterday during the livestream. Press F12 for the Devtools and you can set the Throttle speed under Network. Why is it for? You can see how your page would be loaded under different internet speed assumptions. While it may be getting phased out, last time I looked for studies 1 in 5 mobile users still had an equivalent of 3G as their internet connection. This way, you can test when is what loaded, how does it feel, and so on for your website.  (Thanks as usual to Google for Developers for implementing all these cool little things)

Agents in a terminal: powerful, but niche. Agents running a web browser: look out, world. Caveat -- it has to work ... https://lnkd.in/eGHCnMvm

Need to inspect web traffic/API requests? Too much noise from unrelated apps when debugging your API integration? Requests from every process slow you down and clutter your logs. With Dev Proxy, you can intercept requests from only the processes you care about. Filter by process name or PID to focus your workflow. Spend less time searching for the right requests. See only the traffic you want, so you can debug faster and avoid distractions. Here's how to do it: https://lnkd.in/eZ7r-t9H

Focus Search v2.0 is OUT! 🎉 After literally thousands (okay… tens) of emails, I’ve finally added the one thing people kept asking for: custom key binds to focus the search input. “Why the delay?” I hear about 11 of you cry… Well, because it worked perfectly on 𝙢𝙮 machine… No really, I was that lazy. So what changed? Shortly after Google featured my addon, Chromium browsers decided that CTRL + SPACE should focus the 𝙗𝙧𝙤𝙬𝙨𝙚𝙧 search bar by default - which just so happened to be the exact same shortcut my add-on was using to focus a websites search bar, ultimately breaking the addon. Coincidence? Or are they after my idea 👀 Anyway, you can now pick any two keys you like to trigger the magic. Just click the extension icon and select “Set Custom Shortcut”. Get the latest version now on the Chrome and Mozilla extension store. Well, back to it then…

The next generation of browsers will fundamentally change how we interact with the web. If you want to try for yourself, Comet by Perplexity is a good and mostly free way to start. Here's my latest column on the advantages of agentic browsers.

Metadata can be understood as the secret instruction you give to a web browser. These instructions help the browser understand how to show your website ,who made it and even what it's about.#ALX_SE, #ALX_BE, #ALX_FE, #ALX_PDFE, #ALX_PDBE

Is your website slow, and you want to understand why? Here’s how the PerformanceObserver API can help you 👇 1. What is the PerformanceObserver API? The PerformanceObserver API allows you to monitor your website's performance directly in your code. It observes performance events in real time: - resources, - user interactions, - page loading. 2. Why use it? Browser tools are limited to manual testing. This API collects real user data and enables dynamic optimizations. 3. A concrete example Listen to "resource" events. Then, identify images that take more than 500ms to load. Next, adjust your site to reduce those loading times. 4. Browser support This API is supported by all major browsers (Chrome, Firefox, Safari, and Edge), covering 94.93% of users. 5. In summary You move from manual debugging to automated data collection. It's the best way to ensure optimal performance. Have you already used PerformanceObserver? Share your experience in the comments!