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

🧵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 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

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

🔵 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

thanks!

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