Tailwind CSS Detector
Paste any URL and instantly see whether the site is built with Tailwind CSS — with the matched evidence.
We do not store the URL you audit. Want the full audit (performance / images / SEO / accessibility + real-browser speed test)? → run the full audit
Why check this
Confirm the platform first: Framework decides what can be changed and whether it is worth it.
What this is
Tailwind CSS is a utility-first styling framework used heavily on marketing pages and SaaS front ends. Confirming utility class clusters, `--tw-` variables or toolchain traces shows whether a missing purge inflated CSS, or whether a runtime CDN script reached production.
How to tell from a public page
- [Tailwind] Class clusters show utility patterns (for example flex plus gap-/p-).
- [Tailwind] Styles include `--tw-` custom properties.
- [Tailwind] Source or comments leave toolchain strings.
- [Tailwind] Official CDN scripts sometimes appear (they should not in production).
How to read the result
Confirm when utility patterns or CSS variables reproduce; a design spec saying the stylesheet is similar does not qualify. Absence can mean utility classes were compiled into short hashes. Sites that hand-wrote a few similar class names create soft matches. After a hit, inspect CSS file weight and accidental CDN runtimes.
What to do next
Enable content-path purge, avoid production CDN runtimes, and inspect the front-end framework — often Next — via Next.js detector. Combined vitals return via run the full performance / images / SEO / accessibility audit on the home page. Attach utility-class samples when arguing about CSS weight.
Related detectors
FAQ
How is Tailwind CSS detected?
From structural signatures in the public HTML and response headers (domains, paths, attributes, scripts). Every verdict lists how many times each pattern matched — nothing is guessed.
Can the result be wrong?
If only a bare brand keyword matches without structural evidence, we label it \u201clikely\u201d instead of \u201cconfirmed\u201d — we would rather under-report than cry wolf.
Do you save the URLs I check?
No. The audit runs inside the request and the URL you paste is not written to storage. There are no third-party tracking scripts on the page either, so no log of who checked what exists. Copy the result yourself if you want a record.
Can a website hide what it is built with?
Partly, but rarely completely. The HTML sent to your browser, the response headers, script paths and asset structure have to be exposed to work, so there is always something readable. Server-side code, build config and private APIs stay invisible. That is why this tool reports the evidence it found rather than claiming a full picture. No match does not mean the technology is absent.
Optimization help is available
Tell me your URL and what you want fixed — you get a clear scope, price and timeline.
To：[email protected] | Cc：[email protected]
