Web Performance Optimization & Lighthouse · 강의

예산 모니터링 및 알림

정의한 성능 예산을 지키도록 자동 모니터링 및 알림 시스템을 구현합니다.

예산 모니터링 및 알림은(는) CoddyKit의 무료 Web Performance Optimization & Lighthouse 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Web Performance Optimization & Lighthouse 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Web Performance Optimization & Lighthouse 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Why Monitor Performance Budgets?

You've learned to set performance budgets. But how do you ensure your website stays within those limits as it evolves? That's where continuous monitoring and alerting come in!

Monitoring helps you:

Catch regressions early: Identify performance drops before they impact users.
Maintain quality: Ensure new features don't unintentionally slow things down.
Stay competitive: Keep your site fast and responsive, meeting user expectations.

What Can We Monitor?

Performance budgets aren't just about page load time. They can apply to various aspects of your website:

Resource Size: Total JavaScript, CSS, or image bundle size.
Performance Scores: Lighthouse scores for performance, accessibility, etc.
Metric Thresholds: Specific Core Web Vitals like Largest Contentful Paint (LCP) or Cumulative Layout Shift (CLS).
Request Count: The number of network requests your page makes.

Continuous monitoring helps track these against your predefined limits.

Build-Time Budget Checks

One of the earliest points to check performance budgets is during your project's build process. Tools like Webpack, a popular JavaScript module bundler, can be configured to warn or error if certain asset size budgets are exceeded.

This prevents large files from even making it to deployment, catching issues before they reach users.

Webpack Performance Hints

Webpack allows you to define performance hints in your configuration. These hints will issue warnings or throw errors if your bundles exceed specified sizes.

Here's a simple example in a webpack.config.js file:

module.exports = {
  // ... other webpack config
  performance: {
    hints: 'warning', // Can be 'error' or false
    maxAssetSize: 200 * 1024, // 200 KiB
    maxEntrypointSize: 250 * 1024, // 250 KiB
    assetFilter: function(assetFilename) {
      return !/(\.map$|^favicon\.ico$)/.test(assetFilename);
    }
  }
};

Continuous Integration (CI) for Budgets

For more comprehensive checks, especially against metrics like Lighthouse scores or Core Web Vitals, you can integrate performance budget monitoring into your Continuous Integration (CI) pipeline.

A CI pipeline automatically runs tests and builds your code whenever changes are pushed. By adding performance checks, you can:

Automate audits: Run Lighthouse or other tools on every code change.
Fail builds: Prevent deployments if performance budgets are violated.
Get instant feedback: Developers see performance issues directly in their pull requests.

Lighthouse CI Budget Assertions

Lighthouse CI is an excellent tool for integrating performance checks into your CI pipeline. It allows you to define specific assertions (rules) that your Lighthouse audit results must meet.

If any assertion fails, Lighthouse CI can mark your build as a failure. This ensures your performance never drops below a baseline.

Here's how you might define budgets in a .lighthouserc.json file:

{
  "ci": {
    "collect": {
      "url": "http://localhost:8080"
    },
    "assert": {
      "assertions": {
        "performance-score": ["error", {"minScore": 0.90}],
        "interactive": ["error", {"maxNumericValue": 3000}],
        "total-blocking-time": ["warn", {"maxNumericValue": 200}]
      },
      "budgets": [{
        "resourceSizes": [
          {"resourceType": "script", "budget": 170},
          {"resourceType": "image", "budget": 250}
        ],
        "resourceCounts": [
          {"resourceType": "script", "budget": 10}
        ]
      }]
    }
  }
}

Types of Alerts

When a performance budget is exceeded, you need to know about it! Alerts can take various forms:

Build Failure: The most direct alert, stopping deployment until fixed.
Notifications: Messages sent to team communication channels (Slack, Microsoft Teams).
Email Reports: Detailed summaries sent to specific individuals or mailing lists.
Dashboard Warnings: Visual indicators on monitoring dashboards.

The goal is to make performance issues visible and actionable for your team.

Setting Up Notification Channels

Many CI/CD platforms and monitoring tools offer integrations with popular communication services. For example, if your Lighthouse CI audit fails, you can configure your pipeline to:

Post a message to a Slack channel.
Send an email to the development team.
Create an issue in a project management tool like Jira.

These integrations ensure that the right people are informed immediately when budgets are breached.

Real User Monitoring (RUM) Alerts

While build-time and CI checks are proactive, Real User Monitoring (RUM) provides insights into actual user experiences. RUM tools collect performance data directly from your users' browsers.

You can set up RUM alerts for:

Core Web Vitals: Alert if a certain percentage of users experience LCP or CLS above your thresholds.
Error Rates: Notify if JavaScript errors spike, potentially impacting performance.
Geographic Performance: Get alerts if users in a specific region experience slow loading times.

RUM alerts help you react to real-world performance degradations.

Quick Check: Budget Monitoring

Which of the following are effective ways to monitor and receive alerts about performance budget violations?

Recap: Staying Within Budget

Great job! You've learned how critical continuous monitoring and alerting are for maintaining web performance.

We explored how build tools like Webpack can enforce size budgets.
We saw how CI/CD pipelines, especially with tools like Lighthouse CI, automate checks and fail builds on budget breaches.
We discussed various alerting mechanisms, from build failures to notifications.
And finally, we touched upon Real User Monitoring (RUM) for real-world performance alerts.

By implementing these strategies, you can ensure your website consistently meets its performance goals.

자주 묻는 질문

“예산 모니터링 및 알림” 강의는 무료인가요?

네 — “예산 모니터링 및 알림” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Web Performance Optimization & Lighthouse 강의 전체를 잠금 해제할 수 있습니다. Web Performance Optimization & Lighthouse 강의에는 총 4개의 강의가 포함되어 있습니다.

“예산 모니터링 및 알림”에서 뭘 배우나요?

정의한 성능 예산을 지키도록 자동 모니터링 및 알림 시스템을 구현합니다. 브라우저에서 직접 실행하는 실습 코드로 Web Performance Optimization & Lighthouse을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Web Performance Optimization & Lighthouse을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Web Performance Optimization & Lighthouse은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.

“예산 모니터링 및 알림” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Web Performance Optimization & Lighthouse 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Web Performance Optimization & Lighthouse 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Web Performance Optimization & Lighthouse(으)로 돌아가기