English
14 KB page size
The full styled HTML of a trip2g page gzips to ~11.7 KB — inside the TCP initial congestion window of ~14 KB. The browser receives the complete, styled page in a single round-trip.
Why 14 KB matters
TCP begins every connection with an initial congestion window of 10 segments (~14 KB, per RFC 6928). Any data beyond that limit requires an additional round-trip before the server can continue sending. For a web page, that delay shows up directly as a slower first paint.
A page under 14 KB arrives in one window. A page at 20 KB needs two round-trips to deliver everything — and the browser cannot render the styled page until it has the stylesheet.
How trip2g stays under the limit
The default template embeds the stylesheet as a <style> tag directly in the HTML instead of a separate <link> request. No extra HTTP connection, no render-blocking resource, no flash of unstyled content.
The stylesheet is compiled and minified from SCSS. Gzipped inline with the HTML, it adds ~11 KB. The rest — page structure, metadata, and content — fits in the remaining ~0.7 KB.
Result
- No separate CSS request
- Full styled page in the first TCP window
- Consistent behavior on high-latency and mobile connections where round-trip time dominates
- Solid baseline for Core Web Vitals (LCP, CLS)
2026-05-10
Pages on trip2g.com often exceed the 14 KB budget when a right sidebar is present. The sidebar adds widget HTML that pushes the page past the limit. The landing page stays within budget; note pages with both sidebars do not.
2026-05-06
The trip2g.com landing page was tuned to fit the budget today: inline SVG diagrams were extracted into separate files, served with cache-friendly URLs, so the HTML stays inside the 14 KB window.
Admin now ships a homepage size health check that fetches the gzipped homepage and warns when it exceeds the limit. Goal: keep the landing page ultra-fast — the first paint never costs more than one round-trip.