Site profile
theweddingconnect.com
Built with gtag, vue 3, swagger-ui-dist 5.33.0, facebook-pixel, @reachfive/identity-ui 2.1.0, @cognigy/webchat 3.50.0, @animuz/embed 0.2.9, tia-gpc-widget 3.1.1. 5 pages and 46 stored files, last crawled 2026-10-04.
rank 9,942,454 8 libraries 2 identifiers 38 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 |
|---|---|---|
| gtag | 2026-10-04 | |
| vue | 3 | 2026-10-04 |
| swagger-ui-dist | 5.33.0 | 2026-10-04 |
| facebook-pixel | 2026-10-04 | |
| @reachfive/identity-ui | 2.1.0 | 2026-10-04 |
| @cognigy/webchat | 3.50.0 | 2026-10-04 |
| @animuz/embed | 0.2.9 | 2026-10-04 |
| tia-gpc-widget | 3.1.1 | 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 |
|---|---|---|
| Meta pixel id (Meta) | 994126617285176 | view source |
| Google Analytics 4 measurement id (Google) | G-Z9BL6LMS1G | view source |
Third-party hosts
Hosts outside theweddingconnect.com 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.
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, 46 files, 1.3 MB; 8 libraries, 2 identifiers, 38 third-party hosts
8 libraries added
- facebook-pixel
- gtag
- tia-gpc-widget 3.1.1
- @cognigy/webchat 3.50.0
- @reachfive/identity-ui 2.1.0
- swagger-ui-dist 5.33.0
- @animuz/embed 0.2.9
- vue 3
2 identifiers added
- 994126617285176 Meta pixel id
- G-Z9BL6LMS1G Google Analytics 4 measurement id
38 third-party hosts added
46 files added
- https://theweddingconnect.com/ html
- https://theweddingconnect.com/category/bridal-shops html
- https://theweddingconnect.com/blog html
- https://theweddingconnect.com/category/bakeries html
- https://theweddingconnect.com/category/bands html
- https://theweddingconnect.com/assets/index-BXE52XGC.js js
- https://theweddingconnect.com/assets/vendor-BmWu54FF.js js
- https://theweddingconnect.com/assets/icons-99NBSVHi.js js
- https://theweddingconnect.com/assets/VendorsPage-BZip0nMz.js js
- https://theweddingconnect.com/assets/VendorDetailPage-Dg2iSkNa.js js
- https://theweddingconnect.com/assets/StateLandingPage-Z5iXmxhR.js js
- https://theweddingconnect.com/assets/CategoryLandingPage-DxXmb0oY.js js
- and 34 more
Questions about theweddingconnect.com
- How does PageSourceSearch know what theweddingconnect.com 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 theweddingconnect.com 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 theweddingconnect.com?
- 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 theweddingconnect.com?
- 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.