Website technology stack

The rest of what the pages carry, grouped by what it does: the runtime, the framework, the CDN in front and the third-party scripts the site loads.

• Help center

Beyond the web server and the CMS, a page carries a whole stack of components. SiteScan lists them one row per category, ordered from what serves the page to what the page loads: runtime (PHP, Node.js, ASP.NET), framework (Next.js, Nuxt, Laravel), JS libraries, CSS and UI kits, bundler, e-commerce, CDN, hosting, cache, analytics, marketing tags, payments, captcha, chat, maps, fonts, PWA features and the site generator.

How it is detected

Signatures are matched in the headers and HTML of the entry page the crawler already fetched — script paths, global variables, cookies and response headers such as X-Powered-By or x-vercel-id. A version is shown only when the site publishes one. The analytics row also includes the trackers the privacy check found on any crawled page.

These rows are inventory, not verdicts: everything here is shown in green.

How to use the list

• Check the versions against current releases — an outdated jQuery or framework is an easy target.
• Count the third parties. Every chat widget, map, font host and marketing tag costs loading time and may need consent; see third-party scripts.
• Look for leftovers: two analytics tools doing the same job, or a library nothing uses any more.
• If you would rather not advertise the stack, remove X-Powered-By and similar headers; it does not change what the markup reveals.