Stack Health Score
Methodology
Every scan on TrueTechFinder produces a Stack Health Score between 0 and 100. This page explains exactly how that score is calculated — transparently, with no black boxes.
A single number that summarises six measurable signals
The Stack Health Score is a weighted composite of six pillars, each measuring a distinct quality dimension of the detected technology stack. The maximum score is 100. The minimum is 0.
Scores above 80 represent modern, secure, well-observed stacks. Scores between 50–80 indicate a functional but improvable stack. Scores below 50 signal meaningful technical debt or risk areas.
What we measure and why it matters
Evaluates the presence and quality of a CDN, edge delivery network, and hosting architecture. Sites running a reputable CDN (Cloudflare, Fastly, Akamai, Vercel Edge) with global PoPs score highest. Sites serving directly from an origin with no CDN lose significant points.
Checks for HTTPS, HSTS enforcement, modern TLS version, and the presence of key HTTP security headers (Content-Security-Policy, X-Frame-Options, Referrer-Policy). Security posture is one of the most actionable signals a stack scan can surface.
Assesses how current the detected frameworks, CMS, and build tools are. Sites built on actively maintained, modern technology (Next.js, Nuxt, SvelteKit, Astro) score well. Sites on end-of-life platforms, legacy PHP frameworks, or outdated CMS versions score lower.
Looks for signals of performance-conscious choices: lightweight analytics (Plausible, Fathom), deferred/async loading patterns, image optimisation services, and the absence of known performance-heavy tag managers firing synchronously.
Rewards sites that demonstrate production-grade monitoring: error tracking (Sentry, Bugsnag), APM (Datadog, New Relic), uptime monitoring, and real-user monitoring (RUM). These signals indicate a team that actively manages reliability.
Flags signs of duplication or internal contradictions: multiple competing analytics tools, two CMS platforms running simultaneously, conflicting A/B testing services, or signs of a migration in progress. A coherent stack scores higher than a fragmented one.
Limitations & transparency
Scores are based on technologies we can detect from a public scan. Technologies behind authenticated sessions, internal tools, or obfuscated code may not be captured.
Every scan reflects the state of a site at that moment. A site's score can change significantly after a platform migration, security hardening, or CDN change.
A high score does not mean a site is fully secure. It reflects detected signals only. A proper security audit requires deeper access than a passive technology scan.
See your site's score now
Enter any URL and get a Stack Health Score plus the full breakdown across all six pillars — free, no account required.
Scan Any Website Free →