0Pricing
Web Performance Optimization & Lighthouse · Lesson

Analyzing Performance Data

Interpret RUM and synthetic monitoring data to identify trends, regressions, and areas for improvement in user experience.

Analyzing Performance Data is a free Web Performance Optimization & Lighthouse lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Web Performance Optimization & Lighthouse learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Decoding Performance Data

Welcome! In this lesson, we'll dive into the art of analyzing the performance data collected by Real User Monitoring (RUM) and Synthetic Monitoring tools.

Understanding this data is crucial for identifying trends, pinpointing issues, and ultimately making your website faster for everyone.

Unpacking RUM Metrics

RUM tools gather data directly from your users' browsers. This includes a wealth of metrics like:

  • Page Load Time: Total time for a page to fully load.
  • Core Web Vitals: LCP, FID, CLS – key user experience metrics.
  • Resource Timings: How long specific images, scripts, or stylesheets take to load.
  • JavaScript Errors: Client-side errors impacting user experience.

RUM shows you what users actually experience.

Understanding Data Distributions

When looking at RUM data, simple averages can be misleading. Instead, focus on percentiles.

  • Median (50th percentile): Half of your users experience this or better.
  • 90th Percentile: 90% of users experience this or better. This is often a good target for optimization.
  • 99th Percentile: The experience of your slowest users. Addressing this can uncover critical issues.

A high 90th percentile LCP means many users are waiting too long.

Tracking Performance Over Time

Analyzing data over time helps identify trends and regressions. A trend might be a gradual improvement from optimizations, or a slow degradation due to new features.

Regressions are sudden drops in performance, often after a new deployment. Dashboards typically show graphs of metrics over days or weeks, making these changes visible.

  • Upward spike: Performance got worse.
  • Downward dip: Performance improved.

Synthetic Metrics & Stability

Synthetic monitoring runs automated tests from controlled environments. This means consistent network speeds, device types, and locations.

Key synthetic metrics include:

  • Speed Index: How quickly content visually populates.
  • Time to First Byte (TTFB): Time until the server responds.
  • Lighthouse Scores: A comprehensive audit score for performance, accessibility, etc.

Synthetic data is excellent for catching regressions in a controlled, repeatable way.

Complementary Perspectives

RUM and Synthetic data offer different, yet complementary, views.

  • RUM: Shows the messy, real-world experience (varied networks, devices, locations). Great for understanding user impact.
  • Synthetic: Provides a baseline, repeatable performance measurement. Ideal for CI/CD and catching regressions early.

Using both gives you a holistic understanding of your site's performance.

The Business Impact of Speed

Performance isn't just a technical metric; it directly impacts your business. Analyzing data helps you connect the dots:

  • Conversion Rates: Faster sites often lead to higher sales or sign-ups.
  • Bounce Rate: Slow pages make users leave quickly.
  • User Engagement: Responsive sites keep users interacting longer.

Quantify the impact of performance improvements to justify further investment.

Pinpointing Performance Bottlenecks

Once you spot an issue, you need to drill down. Most monitoring tools allow you to filter data by:

  • Page URL: Is the issue specific to one page?
  • Browser/Device: Does it affect only mobile users or a specific browser?
  • Geographic Location: Are users in certain regions experiencing slowness?
  • Resource Type: Is it a large image, a slow API call, or a blocking script?

This helps narrow down the problem area for your team.

Be Notified, Not Surprised

Don't wait for users to report issues. Set up alerts to be notified automatically when performance metrics cross critical thresholds.

Common alert conditions include:

  • 90th percentile LCP exceeds X seconds.
  • Cumulative Layout Shift (CLS) score is above Y.
  • Error rate on a critical page increases by Z%.

This allows for quick response and minimizes user impact.

{
  "alertName": "High LCP on Homepage",
  "metric": "LCP_90th_percentile",
  "threshold": 4000,
  "operator": "greaterThan",
  "period": "5_minutes",
  "page": "/homepage"
}

Translating Data into Action

The goal of data analysis isn't just to find problems, but to fix them. Prioritize optimizations based on:

  • Impact: How many users are affected? How critical is the page/feature?
  • Effort: How difficult is the fix?
  • Business Value: What's the potential ROI?

Start with high-impact, low-effort changes for quick wins, then tackle bigger projects.

Performance Data Scenario

Your team just deployed a new feature. Looking at your RUM dashboard, you notice the 90th percentile LCP for mobile users on the homepage jumped from 2.5 seconds to 5 seconds. The median LCP for desktop users remained stable at 1.8 seconds.

What are the most likely immediate conclusions you can draw from this data?

Recap: Mastering Performance Data

Great job! You've learned how to effectively analyze RUM and Synthetic monitoring data.

Remember to look beyond averages, track trends, correlate performance with business outcomes, and drill down to find root causes. Proactive alerting and turning data into actionable insights are key to continuous optimization.

Keep monitoring, keep optimizing!

Frequently asked questions

Is the “Analyzing Performance Data” lesson free?

Yes — the full text of “Analyzing Performance Data” is free to read here on the web, and the Web Performance Optimization & Lighthouse course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Web Performance Optimization & Lighthouse course, upgrade to CoddyKit PRO.

What will I learn in “Analyzing Performance Data”?

Interpret RUM and synthetic monitoring data to identify trends, regressions, and areas for improvement in user experience. You practise Web Performance Optimization & Lighthouse with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Web Performance Optimization & Lighthouse?

No prior experience is required. Web Performance Optimization & Lighthouse on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Analyzing Performance Data” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Web Performance Optimization & Lighthouse lesson?

Yes. Every Web Performance Optimization & Lighthouse lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. RUM vs. Synthetic Monitoring
  2. Implementing RUM Solutions
  3. Analyzing Performance Data
  4. Setting Up Performance Alerting
← Back to Web Performance Optimization & Lighthouse