Site profile
e-look.jp
Built with swiper 4.4.5, gtm, gtag, load-awesome 1.1.0, velocity-animate 1.5.2, fancybox 3.0.1, facebook-pixel, anfuns-assets 1.0.10, flexslider 2.7.2, odometer 0.4.8, iscroll 5.1.3, ui-cropper 1.0.9 and more. 4 pages and 27 stored files, last crawled 2026-10-04.
rank 10,175,696 16 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.
| Library | Version | Seen |
|---|---|---|
| swiper | 4.4.5 | 2026-10-04 |
| gtm | 2026-10-04 | |
| gtag | 2026-10-04 | |
| load-awesome | 1.1.0 | 2026-10-04 |
| velocity-animate | 1.5.2 | 2026-10-04 |
| fancybox | 3.0.1 | 2026-10-04 |
| facebook-pixel | 2026-10-04 | |
| anfuns-assets | 1.0.10 | 2026-10-04 |
| flexslider | 2.7.2 | 2026-10-04 |
| odometer | 0.4.8 | 2026-10-04 |
| iscroll | 5.1.3 | 2026-10-04 |
| ui-cropper | 1.0.9 | 2026-10-04 |
| @vitest/utils | 5.0.2 | 2026-10-04 |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-04 |
| jquery-drawer | 3.2.2 | 2026-10-04 |
| velocity-ui-pack | 1.2.2 | 2026-10-04 |
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-985680979 | view source |
| Meta pixel id (Meta) | 1473935886270405 | view source |
| Meta pixel id (Meta) | 1668558393459488 | view source |
| Google Tag Manager container (Google) | GTM-MLJF4H2 | view source |
Third-party hosts
Hosts outside e-look.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 |
|---|---|---|
| b92.yahoo.co.jp | script | view source |
| bnr.cl.unisize.makip.co.jp | script | view source |
| cdnjs.cloudflare.com | script stylesheet | view source |
| fonts.googleapis.com | stylesheet | view source |
| fspark-ap.com | script | view source |
| look-for-ec.prd.saas-ros.jp | 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) {
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
4 pages, 27 files, 1.4 MB; 16 libraries, 4 identifiers, 8 third-party hosts
16 libraries added
- gtm
- facebook-pixel
- gtag
- stackedboost-shopify-assets 0.2.0
- swiper 4.4.5
- @vitest/utils 5.0.2
- ui-cropper 1.0.9
- jquery-drawer 3.2.2
- load-awesome 1.1.0
- velocity-ui-pack 1.2.2
- velocity-animate 1.5.2
- anfuns-assets 1.0.10
- and 4 more
4 identifiers added
- GTM-MLJF4H2 Google Tag Manager container
- 1473935886270405 Meta pixel id
- 1668558393459488 Meta pixel id
- AW-985680979 Google Ads conversion id
10 third-party hosts added
27 files added
- https://www.e-look.jp/ html
- https://www.e-look.jp/login html
- https://www.e-look.jp/search html
- https://www.e-look.jp/shop/keith/%E3%83%9F%E3%83…/view/shop_product_id/154342 html
- https://www.e-look.jp/assets/js/jquery-1.11.1.min.js js
- https://www.e-look.jp/assets/js/staticCheckLogin.js js
- https://www.e-look.jp/assets/drawer/js/drawer.js js
- https://www.e-look.jp/assets/js/jquery.velocity.js js
- https://www.e-look.jp/assets/bootstrap/js/bootstrap.js js
- https://www.e-look.jp/assets/boxer-master/jquery.fs.boxer.js js
- https://www.e-look.jp/assets/swiper/js/swiper.min.js js
- https://www.e-look.jp/assets/flexslider/jquery.flexslider.js js
- and 15 more
Questions about e-look.jp
- How does PageSourceSearch know what e-look.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 e-look.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 e-look.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 e-look.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.