Gravity @gravityci

We collected some general best practices on artifact sizes for you. Easy to remember—but unfortunately, not always easy to follow. We’ve made these mistakes too. It's surprisingly easy to miss when things grow. That’s why we built Gravity. Try it ➡️ gravity.ci

Also, read the full Web Almanac chapter here ➡️ almanac.httparchive.org/en/2024/page-w… 🧵6/6

You probably don’t mean to ship bloated bundles. But it happens quietly. A few KB here, a few KB there—it builds over weeks of PRs. You won’t catch it in code reviews. You might not even notice it post-deploy. ⚠️ That’s why we built gravity.ci Give it a try! 🧵5/6

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. 🧵1/6

We spotted a +12KB increase in a sitemap file. That led to catching a subtle bug: a bunch of additional, yet broken entries. Gravity flagged the change. We fixed it before merge 👉 That’s the power of making size changes visible. Give it a try ➡️ gravity.ci

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/mai…

Considering Gravity for your team? Here’s a quick demo showing how it fits into your CI workflow, tracks artifact sizes, and prevents bloat before it reaches production ➡️ youtube.com/watch?v=2vD_ge… 🪐 Built for developers who care about performance – by @mainmatter

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

Gravity is live on #producthunt: producthunt.com/posts/gravity-… 🚀

Nobody wants to ship slow, bloated software. But without visibility, it’s hard to know when things are growing out of control. Gravity makes sure you aware before it’s too late. Try it now ➡️ gravity.ci Let us know what you think! 🧵4/4

Gravity integrates into your CI pipeline and tracks build artifact sizes in every PR. 🔷 Analyses your production build artifacts 🔷 Compares them to the target branch 🔷 Flags new or growing files before they get merged 🔷 Adds a check to GitHub to make you aware 🧵3/4

Gravity is live 🪐 and we think you’re gonna love it. It’s a CI tool that keeps your build artifacts in check—so you don’t accidentally ship bloated JS bundles, oversized images, huge CSS files, or other assets. Built by @mainmatter Learn more ➡️ mainmatter.com/blog/2025/03/1… 🧵1/4