Number of CSS Includes counts the externally linked stylesheets on a page — the <link rel="stylesheet"> references RankGear finds in the rendered HTML. It is a raw count, not a verdict: a single link can pull in an enormous stylesheet, so read it alongside actual performance rather than as a target to minimize.
| Factor ID | RG-TEC-032 |
|---|---|
| Family | Tech & platform |
| Measurement | Count |
| Measured zone | Rendered HTML without scripts |
What it measures
This factor counts recognized link elements whose rel value is exactly stylesheet. It reflects how many externally linked stylesheet references the page declares — a proxy for how the page assembles its styling from separate files.
How RankGear measures it
RankGear parses link tags from the script-free rendered HTML and counts those with a trimmed, case-insensitive rel="stylesheet" value. Inline <style> blocks and style attributes do not count. Repeated stylesheet references are counted separately, so the same file linked twice adds two to the total.
What RankGear looks for
<link rel="stylesheet" href="/assets/app.css">
<link rel="stylesheet" href="/assets/theme.css">
<!-- counts: 2 -->
<style> .btn { color: coral } </style> <!-- inline block: not counted -->
<div style="margin:0"> <!-- style attribute: not counted -->| If the page has… | Read it as |
|---|---|
| A high count | Many separate stylesheet requests — worth checking for unused or duplicate files, but not automatically a problem if performance is fine. |
| A low count | Few external stylesheets — but note a single link can still load a very large stylesheet, so confirm size and render behavior separately. |
How to optimize it
Treat the count as an observation, not a number to drive to zero. Remove unused or duplicate stylesheets, avoid loading framework components the page does not need, and deliver critical styling efficiently. After any consolidation, test visual behavior across breakpoints and states to confirm nothing broke.
Important considerations
- Count alone does not measure stylesheet size, render blocking, cache behavior, or unused CSS.
- A low count can still represent a very large stylesheet.
- Bundling can help or hurt depending on caching and page architecture.
- Optimize measured performance rather than chasing the smallest count.
- This is a prioritization signal that relates to position within a measured result set — it is correlation, not a guarantee that fewer includes will move a page up.
Related factors
Part of the Factors reference · how RankGear measures · glossary.