Uncompressed Size is the total file size of web assets (HTML, CSS, JavaScript, images) before any compression algorithms like Gzip or Brotli are applied. In A/B testing, it helps teams protect page speed and user experience while variants, scripts, and tracking are running.
Uncompressed Size is the total file size of web assets (HTML, CSS, JavaScript, images) before any compression algorithms like Gzip or Brotli are applied.
This metric represents the raw size of resources that browsers must parse and process after decompression, even though they're transmitted in compressed form. While compressed size affects network transfer time, uncompressed size impacts parsing, compilation, and execution performance. The ratio between compressed and uncompressed size indicates compression efficiency, typically ranging from 3:1 to 10:1 for text-based assets.
In A/B testing, tracking uncompressed size helps identify variants that add significant JavaScript or CSS overhead, which can slow down page interactivity even with good network performance. Large uncompressed files require more CPU time to parse and execute, particularly impacting mobile devices with limited processing power. This metric is especially important when testing variants that include additional tracking scripts, personalization engines, or interactive features.
A test variant that adds a new recommendation widget appears to load quickly due to good compression, but analysis reveals 450KB of uncompressed JavaScript that causes a 2-second delay in Time to Interactive on mobile devices, leading to lower engagement despite successful initial loading.
Use Uncompressed Size as a guardrail when QAing experiments. Check it on mobile and desktop, monitor it after launch, and treat major slowdowns as a reason to simplify the variant or move heavier work out of the critical rendering path.
A common mistake is optimizing the variant message while ignoring whether Uncompressed Size made the experience slower. If a test harms page speed, the result may reflect performance friction rather than the quality of the idea.
Uncompressed Size is the total file size of web assets (HTML, CSS, JavaScript, images) before any compression algorithms like Gzip or Brotli are applied. In A/B testing, it helps teams protect page speed and user experience while variants, scripts, and tracking are running.
In A/B testing, tracking uncompressed size helps identify variants that add significant JavaScript or CSS overhead, which can slow down page interactivity even with good network performance. Large uncompressed files require more CPU time to parse and execute, particularly impacting mobile devices with limited processing power. This metric is especially important when testing variants that include additional tracking scripts, personalization engines, or interactive features.
Use Uncompressed Size as a guardrail when QAing experiments. Check it on mobile and desktop, monitor it after launch, and treat major slowdowns as a reason to simplify the variant or move heavier work out of the critical rendering path.
This comprehensive checklist covers all critical pages, from homepage to checkout, giving you actionable steps to boost sales and revenue.
Mida.so is a super lightweight A/B testing tool to help you experiment, analyze and implement conversion strategies in minutes.
