Site profile
materialize.com
Built with @finsweet/attributes 2.7.1, mealz-components 3.2.8, gtm, @wix/design-system 1.328.0, @blotoutio/providers-blotout-consent-sdk 1.73.0, @playpilot/tpi 8.40.0, @typebot.io/js 0.10.11, reveal.js 6.0.2, hubspot-forms, @desivocal/agents-cdn 1.0.21, @pairbo/ui-kit 0.4.23, @epigraph/configurator 2.7.0 and more. 5 pages and 57 stored files.
rank 392,495 14 libraries 1 identifier 0 third-party hosts 0 crawls open the site
Technologies and libraries
Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.
| Library | Version | Seen |
|---|---|---|
| @finsweet/attributes | 2.7.1 | 2026-09-24 |
| mealz-components | 3.2.8 | 2026-09-24 |
| gtm | 2026-09-24 | |
| @wix/design-system | 1.328.0 | 2026-09-24 |
| @blotoutio/providers-blotout-consent-sdk | 1.73.0 | 2026-09-24 |
| @playpilot/tpi | 8.40.0 | 2026-09-24 |
| @typebot.io/js | 0.10.11 | 2026-09-24 |
| reveal.js | 6.0.2 | 2026-09-24 |
| hubspot-forms | 2026-09-24 | |
| @desivocal/agents-cdn | 1.0.21 | 2026-09-24 |
| @pairbo/ui-kit | 0.4.23 | 2026-09-24 |
| @epigraph/configurator | 2.7.0 | 2026-09-24 |
| biel-search | 0.1.89 | 2026-09-24 |
| vditor | 4.0.0 | 2026-09-24 |
Tracking, tag and verification IDs
Public identifiers read out of the source. Each links to every other site in the index that carries the same one.
| What | Value | Found in |
|---|---|---|
| Google Tag Manager container (Google) | GTM-5VDFPSJ | view source |
Third-party hosts
The stored pages and scripts reference no host outside materialize.com.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about materialize.com
- How does PageSourceSearch know what materialize.com is built with?
- From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
- How far back does the history of materialize.com go?
- To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
- Can I see an older version of a script from materialize.com?
- Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
- Which other websites use the same tracking IDs as materialize.com?
- Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.
Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.