Site profile
colonial-beach.jp
Built with jquery 2.1.0, gtm, @accessible360/accessible-slick 1.0.1, jquery-match-height 0.7.2, jquery-colorbox 1.6.4, google-maps, slick-slider 1.8.2, @vitest/utils 5.0.2, google-maps-utility-library-v3-infobox 1.1.14, google-maps-infobox 2.0.0. 5 pages and 13 stored files, last crawled 2026-10-09.
rank 14,731,609 10 libraries 1 identifier 11 third-party hosts 1 crawl 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 |
|---|---|---|
| jquery | 2.1.0 | 2026-10-09 |
| gtm | 2026-10-09 | |
| @accessible360/accessible-slick | 1.0.1 | 2026-10-09 |
| jquery-match-height | 0.7.2 | 2026-10-09 |
| jquery-colorbox | 1.6.4 | 2026-10-09 |
| google-maps | 2026-10-09 | |
| slick-slider | 1.8.2 | 2026-10-09 |
| @vitest/utils | 5.0.2 | 2026-10-09 |
| google-maps-utility-library-v3-infobox | 1.1.14 | 2026-10-09 |
| google-maps-infobox | 2.0.0 | 2026-10-09 |
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-N22V7CP | view source |
Third-party hosts
Hosts outside colonial-beach.jp that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.
| Host | Loaded as | Found in |
|---|---|---|
| ajax.googleapis.com | script | view source |
| cdnjs.cloudflare.com | stylesheet | view source |
| connect.facebook.net | script | view source |
| fonts.googleapis.com | stylesheet | view source |
| gate-series.com | script | view source |
| instawidget.net | script | view source |
| knowledgetags.yextpages.net | script | view source |
| maps.googleapis.com | script | view source |
| snapwidget.com | iframe | view source |
| www.google.com | iframe connect | view source |
| www.googletagmanager.com | iframe | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.
-
first crawl
5 pages, 13 files, 326.9 KB; 10 libraries, 1 identifier, 11 third-party hosts
10 libraries added
- gtm
- @vitest/utils 5.0.2
- @accessible360/accessible-slick 1.0.1
- slick-slider 1.8.2
- jquery-match-height 0.7.2
- jquery-colorbox 1.6.4
- google-maps-infobox 2.0.0
- google-maps-utility-library-v3-infobox 1.1.14
- jquery 2.1.0
- google-maps
1 identifier added
- GTM-N22V7CP Google Tag Manager container
12 third-party hosts added
13 files added
- https://colonial-beach.jp/minatomirai/ html
- https://colonial-beach.jp/minatomirai/news/ html
- https://colonial-beach.jp/minatomirai/menu/dinner/ html
- https://colonial-beach.jp/minatomirai/wedding/ html
- https://colonial-beach.jp/minatomirai/gallery/ html
- https://colonial-beach.jp/assets/js/slick/slick.min.js js
- https://colonial-beach.jp/assets/js/jquery.matchHeight.js js
- https://colonial-beach.jp/assets/js/jquery.colorbox-min.js js
- https://colonial-beach.jp/assets/js/common.js js
- https://colonial-beach.jp/assets/js/infobox.js js
- https://colonial-beach.jp/assets/js/map.js js
- https://ajax.googleapis.com/ajax/libs/jquery/2.1.0/jquery.min.js js
- and 1 more
Questions about colonial-beach.jp
- How does PageSourceSearch know what colonial-beach.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 colonial-beach.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 colonial-beach.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 colonial-beach.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.