Skip to main content

🕹️ Chrome DevTools MCP - A Technical Deep Dive

· 14 min read
卤代烃
微信公众号@卤代烃实验室

cdm-hero.jpg

On September 23, 2025, Google released Chrome DevTools MCP, currently at version 0.9.0. Google positions it as an assistant for AI coding agents to handle debugging and performance testing, improving web development debug capabilities. See the official blog for use cases: Chrome DevTools (MCP) for your AI agent.

This post analyzes Chrome DevTools MCP's implementation by examining the source code and MCP output, exploring its capabilities and limitations.

⚡️ [Performance Optimization] How to Efficiently Get Meta Information from Base64 Images

· 9 min read
卤代烃
微信公众号@卤代烃实验室

get-base64-image-meta-info-hero-image.jpg

Hello everyone, it's been over a year since my blog was last updated. I guess the SEO ranking has dropped completely, and I don't know how many people will see this in the end.

Starting from May last year, due to organizational structure changes at work, I shifted from the performance optimization field to AI. Due to confidentiality agreements, I can't say much about the specific content, so I haven't updated for a long time. This year, my work direction has changed again, mainly focusing on GUI Agent work.

A year has passed, but the programming field has undergone earth-shaking changes. With the launch of tools like Cursor/Claude Code, everyone has basically broken free from the constraints of traditional programming methods (let's not worry about whether the generated code is correct, just ask if it's fast or not); many departments are not satisfied with the efficiency gains from external programming tools and have started building their own internal Agents, attempting to double efficiency in both business and engineering. Since my recent work involves more collaboration with large model teams, I feel this more deeply, and I'll have opportunities to share my insights slowly in the future.


⚡️ [Performance] How the browser optimizes resource downloads with HTML Preload Scanner

· 8 min read
卤代烃
微信公众号@卤代烃实验室

html-preload-scanner-hero-image.jpg

Hello everyone, I am skychx, specializing in performance optimization.

When doing web-related performance optimization, it is necessary to have a certain understanding of the underlying principles of the browser, so that the page can better walk on the happy path. Today, let's understand a browser default performance optimization scheme that is rarely known by people - HTML Preload Scanner, and see how it optimizes the loading speed of network resources.

⚡️ [Performance] Three ways to observe network performance data in the browser.

· 7 min read
卤代烃
微信公众号@卤代烃实验室

observe-browser-network-hero-image.jpg

Introduction

There are various ways to observe network performance data with the browser's Devtools tool, but these data are presented in different ways. This article is to interpret these performance data presentation methods and make a longitudinal comparison to help more people optimize the performance problems brought by the network.

🛠️ [Hybrid App Dev] How to Locate the JS Code Injected into Hybrid Web Pages by Native

· 6 min read
卤代烃
微信公众号@卤代烃实验室

find_inject_js_hero_image.jpg

A webpage can not only run on public browsers, but also on the WebView component within the APP. Since these Hybrid Web pages run in a relatively closed environment, the APP itself can inject some JS code into WebView, making targeted enhancements to the Web page (the most typical application is JSBridge, which provides a bridge for Web <--> Native communication).

🪢 [Network Protocol] A Brief Discussion on the Evolution of HTTP Priority Algorithms

· 8 min read
卤代烃
微信公众号@卤代烃实验室

http_%20prioritization_hero_img.jpg

A couple of days ago on "Jike," I spontaneously wrote a brief history of HTTP priority development. I felt it was too rushed at the time, so I decided to write a blog to expand on it, analyzing the concept of "priority" longitudinally to see the development and evolution of these fundamental protocols.


⚡️ The Cost Of JavaScript (2017 - 2023)

· 8 min read
卤代烃
微信公众号@卤代烃实验室

ybsbny.png

Rant Time

I don't know when it started, but frontend development began to compete on "high-end knowledge," constantly bringing up browser underlying principles and how V8 works. It's not that these topics are useless, but the trend suggests that if you don't understand these things, you can't even build a simple webpage.

In my work, I've collaborated with kernel teams and VM teams and consulted them about these related issues. Their attitude is very clear: when facing large-scale engineering projects with tens of millions of lines of code, even as professionals, they don't understand everything. If you happen to meet someone who truly understands everything, they definitely wouldn't be doing frontend work. This makes the "eight-part essay" battles between interviewers and candidates seem ridiculous.

So if you really encounter scenarios that require learning related knowledge, or you're simply personally interested in understanding the principles and details, what's the best approach? It's simple: directly read the blogs or talks from relevant teams or core developers. This is first-hand information, aside from the source code itself, and the quality is much higher than those second-hand dealers.

🔄 Adjusting Blog Content Direction

· 4 min read
卤代烃
微信公众号@卤代烃实验室

I haven't updated my blog much in the past two years. Looking back since 2022, I've only published 5 posts (though that wasn't many before either), which is far below my own expectations. Actually, I've written some technical documents and articles internally at my company, but due to length limitations and sensitivity concerns, none of them were made public, which is quite a pity.