Site profile
hoshizaki.co.jp
Built with swiper 11, gsap 3.12.2, jquery 3.6.0, gtm, gtag, alpinejs 3.17.4, jquery-cookie 1.4.1, @epigraph/configurator 2.7.0, @teamepyc/sliders 0.9.5-alpha, @imshaiksaif/webflow-marquee 3.0.1, @bikematrix/web-components 1.3.23, @flowbase-co/boosters-gsap 3.12.7 and more. 4 pages and 27 stored files.
rank 411,877 15 libraries 3 identifiers 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 |
|---|---|---|
| swiper | 11 | 2026-09-24 |
| gsap | 3.12.2 | 2026-09-24 |
| jquery | 3.6.0 | 2026-09-24 |
| gtm | 2026-09-24 | |
| gtag | 2026-09-24 | |
| alpinejs | 3.17.4 | 2026-09-24 |
| jquery-cookie | 1.4.1 | 2026-09-24 |
| @epigraph/configurator | 2.7.0 | 2026-09-24 |
| @teamepyc/sliders | 0.9.5-alpha | 2026-09-24 |
| @imshaiksaif/webflow-marquee | 3.0.1 | 2026-09-24 |
| @bikematrix/web-components | 1.3.23 | 2026-09-24 |
| @flowbase-co/boosters-gsap | 3.12.7 | 2026-09-24 |
| @gemeosagency/splide | 3.7.0 | 2026-09-24 |
| imagemapster | 1.9.2 | 2026-09-24 |
| @mgdis/mg-components | 6.29.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 Ads conversion id (Google) | AW-934558341 | view source |
| Google Ads conversion id (Google) | AW-960987803 | view source |
| Google Tag Manager container (Google) | GTM-KVQCKB2 | view source |
Third-party hosts
The stored pages and scripts reference no host outside hoshizaki.co.jp.
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 hoshizaki.co.jp
- How does PageSourceSearch know what hoshizaki.co.jp 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 hoshizaki.co.jp 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 hoshizaki.co.jp?
- 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 hoshizaki.co.jp?
- 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.