A Playground for test releases
Type in made-up numbers for a few releases and watch the verdict react, using the same rules as real releases. Nothing is saved.
What’s new
What we added to CodeGecko, newest first. Every change ships to every project, no setup needed unless it says so.

Type in made-up numbers for a few releases and watch the verdict react, using the same rules as real releases. Nothing is saved.
A short walkthrough the first time you open Releases, a release report and a metric page. Replay it any time from the account menu.
See the bytes and main-thread blocking that came from other domains, with new domains flagged. It explains a slowdown; it never decides the verdict on its own.
What’s measuredPage weight · /products/:slug
v1.0.7 vs v1.0.6Each release lists the commits that shipped in it, so a regression points straight at the change that caused it.
Every release report now shows what each page shipped and whether it broke. When a page gets slower, you see whether the bytes grew or errors went up.
See how long the page froze and which script was behind most of it. Measured in Chrome and Edge, and counted toward the verdict once there’s enough data.
MethodologyLong animation frames · one visit
Most blocking from reviews-widget.js
When a page gets slower, the report splits the load into DNS, connect, server, download and DOM ready, so you can see where the time went.
Load steps · LCP regressed
Open any metric from a release report to see how it moved release by release, with each deploy marked by its verdict.
Good, Needs improvement and Poor, from Google’s Core Web Vitals ranges, now sit next to every metric. They show where a metric stands; the verdict still shows how it moved.
Pages are grouped automatically. Set your own groups with data-routes, or merge pages in the dashboard so quiet pages count together and reach a verdict sooner.
<script async src="…/collector.js" data-routes="/blog/:post, /docs/:page"></script>
Real-user Core Web Vitals, compared release by release. A script tag collects visits, one CI step registers each deploy by its commit, and your second release gets the first verdict.
How it works