Conffab’s Post

So You Want To Build A Browser Engine https://buff.ly/3XrQz0R If you’re building a browser engine from scratch just for fun, stop reading now and I wish you the best. If you want to build an engine that’s competitive with Chromium, and surpasses it in some respects, here’s my advice.Source: So You Want To Build A Browser Engine (https://buff.ly/3x3M7us)

So You Want To Build A Browser Engine https://buff.ly/3XrQz0R If you’re building a browser engine from scratch just for fun, stop reading now and I wish you the best. If you want to build an engine that’s competitive with Chromium, and surpasses it in some respects, here’s my advice.Source: So You Want To Build A Browser Engine (https://buff.ly/3x3M7us)

So You Want To Build A Browser Engine

I hate clickbait! But this one is for real: achieve a TTFB of 0 seconds! This merchant is doing so already for (3.7k/28k=) 13% of their pageviews. Easy win 🚀 However: → there's a lesson here though → even for this merchant that is doing great already → as they are missing out on another 7% of instant #TTFB An explanation of what you're seeing: → 𝐚𝐥𝐥 overall, the mobile 80th percentile TTFB is 346ms across 28k pageviews. We can agree on this being very healthy already 🤩 → 𝐧𝐚𝐯𝐢𝐠𝐚𝐭𝐞 22 out of 28k (78.5%) is navigating in a typical way (clicking links on webpages); → 𝐛𝐚𝐜𝐤_𝐟𝐨𝐫𝐰𝐚𝐫𝐝 this is users clicking on the browser's back/forward buttons. Still 131ms though. Because unfortunately, all server, JS & CSS stuff is executed once again in these cases. This applies to (2/28=) 7% of pagehits. Which is painful to see, as back_forward_cache is doing way better: → 𝐛𝐚𝐜𝐤_𝐟𝐨𝐫𝐰𝐚𝐫𝐝_𝐜𝐚𝐜𝐡𝐞 same as back_forward. But RUMvision is able to distinguish attempts where the browser was able to serve the whole page from a browser snapshot/cache. So, 13% led to a TTFB that we want: Instant 0 second TTFB 💪 And a huge #CoreWebVitals boost! 𝐓𝐡𝐞 𝐜𝐚𝐮𝐬𝐞 But what is causing the difference between back_forward and back_forward_cache behaviour in browsers? → Both your own code as well as #thirdParty #JavaScript could prevent pages from an instant TTFB → It's typically no-store HTTP headers or third parties using the unload event listener. 𝐓𝐡𝐞 𝐟𝐢𝐱 You only know how to fix, if you know what the bottleneck is. → One could use #Lighthouse / DevTools (via manual or automated tests). → But many Real User Monitoring cases is showing that it isn't the same for all pages, or maybe even all users 😬 RUMvision will help you identify your 0ms TTFB blind spots.

The power of bfcache is showing in Real User Monitoring with an impressive TTFB of ~0sec for back/forward navigation's restored from bfcache. BUT: Not only TTFB is improved by bfcache! bfcache also provides * A Smoother Browsing Experience * Reduced Server Load AND * Improved Core Web Vitals (CWV) Field Data: According to Chrome Developer Relations Team... ... "The bfcache is a significant browser-level performance optimization, and it entirely eliminates the layout shifts during page load, which for many sites is where most of their CLS occurs. The introduction of the bfcache caused the biggest improvement in CLS that we saw in 2022." Check here to see by how much CWV improved when bfcache was introduced in Chrome Browser: https://lnkd.in/gWPB4Q33 #Magento #webperformance #webperf #magento2 #magentodeveloper #magentodevelopment #magentoecommerce #corewebvitals #cwv #perfmatters

The power of bfcache is showing in Real User Monitoring with an impressive TTFB of ~0sec for back/forward navigation's restored from bfcache. BUT: Not only TTFB is improved by bfcache! bfcache also provides * A Smoother Browsing Experience * Reduced Server Load AND * Improved Core Web Vitals (CWV) Field Data: According to Chrome Developer Relations Team... ... "The bfcache is a significant browser-level performance optimization, and it entirely eliminates the layout shifts during page load, which for many sites is where most of their CLS occurs. The introduction of the bfcache caused the biggest improvement in CLS that we saw in 2022." Check here to see by how much CWV improved when bfcache was introduced in Chrome Browser: https://lnkd.in/gWPB4Q33 #Magento #webperformance #webperf #magento2 #magentodeveloper #magentodevelopment #magentoecommerce #corewebvitals #cwv #perfmatters

If you ever accidentally installed a weird browser toolbar, you’ve likely been the victim of browser hijacking. Though not as common as it once was, you can still run into hijackers, especially when downloading older software. In this guide, we answer the question "what is browser hijacking? and explain how to protect yourself. #Cloudwards #BrowserHijackingExplained #InternetSecurity101 🥷🏼 💻 👀

No wonder nobody has managed to create a nice way to preview, most websites pretty much block cross-site requests unfortunately. 😑 Here is my micro experiment, for certain things an <iframe> seems pretty good though: https://lnkd.in/dPAtNccy This extension actually does a pretty good job, but it's so close to basically opening a new tab... https://lnkd.in/dvtszM3q

#Diagram to illustrate the flow of the request created when you type https://www.google.com in your browser and press Enter. #DNSREQUEST

A lot of websites implement browser fingerprinting, using just a regular proxy (either residential proxy, data centre or even a VPN) is not enough. You need to use a scraping browser that can generate a proper "in the wild" browser fingerprint, that's where #brightdata's scraping browser wins https://lnkd.in/dT-Dp_N4 We just tested it with #trustpilot and it works great :)