Monitor page speed and Core Web Vitals in the lab and with real user data.
London, England
Joined July 2018
- Tweets1.5K
- Following263
- Followers2.4K
- Likes537
DebugBear retweeted
The new agentic browsing checks are now live on PageSpeed Insights!
Learn more: debugbear.com/blog/lighthous…
DebugBear retweeted
Google announced the new Lighthouse agentic browsing category at Google I/O yesterday! It validates WebMCP integrations, LLMs.txt files, and if the accessibility tree is readable, ...
Test your own website here: debugbear.com/test/website-g…
DebugBear retweeted
Technical SEO Checklist: The Complete Guide For 2026 - debugbear.com/blog/technical… from @mjcachon
DebugBear retweeted
We've built over 10 different free tools at DebugBear! Added some screenshots and tidied up our listing page recently: debugbear.com/tools
DebugBear retweeted
How do you get customers to find your online store?
We just published an in-depth guide by @mjcachon on ecommerce SEO, covering everything from keyword research to site architecture and performance optimization.
Check it out here: debugbear.com/blog/ecommerce…
DebugBear retweeted
Added a new request stats view to the DebugBear page speed test result!
Try it for free here debugbear.com/test/website-s…
DebugBear retweeted
✨ SPDY STREAM 018 ✨ TODAY, we have
@mattzeunert from @DebugBear! He recently penned an piece for @smashingmag about the importance of metric monitoring + effectively collecting #CoreWebVitals. We're chatting live later today
📆 TODAY!
⏰ 1pm EST, 7pm CET
🔗 youtube.com/live/VfPX9G5cahw…
DebugBear retweeted
There are lots of tips for improving your website performance. But even if you follow all of the advice, are you able to maintain an optimized site? And are you targeting the right pages?
↬ Matt Zeunert outlines an effective strategy for web performance optimization and explains the roles that different types of data play in it: smashingmagazine.com/2025/11…
(This article is supported by @DebugBear 💖)
DebugBear retweeted
📕 Partytown: Optimize Third Party Scripts with Web Workers
👉🏻 Third-party resources often weigh down websites and can be tricky to fine-tune for performance.
debugbear.com/blog/partytown…
DebugBear retweeted
Test TTFB From Multiple Test Locations
debugbear.com/test/ttfb
by @DebugBear
DebugBear retweeted
Small Details, Big Impact on Web Performance
During a recent web performance audit, I came across an interesting case:
1️⃣ A favicon.ico that redirected (301) to another URL with a language parameter
2️⃣ The final URL didn’t exist, returning an uncompressed 13 MB HTML page
It might seem like a minor issue, but the impact is real:
- Unnecessary extra requests
- Downloading data with no value to the user
- Longer load times
Takeaway: Reviewing static assets (favicons, images, CSS, JS) and their paths can save bandwidth and improve user experience. Sometimes, performance bottlenecks hide in the smallest, most unexpected places.
#WebPerf #WebPerformance #Frontend #DeveloperTips #UX #WebOptimization
ALT A screenshot of a web browser's developer tools, specifically the network tab, showing the details of a network request for a "favicon.ico" file. The view is split into two main sections. The left section, under the "Request" heading, details the HTTP GET request, including the URL https://www.**********/favicon.ico (with the domain name obscured). The right section, under the "Response" heading, shows the server's response details. The highlighted information includes "Status: 200", "Transmitted Size: 1.19 MB", "Full Size: 13.0 MB", "Content Type: text/html; charset=utf-8", and "Request Duration: 3.46 s".
DebugBear retweeted
Ever wondered how to make the useAsyncData calls in @nuxt_js more efficient and performant?
Check out my article for @DebugBear where I show just that!
debugbear.com/blog/nuxt-usea…
DebugBear retweeted
I'm a big fan of @DebugBear. debugbear.com/test/website-s…
Handy to see all your attributes in the waterfall, such as fetch, preload, LCP, defer, async, etc.
DebugBear retweeted
Really good read, the full spectrum of perf work is sometimes a bit opaque. But there are ways to fix that.
Unified metrics is one of my favorite strategies. And using ServerTimings kinda like a secret weapon. – at Stockholm, Sweden
Over time, front-end performance in the browser has become more and more important.
But websites still can't be fast without a high-performing backend!
Our new article explains what that means for developers and organizations.
debugbear.com/blog/performan…
DebugBear retweeted
I thought the browser console was simple... I was wrong 🤯
It's actually packed with hidden features:
🖼️ Logging images
✨ AI explanations
🥹 Logging tables
🔧 Console utilities ($0, $_, ...)
🔎 Advanced filters
🔥 Live expressions
New article below!
debugbear.com/blog/chrome-br…
DebugBear retweeted
📊 Struggling with a slow Largest Contentful Paint (LCP)? Newly introduced by Google, LCP subparts help you pinpoint where page load delays come from. Now included in the Chrome UX Report, this data provides real visitor insights to speed up your site and boost rankings.
↬ Matt Zeunert unpacks what LCP subparts are, what they mean for your website speed, and how you can measure them: smashingmagazine.com/2025/03…
(Article is kindly sponsored by @DebugBear 💖)
DebugBear retweeted
📢 The Chrome DevTools flame chart has just become *much* easier to use.
I wrote about these new features (for DebugBear), and other new DevTools features you probably didn't know about.
debugbear.com/blog/favourite…
DebugBear retweeted
Compare how your website looks with and without JavaScript
debugbear.com/test/noscript/ by @DebugBear
#WebPerf #PerfTools #PerfDebugging
ALT Compare how your website looks with and without JavaScript screenshot
DebugBear retweeted
CSS Weekly #605
🚀 Optimizing The Critical Rendering Path
😶🌫️ Focus by Negation Effect
🔎 Dynamic Focus Zoom Effect
🌄 How to Favicon & Gif in 2025
Featuring @mattzeunert, @KevinJPowell, @sitnikcode, @hypeddev, @geoffreygraham, @tahazsh, @jh3yy.
cssw.io/issue-605
DebugBear retweeted
LCP and INP are part of Interop 2025!!!!
web.dev/blog/interop-2025?hl…
Will be fantastic to see broader browser support for the underlying APIs needed to calculate these metrics. At the moment there is a big blind spot when only Chromium-based browsers can measure these fully.
