Automated Bundle Size Control in CI/CD: Setup and Optimization

The bundle grows unnoticed — we help you control it

You added one dependency, a colleague imported an entire utility — and a month later the JS bundle bloated by 200 KB. LCP dropped by 30%, and the culprit is nowhere to be found. In 80% of projects, developers notice the problem only after deploying to production. Automated bundle size checks in CI/CD stop degradation before it reaches release. Our engineers, with 5+ years of experience, set up such control for your stack. Initial consultation is free. Contact us for a bundle audit.

What problems we solve

• Invisible bundle growth — every new dependency increases size, but it's invisible in a PR until LCP jumps by 30%. For example, importing lodash entirely instead of lodash.get adds 20 KB in gzip.
• Code duplication — the same library in different chunks after code splitting, increasing total size by 10-15%.
• Bloated initial bundle — lazy loading not configured; the user downloads everything at once, increasing TTI by 2 seconds.
• Missing baseline — without a size history, it's hard to track which version caused a regression.

How it works

On each PR or deployment, we build the bundle, compare its size and individual chunk sizes against a baseline — values from the previous deployment or fixed limits. If the threshold is exceeded, CI fails or leaves a warning in PR. This can save up to $500 per month on performance maintenance.

Tools fall into two categories:

How bundlewatch helps control bundle size

Install it:

npm install --save-dev bundlewatch

Configure in package.json:

{
  "bundlewatch": {
    "files": [
      { "path": "dist/assets/index-*.js", "maxSize": "150kB" },
      { "path": "dist/assets/vendor-*.js", "maxSize": "400kB" },
      { "path": "dist/assets/*.css", "maxSize": "50kB" }
    ],
    "ci": {
      "trackBranches": ["main", "master"],
      "repoBranchBase": "main"
    }
  }
}

In GitHub Actions:

name: Bundle Size Check
on: [pull_request]
jobs:
  bundlewatch:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - run: npm ci
      - run: npm run build
      - run: npx bundlewatch
        env:
          BUNDLEWATCH_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          CI_REPO_OWNER: ${{ github.repository_owner }}
          CI_REPO_NAME: ${{ github.event.repository.name }}
          CI_COMMIT_SHA: ${{ github.event.pull_request.head.sha }}
          CI_BRANCH: ${{ github.head_ref }}
          CI_BRANCH_BASE: ${{ github.base_ref }}

bundlewatch leaves a comment in the PR with a table: current size, delta, status. More details at bundlewatch.

Setting up size-limit: deeper than just limits

size-limit analyzes the import tree: shows module weight considering tree-shaking and gzip.

npm install --save-dev size-limit @size-limit/preset-app

.size-limit.json:

[
  {
    "path": "dist/assets/index-*.js",
    "limit": "150 kB",
    "gzip": true
  },
  {
    "name": "Vendor chunk",
    "path": "dist/assets/vendor-*.js",
    "limit": "380 kB",
    "gzip": true
  }
]

In package.json:

{
  "scripts": {
    "size": "size-limit",
    "analyze": "size-limit --why"
  }
}

--why runs webpack-bundle-analyzer and shows exactly what is pulling the size.

Why relative limits are more convenient than absolute?

Absolute limits become outdated as the project grows, and constantly raising numbers is tedious. An alternative: check delta against the base branch. We use a script that compares the current branch size with the base. The script builds, saves the current size, fetches the base branch size from CI artifacts, and calculates the delta. If the delta exceeds 10%, CI fails. This approach saves setup time and doesn't require manual limit updates.

What to check besides total size

• Number of chunks — growth in chunk count from code splitting can increase HTTP requests.
• Initial bundle size separately from lazy-loaded chunks — this impacts LCP and TTI.
• Dependency duplicates — when one library is pulled into multiple chunks in different versions. Analyze with npm ls <package> or npx duplicate-package-checker-webpack-plugin.

Comparison of approaches: bundlewatch vs size-limit

Typical mistakes and how to avoid them

Some teams forget to configure caching, making the check take 5+ minutes. We cache node_modules and .vite, reducing time to 40–60 seconds. Another mistake is setting limits “by eye”. The right way: measure current sizes and set a 10–15% buffer.

What's included in the work

• Audit of the current bundle and identification of problem areas.
• Setup of the chosen tool (bundlewatch or size-limit) with custom limits.
• Integration into CI/CD (GitHub Actions, GitLab CI, Bitbucket Pipelines).
• Documentation of the configuration and maintenance process.
• Team training on working with notifications and analysis.
• Post-release support for 1 month.

Estimated timeline

Basic bundlewatch setup in an existing CI pipeline takes 4 to 8 hours. Setting up size-limit with analysis and PR notifications takes 1 to 2 business days. The cost is calculated individually after evaluating your project. Get a consultation — we'll tell you which option is optimal. Order a bundle audit, and we'll propose concrete solutions.

Why are Core Web Vitals critical for technical SEO?

PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.

Core Web Vitals: what really affects rankings

Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.

LCP: why 8 seconds is not an image problem

LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.

Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.

Solution:

1. Move to <img> with fetchpriority="high" and loading="eager"
2. Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
3. <link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
4. Remove render-blocking scripts above hero with defer

Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.

If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.

CLS: what causes layout shifts and how to stop them

CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.

Sources:

• Images without dimensions. <img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
• Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via min-height or load before main content.
• Web fonts. font-display: swap with size-adjust minimizes CLS.
• Dynamic content — add skeleton placeholder with dimensions.

INP: why interface freezes for 500ms

INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.

Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.

Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:

• Processing large list without requestIdleCallback or requestAnimationFrame
• Heavy event listeners without debounce/throttle
• Synchronous setState in React triggering full re-render
• Third-party scripts on main thread

Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.

How do structured data and Schema.org improve search visibility?

Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.

Markup types by scenario:

• E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
• Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
• Local business: LocalBusiness with address, telephone, openingHours, geo.
• FAQ: FAQPage with mainEntity — questions appear as expandable block.

Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.

How to conduct a technical SEO audit

Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.

Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.

JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.

Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.

Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.

What does the optimization process look like?

What deliverables do you receive?

• Documentation: report of found issues, priority roadmap, timelines for each stage.
• Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
• Training: one or two calls reviewing typical mistakes for your team.
• Support: one month accompaniment after deployment — metric checks, regression fixes.

How many positions can you regain through technical SEO?

We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.

Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.