Skip to main content

Why Use DebugBear?

Wondering what makes DebugBear a great tool to speed up your website, and how it's different from other tools?

This article explains what makes DebugBear different.

Built for Core Web Vitals

Google's Core Web Vitals measure how fast your website is and whether it provides a good experience to visitors. Having good Web Vitals means you'll rank higher in Google and have happier users.

DebugBear is a modern tool that's built with the Core Web Vitals in mind. We track three types of Core Web Vitals data:

We consider the needs of everyone involved in Core Web Vitals optimization: from clients to Technical SEOs and developers.

Core Web Vitals in DebugBear

Page speed data you can trust

Collecting accurate page speed data isn't easy. Many tools use shortcuts to avoid the cost of setting up a high-quality test environment.

DebugBear runs tests in a controlled lab environment that reflects the experience of real users.

Compare that with this test result from PageSpeed Insights (actual measured data surfaced by our Site Speed Chrome extension). The Largest and First Contentful Paint events happen at the same time, but PSI says the LCP happens much later.

Sometimes PageSpeed Insights even reports that the website would load faster on a slower connection!

PageSpeed Insights observed data

Even other paid site speed tools often only report low quality data. This also applies to SEO tools like Moz.

Detailed test reports

A lot of stuff happens when loading a website, and it's often hard to find out what's really slowing it down.

DebugBear provides a tailored report for every performance metric that surfaces only the relevant data. That includes a detailed request waterfall that shows more than just a list of requests:

  • See how the priority of each request and bandwidth is used to download the response
  • Quickly identify render-blocking requests or preloaded resources or the LCP image

Finally, all this data is put into context by showing the rendering progress at each point in time as well as CPU activity for each resource.

Largest Contentful Paint metric data

Easily compare test results

Tracking down the cause of a site speed regression can be hard. DebugBear lets you see test results side by side and highlights differences.

This also works for optimizations.

Analysis of a site speed optimization

In the example above two changes were made to load the LCP element more quickly. Accordingly, the Largest Contentful Paint chart shows a large reduction in page load time.

LCP chart

You can also show off optimizations to clients or team members by viewing a before and after video recording.

Site speed video recording

Configurability and advanced settings

While being easy to set up, DebugBear also supports many advanced features:

Can we build this in-house?

Building a Lighthouse monitoring system in-house generally isn't a good idea:

  1. You'll get unreliable simulated metrics from Lighthouse
  2. Custom systems are difficult to maintain over time and you'll need to divert engineering time away from other projects

How is DebugBear different from Lighthouse?

In addition to providing higher-quality data than Lighthouse, DebugBear data is also more detailed and provides custom insights and recommendations.

And of course DebugBear monitors your website continuously, keeps a history of the results, and alerts you to changes.

In addition to the lab-based Lighthouse tests, DebugBear also keeps track of Google Core Web Vitals data and provides a custom real user monitoring solution.

Real-user monitoring

In addition to running high-quality lab tests, DebugBear also lets you collect in-depth real-user Core Web Vitals data.

RUM Core Web Vitals dashboard

You can track how many page views meet the Core Web Vitals, and use annotations to mark deployments or other changes on your website.

DebugBear Core Web Vitals trend

Get page speed data for all pages on your website, and see what page elements are responsible for the Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint.

Real user LCP elements data

Google's new Interaction to Next Paint metric is often hard to debug. DebugBear shows what scripts are responsible for processing delays, and what events or other triggers cause code to run.

INP script breakdown

What our customers say

We have hundreds of happy customers. Here's what some of them have said about us:

DebugBear has been a game changer in how we monitor and improve page speed for our clients. It's the perfect workflow to monitor and fix page speed issues before they start impacting Google rankings.

Steve Walker, Technology Director at Journey Further

We've updated around 15,000 pages and saw some nice gains from it. "Good URLs" and their impressions have increased 3x since implementation.

Rafayel Begoyan, Senior SEO Specialist at CoinStats

We love DebugBear. It has proven useful time and time again. I evaluated the different competitors and DebugBear was the best overall product.

Rafael Corral, Senior Software Engineer at Medium

The reporting data is very helpful in pinpointing what causes site speed issues – immediately actionable. It's well above and beyond the info you get from Lighthouse and the performance tests through Chrome.

Loren McDonald, IT Director at Manncorp

DebugBear's dashboard lets us see Core Web Vitals at a glance. At the same time, we're able to examine each result in a developer-friendly way.

John Bacon, Product Manager at GigSalad

Try DebugBear for free

Start monitoring your website with a free 14-day trial, or run a free site speed test here.

Monitor Page Speed & Core Web Vitals

DebugBear monitoring includes:

  • In-depth Page Speed Reports
  • Automated Recommendations
  • Real User Analytics Data