Technology in use
Which technology does the website use, from the CMS and hosting to analytics tools, and are parts of it old?
What we check
From typical traces in the code, in the responses of the server and in the DNS records we recognise which technology the website uses:
| Category | Examples |
|---|---|
| CMS or builder | WordPress, TYPO3, Joomla, Wix, Jimdo, Squarespace, Webflow |
| Page builder | Elementor, Divi, WPBakery |
| Shop system | WooCommerce, Shopify, Shopware |
| Hosting and CDN | Hostpoint, Infomaniak, Cloudflare |
| Microsoft 365, Google Workspace | |
| Analytics and tag manager | Google Analytics, Matomo, Google Tag Manager |
| Consent tool | Cookiebot, Usercentrics, Borlabs |
In the footer area we also look for a note on who built the website.
Hints on age are components that appeared several years ago, such as an old jQuery or Bootstrap version, a doctype from the time before HTML5 or a copyright notice that has not been updated for years. If we find such things, we give a note.
The detection relies on the open detection rules of the webappanalyzer project. This check does not feed into the score.
Why it matters
The technology determines how the other points in the report can be fixed. A meta description is set differently in WordPress than in Wix, a redirect differently at Hostpoint than at Cloudflare. With this overview the matching instructions in the articles are quicker to find.
It also helps with putting things in context:
- Who looks after what? Hosting, email, website and analytics are often with different providers. The list shows who is responsible for which topic.
- How old is the website? Many old components suggest that the technical basis has not been renewed for some time. Outdated components often no longer receive security updates.
- What else is running along? Sometimes analytics tools or services turn up that nobody knew about any more, for example from an earlier campaign.
How to fix it
There is nothing to fix. Use the list like this:
- As an overview for conversations with the agency or hosting provider, for example when a modernisation is planned.
- For tidying up: remove services that are no longer needed. This makes the page faster and simplifies the privacy policy.
- For hints on age: have the components named updated. With very many old parts a relaunch is often more economical than many individual repairs.
- On the copyright notice: a "© 2017" in the footer looks as if the website has been abandoned. Many CMS can insert the current year automatically.
How to check it yourself
The browser extension "Wappalyzer" shows the technology detected for every website you visit. It is based on similar detection rules.
Frequently asked questions
Why is the CMS missing from the list?
Well-maintained websites often reveal little about their technology, for example because version details are hidden. From a security point of view this is even desirable. The detection is therefore never complete.
Does this check count in the score?
No. It is an overview that helps to put the other results in context and to find the right instructions.
Check a website now
We check "Technology in use" and all other points in a few minutes, free and without sign-up.
Related topics
-
Outdated software
Does the website run software that no longer receives security updates?
-
JavaScript libraries with known vulnerabilities
Does the website load JavaScript libraries such as jQuery in versions with known security vulnerabilities?
-
WordPress plugins with known vulnerabilities
Does the WordPress website use plugins in versions with publicly known security vulnerabilities?
-
HTML5 doctype
Does the home page begin with the modern declaration "<!DOCTYPE html>"?