Site profile
jom.pt
Built with gtm, gtag, lozad 1.16.0, angular 1.8.3, recaptcha, kore-web-sdk 11.28.1, google-maps, layui 2.13.9, jsxgraph 1.13.3, @vitest/utils 5.0.2, stackedboost-shopify-assets 0.2.0, google-maps-utility-library-v3-infobox 1.1.14 and more. 4 pages and 23 stored files.
rank 3,586,946 16 libraries 2 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 |
|---|---|---|
| gtm | 2026-09-26 | |
| gtag | 2026-09-26 | |
| lozad | 1.16.0 | 2026-09-26 |
| angular | 1.8.3 | 2026-09-26 |
| recaptcha | 2026-09-26 | |
| kore-web-sdk | 11.28.1 | 2026-09-26 |
| google-maps | 2026-09-26 | |
| layui | 2.13.9 | 2026-09-26 |
| jsxgraph | 1.13.3 | 2026-09-26 |
| @vitest/utils | 5.0.2 | 2026-09-26 |
| stackedboost-shopify-assets | 0.2.0 | 2026-09-26 |
| google-maps-utility-library-v3-infobox | 1.1.14 | 2026-09-26 |
| h5p-standalone | 3.8.2 | 2026-09-26 |
| @pimaonline/pimaonline-themepack | 5.28.13 | 2026-09-26 |
| google-maps-infobox | 2.0.0 | 2026-09-26 |
| jquery-base64-js | 1.0.1 | 2026-09-26 |
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 Analytics 4 measurement id (Google) | G-MFBWB6X1KD | view source |
| Google Tag Manager container (Google) | GTM-53TCCQC | view source |
Third-party hosts
The stored pages and scripts reference no host outside jom.pt.
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 jom.pt
- How does PageSourceSearch know what jom.pt 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 jom.pt 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 jom.pt?
- 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 jom.pt?
- 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.