c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Server stats:

2.9K
active users

#webperf

15 posts13 participants3 posts today

New blog post! blogs.igalia.com/dape/2025/03/

In performance research, a principle is reducing the overhead of the analysis tools, to improve the accuracy. Tracing remotely helps: no need for the tracing UI, and no overhead of running it. Specially useful when Chromium runs in an embedded device.

trace-chrome is the tool I wrote to capture and store the traces from a different computer, with a simple command line interface. Check it at github.com/jdapena/trace-chrome

cc @igalia @developers #webperf

blogs.igalia.comtrace-chrome: easy remote tracing of ChromiumJosé Dapena blog.

One of the most common questions we hear is "Why do my numbers for the SAME metrics vary in DIFFERENT tools?"

Here are some of the most common reasons.

Takeaway: The most important thing to track is consistency and changes within a single monitoring tool and settings.

speedcurve.com/web-performance

SpeedCurveHow to Trust Your Web Performance Metrics | SpeedCurveHave you ever wondered why you get different numbers for the same metrics using different tools? Here are some of the most common reasons.

Major site outages grab all the sexy headlines, but what if I told you that boring old page slowdowns actually may hurt your business more? This post includes suggested formulas for calculating the rough cost of downtime vs slowtime for your site.

speedcurve.com/blog/downtime-v

SpeedCurveSpeedCurve | Downtime vs slowtime: Which costs you more?Page slowdowns can cause as much damage as downtime, hurting revenue, brand health, and permanent abandonment rate.