Site profile
lamella.nl
Built with gtm, vanilla-lazyload 19.1.3, jquery-ui 1.14.2, dashjs 5.2.1, @tabler/core 1.5.1, jquery-ui-dist 1.13.3, @silvermine/videojs-quality-selector 1.3.1, adaptivecards 3.0.6, hubspot, dygraphs 2.2.2, sourcebuster 1.1.0, jsxgraph 1.13.3 and more. 5 pages and 81 stored files, last crawled 2026-10-08.
rank 13,700,717 27 libraries 2 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-08 | |
| vanilla-lazyload | 19.1.3 | 2026-10-08 |
| jquery-ui | 1.14.2 | 2026-10-08 |
| dashjs | 5.2.1 | 2026-10-08 |
| @tabler/core | 1.5.1 | 2026-10-08 |
| jquery-ui-dist | 1.13.3 | 2026-10-08 |
| @silvermine/videojs-quality-selector | 1.3.1 | 2026-10-08 |
| adaptivecards | 3.0.6 | 2026-10-08 |
| hubspot | 2026-10-08 | |
| dygraphs | 2.2.2 | 2026-10-08 |
| sourcebuster | 1.1.0 | 2026-10-08 |
| jsxgraph | 1.13.3 | 2026-10-08 |
| jquery.fancytree | 2.38.5 | 2026-10-08 |
| jquery.flipster | 1.1.6 | 2026-10-08 |
| @vitest/utils | 5.0.2 | 2026-10-08 |
| framework7 | 9.1.3 | 2026-10-08 |
| mammoth-plus | 2.0.2 | 2026-10-08 |
| krds-uiux | 1.1.0 | 2026-10-08 |
| guidechimp | 5.0.5 | 2026-10-08 |
| chobitsu | 1.8.6 | 2026-10-08 |
| analytics-client | 3.2.0 | 2026-10-08 |
| blockui | 1.0.0 | 2026-10-08 |
| @crystaldesign/diva-core | 26.11.0 | 2026-10-08 |
| wonder-image | 2.1.2-alpha.4 | 2026-10-08 |
| @fsl-app/erm-app | 1.1.3 | 2026-10-08 |
| @lanyundev/blog-static | 1.4.18 | 2026-10-08 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-08 |
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-MMBSR8MC | view source |
| HubSpot portal id (HubSpot) | 145884532 | view source |
Third-party hosts
Hosts outside lamella.nl 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 |
|---|---|---|
| bsky.app | connect | view source |
| calendly.com | connect | view source |
| facebook.com | connect | view source |
| github.com | connect | view source |
| i.ytimg.com | connect | view source |
| instagram.com | connect | view source |
| js-eu1.hs-analytics.net | connect | view source |
| js-eu1.hs-banner.com | connect | view source |
| js-eu1.hsadspixel.net | connect | view source |
| js-eu1.hscollectedforms.net | connect | view source |
| js.hs-scripts.com | script | view source |
| linkedin.com | connect | view source |
| player.vimeo.com | connect | view source |
| profiles.wordpress.org | connect | view source |
| savvycal.com | connect | view source |
| threads.net | connect | view source |
| tiktok.com | connect | view source |
| v1.widget.futy.io | connect | view source |
| wa.me | connect | view source |
| www.googletagmanager.com | iframe | view source |
| www.w3.org | connect | 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, 81 files, 2.3 MB; 27 libraries, 2 identifiers, 22 third-party hosts
27 libraries added
- gtm
- @vitest/utils 5.0.2
- jquery.flipster 1.1.6
- @grigorov-it/mazer 2.2.0
- jsxgraph 1.13.3
- blockui 1.0.0
- analytics-client 3.2.0
- @lanyundev/blog-static 1.4.18
- wonder-image 2.1.2-alpha.4
- vanilla-lazyload 19.1.3
- krds-uiux 1.1.0
- @fsl-app/erm-app 1.1.3
- and 15 more
2 identifiers added
- GTM-MMBSR8MC Google Tag Manager container
- 145884532 HubSpot portal id
22 third-party hosts added
81 files added
- https://lamella.nl/ html
- https://lamella.nl/product/handbediende-screens/ html
- https://lamella.nl/blogs/ html
- https://lamella.nl/mijn-account/ html
- https://lamella.nl/contact/ html
- https://lamella.nl/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 js
- https://lamella.nl/wp-content/litespeed/js/1/d0d…62e7fae1208aa83a34.js?ver=e1606 js
- https://lamella.nl/wp-content/litespeed/js/1/3b5…445da135b8788d7583.js?ver=052c3 js
- https://lamella.nl/wp-content/litespeed/js/1/4ee…92f5fde81a15a2e5a7.js?ver=72c67 js
- https://lamella.nl/wp-content/litespeed/js/1/8b3…3c3e1fbca9c05e7d1a.js?ver=5c2d1 js
- https://lamella.nl/wp-content/litespeed/js/1/812…687a9f42cba5fdfef5.js?ver=c2e6d js
- https://lamella.nl/wp-content/litespeed/js/1/6f4…0a63967e354365d58f.js?ver=5d58f js
- and 69 more
Questions about lamella.nl
- How does PageSourceSearch know what lamella.nl 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 lamella.nl 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 lamella.nl?
- 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 lamella.nl?
- 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.