Site profile
langstone-hotel.co.uk
Built with gtm, player-venom 0.3.6, jquery-ui 1.14.2, dashjs 5.2.1, @tabler/core 1.5.1, recaptcha, jquery-ui-dist 1.13.3, universalviewer 4.4.4, jsxgraph 1.13.3, accessible-autocomplete 3.0.1, volantis-static 0.0.1761982841160, jquery.flipster 1.1.6 and more. 5 pages and 16 stored files, last crawled 2026-10-07.
rank 12,988,745 16 libraries 3 identifiers 22 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 |
|---|---|---|
| gtm | 2026-10-07 | |
| player-venom | 0.3.6 | 2026-10-07 |
| jquery-ui | 1.14.2 | 2026-10-07 |
| dashjs | 5.2.1 | 2026-10-07 |
| @tabler/core | 1.5.1 | 2026-10-07 |
| recaptcha | 2026-10-07 | |
| jquery-ui-dist | 1.13.3 | 2026-10-07 |
| universalviewer | 4.4.4 | 2026-10-07 |
| jsxgraph | 1.13.3 | 2026-10-07 |
| accessible-autocomplete | 3.0.1 | 2026-10-07 |
| volantis-static | 0.0.1761982841160 | 2026-10-07 |
| jquery.flipster | 1.1.6 | 2026-10-07 |
| @vitest/utils | 5.0.2 | 2026-10-07 |
| chobitsu | 1.8.6 | 2026-10-07 |
| @lanyundev/blog-static | 1.4.18 | 2026-10-07 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-07 |
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-KFPMWFVF | view source |
| Google Tag Manager container (Google) | GTM-TQT3D3Z | view source |
| reCAPTCHA site key (Google) | 6Lfaj90eAAAAAHABiLTXqF_x-ksQJKmYsGHuFUWx | view source |
Third-party hosts
Hosts outside langstone-hotel.co.uk 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 |
|---|---|---|
| app.responseiq.com | script | view source |
| bsky.app | connect | view source |
| calendly.com | connect | view source |
| core.service.elfsight.com | connect | view source |
| dash.elfsight.com | connect | view source |
| facebook.com | connect | view source |
| fonts.googleapis.com | stylesheet | view source |
| github.com | connect | view source |
| instagram.com | connect | view source |
| linkedin.com | connect | view source |
| plus.google.com | connect | view source |
| profiles.wordpress.org | connect | view source |
| savvycal.com | connect | view source |
| static.hotjar.com | connect | view source |
| threads.net | connect | view source |
| tiktok.com | connect | view source |
| twitter.com | connect | view source |
| wa.me | connect | view source |
| www.facebook.com | connect | view source |
| www.google.com | script | view source |
| www.googletagmanager.com | iframe | view source |
| youtube.com | 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
5 pages, 16 files, 4.2 MB; 16 libraries, 3 identifiers, 22 third-party hosts
16 libraries added
- gtm
- @vitest/utils 5.0.2
- recaptcha
- jquery.flipster 1.1.6
- @grigorov-it/mazer 2.2.0
- jsxgraph 1.13.3
- @lanyundev/blog-static 1.4.18
- universalviewer 4.4.4
- volantis-static 0.0.1761982841160
- jquery-ui 1.14.2
- jquery-ui-dist 1.13.3
- player-venom 0.3.6
- and 4 more
3 identifiers added
- GTM-TQT3D3Z Google Tag Manager container
- GTM-KFPMWFVF Google Tag Manager container
- 6Lfaj90eAAAAAHABiLTXqF_x-ksQJKmYsGHuFUWx reCAPTCHA site key
22 third-party hosts added
16 files added
- https://www.langstone-hotel.co.uk/ html
- https://www.langstone-hotel.co.uk/about-us/awards/ html
- https://www.langstone-hotel.co.uk/contact/ html
- https://www.langstone-hotel.co.uk/customer-reviews/ html
- https://www.langstone-hotel.co.uk/business/ html
- https://www.langstone-hotel.co.uk/wordpress/wp-i…/jquery/jquery.min.js?ver=3.7.1 js
- https://www.langstone-hotel.co.uk/wordpress/wp-i…jquery-migrate.min.js?ver=3.4.1 js
- https://www.langstone-hotel.co.uk/wordpress/wp-i…?ver=f0f188028580e8dc1255 js
- https://www.langstone-hotel.co.uk/wordpress/wp-i…?ver=1dfe7db3940c23ea9216 js
- https://www.langstone-hotel.co.uk/content/plugin…/jquery.json.min.js?ver=3.1.2 js
- https://www.langstone-hotel.co.uk/content/plugin…/17.8.3/lazyload.min.js js
- https://www.langstone-hotel.co.uk/content/cache/…8fe5b9aa54065ec4faf43d729c63.js js
- and 4 more
Questions about langstone-hotel.co.uk
- How does PageSourceSearch know what langstone-hotel.co.uk 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 langstone-hotel.co.uk 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 langstone-hotel.co.uk?
- 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 langstone-hotel.co.uk?
- 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.