design.com
AI signal score
2/ 100
Insufficient evidence
This is an experimental heuristic score, not proof of how a site was made.
- Last checked
- (1 hour ago)
AI-related evidence
1Design, copy and structure patterns. These are weak, capped signals — plenty of hand-made sites share them.
-
Uniform section rhythm weak +2 ptsUI_SAME_SECTION_RHYTHM · design
Many page sections repeat nearly identical markup. Generated landing pages often do this, but so does any consistent component-based design, so this is only a weak hint.
- sections:
- 57
- largest_repeated_group:
- 54
Technology context
3Frameworks, libraries and hosting we noticed. Context only — popular tools are not evidence of AI generation and add 0 points.
-
Hosting / CDN hint context 0 ptsTECH_HOSTING_HINT · technology
The static HTML suggests a known hosting / CDN provider. This is technology context only and adds no points: it is common in both hand-written and generated sites.
- signals:
- ["Amazon CloudFront response header"]
-
Uses Tailwind CSS context 0 ptsTECH_TAILWIND · technology
The static HTML suggests Tailwind CSS. This is technology context only and adds no points: it is common in both hand-written and generated sites.
- signals:
- ["--tw-* custom properties in CSS"]
-
Uses Vue / Nuxt context 0 ptsTECH_VUE · technology
The static HTML suggests Vue / Nuxt. This is technology context only and adds no points: it is common in both hand-written and generated sites.
- signals:
- ["scoped-style data-v-* attributes","Nuxt asset path: /_nuxt/entry.JZ-jEKRR.js","Nuxt state script"]
Limitations of this scan
1-
Only a common tech stack context 0 ptsLIMIT_GENERIC_TECH · constraint
Only common technologies were detected, with no builder-specific marker. Frameworks such as React, Tailwind or shadcn/ui are used by countless hand-written sites and are not evidence of AI generation.
- technologies:
- ["TECH_TAILWIND","TECH_VUE"]