We collected some general best practices on artifact sizes for you. Hope this helps! 😊

This card is easy to remember—but unfortunately, not always easy to follow. It's surprisingly easy to miss when things grow. That’s why we built Gravity. It helps you keep artifacts lean.

Try it ➡️ gravity.ci

Page weight isn't just about load time—it’s about access, equity, and sustainability. Believe it or not, page weight is still climbing. In 2024, the median mobile page weighs in at 2.6MB on desktop and 2.3MB on mobile. Every new feature, image, or JS lib adds up. And it's hurting users.

🧵1/6

Visual regression tools help devs spot UI issues early.

Gravity brings that same workflow to artifact size.

A small size diff? Often just noise. But sometimes, it’s a sign of something broken. Like in this PR ➡️ github.com/mainmatter/m...

Everyone knows `node_modules` is among the heaviest object in the universe 🪐 Don’t accidentally ship parts of it to your users.

Let Gravity catch bloated artifacts in your PRs before they go live ➡️ gravity.ci

#frontend #javascript

🔵 Step 3: Merge with Confidence

Once the changes are approved, all checks pass, and your PR is **good to go**—with zero unexpected bloat. Keep your builds lean.

Try Gravity now ➡️ gravity.ci

🧵 3/3

🔵 Step 2: Review & Approve

Gravity gives you a clear diff of what changed—so you can review, approve, or fix size increases before merging. No more surprises post-deploy.

🧵 2/3

Shipping bloated artifacts by accident? 😬 Gravity flags new or growing artifacts in your PR *before* they hit production. Here’s how it work

🔵 Step 1: Detect

Gravity reports when a PR introduces new or growing artifacts, so you’re never caught off guard.

🧵 1/3