Gravity

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 | 2024 | The Web Almanac by HTTP Archive Page Weight chapter of the 2024 Web Almanac covering why page weight matters, bandwidth, complex pages, page weight over time, page requests, and file formats.

Also, read the full Web Almanac chapter here ➡️ almanac.httparchive.org/en/2024/page...

🧵6/6

Gravity Gravity monitors build artifact sizes to prevent accidental increases – right in your CI pipeline.

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 grows gradually. One dependency. One large image. One embed. And suddenly, your page takes 5s to load and burns through a user’s data cap. Devs often don’t realize it’s happening until it’s too late.

🧵4/6

The LCP (Largest Contentful Paint) metric tracks how fast a page’s content becomes visible to users.

A “good” page needs to score less than 2.5s, and anything above 4s is poor. In 2024, the average mobile page LCP is 18s and desktop 6.4s. Thats… not good. 😬

🧵3/6

Heavy pages hit users on slow networks, older phones, and limited data plants. They widen the performance inequality gap, making the web less usable for millions. Page weight is an accessibility issue as much as a performance one.

🧵2/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. And it's hurting users.

🧵1/6

Gravity Gravity monitors build artifact sizes to prevent accidental increases – right in your CI pipeline.

We spotted a +12KB increase in a sitemap file. That led to catching a subtle bug: a bunch of additional, yet broken entries.

Hard to see in code review. Gravity flagged the change. We fixed the bug 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/m...

Gravity helps developers track and control artifact sizes in CI/CD workflows. Whether it's JavaScript bundles, images, binaries, or Docker images, Gravity pr... Gravity Demo | Keep Your Build Artifact Sizes in Check

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 ➡️ www.youtube.com/watch?v=2vD_...

🪐 Built for developers who care about performance – by @mainmatter.com

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

thanks!

Gravity CI - Gravity tracks artifact sizes to prevent accidental increase | Product Hunt Gravity monitors build artifact sizes to prevent accidental increases – right in your CI pipeline. Don't miss a new dependency growing your JS bundle disproportionately or an oversized, uncompressed i...

Gravity is live on #producthunt: www.producthunt.com/posts/gravit... 🚀

Gravity Gravity monitors build artifact sizes to prevent accidental increases – right in your CI pipeline.

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

You know how easy it is to accidentally bloat production assets?

You add a simple date formatter… and suddenly moment.js (+300KB) sneaks in. 😬

Or you push a 16MB JPEG instead of a thumbnail.

These small mistakes add up—slowing down your app, frustrating users, and wasting resources.

🧵2/4

Keeping Artifact Sizes Under Control - Mainmatter Staying on top of asset sizes can be challenging. Gravity is a developer tool that helps teams catch regressions early.

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.com

Learn more ➡️ mainmatter.com/blog/2025/03...

🧵1/4