PageSourceSearch

Site profile

oriori-web.jp

Built with swiper, gtm, gtag, webpack, vue, axios, moment, clappr 0.3.13, regenerator-runtime, object-fit-images, process, core-js and more. 5 pages and 9 stored files, last crawled 2026-10-05.

rank 11,281,182 22 libraries 4 identifiers 8 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.

LibraryVersionSeen
swiper 2026-10-05
gtm 2026-10-05
gtag 2026-10-05
webpack 2026-10-05
vue 2026-10-05
axios 2026-10-05
moment 2026-10-05
clappr 0.3.13 2026-10-05
regenerator-runtime 2026-10-05
object-fit-images 2026-10-05
process 2026-10-05
core-js 2026-10-05
setimmediate 2026-10-05
timers-browserify 2026-10-05
vue-loader 2026-10-05
is-buffer 2026-10-05
dom7 2026-10-05
ssr-window 2026-10-05
scrollmonitor 2026-10-05
ftdomdelegate 2026-10-05
@vitest/utils 5.0.2 2026-10-05
katex-copytex 1.0.2 2026-10-05

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.

WhatValueFound in
AdSense publisher id (Google) ca-pub-9152381951615331 view source
Google site verification (Google) zA5OnlVeNGaynU6nK4wgFravTp6A7m45ALagBUP8I2s view source
Google Tag Manager container (Google) GTM-PVC9K84H view source
Universal Analytics property id (Google) UA-18525814-10 view source

Third-party hosts

Hosts outside oriori-web.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.

HostLoaded asFound in
bit.ly connect view source
github.com connect view source
momentjs.com connect view source
pagead2.googlesyndication.com script view source
vuejs.org connect view source
ws-fe.amazon-adsystem.com script view source
www.googletagmanager.com script iframe view source
www.w3.org connect view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 9) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

FileKindSizeCollectedVersions
https://oriori-web.jp/js/top.js js 753.2 KB 2026-10-05 2026-10-05
https://www.googletagmanager.com/gtag/js?id=UA-18525814-10 js library not fetched 2026-10-05 2026-10-05
https://oriori-web.jp/js/main.js js 1.5 MB 2026-10-05 2026-10-05
https://oriori-web.jp/wp/wp-includes/js/wp-embed.min.js?ver=5.2.21 js 1.4 KB 2026-10-05 2026-10-05
https://oriori-web.jp/about/ html 19.8 KB 2026-10-05 2026-10-05
https://oriori-web.jp/article/ html 36 KB 2026-10-05 2026-10-05
https://oriori-web.jp/news/pr20250319-1/ html 23.5 KB 2026-10-05 2026-10-05
https://oriori-web.jp/shop/ html 27.1 KB 2026-10-05 2026-10-05
https://oriori-web.jp/ html 56.2 KB 2026-10-05 2026-10-05

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.

  1. first crawl

    5 pages, 9 files, 2.4 MB; 22 libraries, 4 identifiers, 8 third-party hosts

    22 libraries added
    • gtag
    • gtm
    • @vitest/utils 5.0.2
    • clappr 0.3.13
    • axios
    • core-js
    • ftdomdelegate
    • is-buffer
    • moment
    • object-fit-images
    • process
    • regenerator-runtime
    • and 10 more
    4 identifiers added
    9 third-party hosts added
    9 files added

Questions about oriori-web.jp

How does PageSourceSearch know what oriori-web.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 oriori-web.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 oriori-web.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 oriori-web.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.