Inline CSS Kilobytes

Abstract illustration of inline CSS inside a style element being weighed in kilobytes, in RankGear indigo and coral.

Inline CSS Kilobytes reports how much CSS lives directly inside a page’s <style> elements, measured in kilobytes. It counts the contents of style elements only — not style attributes, linked stylesheets, or the compressed size sent over the wire — so read it as a description of the page, not a target to minimize.

Factor IDRG-SIZ-011
FamilyPage Size
MeasurementKilobytes
Measured zoneContents of inline style elements

What it measures

This factor reports the measured size of the contents of inline style elements, in kilobytes. It isolates the CSS that is embedded directly in the page markup — the rules written between opening and closing <style> tags — and expresses their combined weight as a single number.

Back to Top

How RankGear measures it

RankGear extracts the contents of every parsed <style> element from the rendered HTML, sums their UTF-16 lengths, and divides by 1,024. This measures style-element contents — it does not include style attributes, linked stylesheets, the compressed transfer size, or CSS generated at runtime.

Back to Top

What RankGear looks for

<style>
  .hero { color: #5457D6; padding: 2rem; }
  .cta  { background: #FF6F61; }
</style>

<!-- counted: the rule text between every <style> and </style> -->
<!-- not counted: <div style="...">, <link rel="stylesheet">, gzip size -->
inline_css_kb = utf16_length(all <style> contents) / 1024
Back to Top

How to optimize it

Keep critical inline CSS deliberate and compact: consolidate repeated rules, and move noncritical reusable styles into cacheable stylesheets when doing so genuinely improves delivery. Treat this factor as an observation about how a page is built rather than a number to drive toward — a small figure earned by stripping useful styles is not an improvement.

Back to Top

Important considerations

  • RankGear divides the UTF-16 length by 1,024; this is a character-length estimate, not a network-transfer byte measurement.
  • Compare the factor against ranking and real user-performance evidence rather than assuming that larger or smaller is always better.
  • Minification, compression, external resources, and runtime CSS behavior may not be reflected in this value.
  • Preserve useful content and functionality while improving efficiency.
  • This is a prioritization signal that relates to position within a measured result set; it does not by itself cause or guarantee a ranking.
Back to Top

Related factors

Part of the Factors reference · how RankGear measures · glossary.

Back to Top