Page Atlas

Your page is a supply chain

A modern web page is rarely one server’s work. The HTML comes from your host, but the fonts arrive from a font CDN, the analytics script from a tracking company, the chat widget from a SaaS vendor, the hero video from a media host. Every one of those is a separate server, in a separate building, in a country you may never have thought about. Page Atlas makes that supply chain visible: paste a URL and watch the page assemble itself on a living 3D globe, every request an arc of light from the server that answered it to you.

Why third-party weight matters

Three reasons, and they compound.

Speed. Every extra host costs a DNS lookup, a TCP connection and a TLS handshake before the first byte arrives. A render-blocking script in your head tag from a slow third party can hold your whole page hostage. Trimming third-party requests is regularly the single biggest win in a performance audit, which is why our score weighs render-blocking third parties so heavily.

Privacy. Every tracker host on your page receives data about your visitors, usually including their IP address and what page they are reading. If you operate under GDPR or similar privacy regimes, the country table matters too: it shows every jurisdiction your visitors’ requests travel to just by opening your page. “Our homepage sends visitors to servers in seven countries” is a sentence your privacy policy should not be surprised by.

Resilience. A third-party script that goes down or gets compromised becomes your outage or your breach. The fewer outside hosts sitting between you and your visitors, the smaller your supply-chain attack surface. Our Website Security Scanner covers the header and TLS side of this; Page Atlas shows you the dependency map itself.

Reading the globe

The yellow pulsing pin is you. Every other pin is a server your page pulled something from, placed where its IP address geolocates. Arcs fire in document order, so the replay is a faithful little re-enactment of your page loading: styles and blocking scripts first, images and media behind them. Arc colour follows resource type (scripts, styles, images, fonts, frames), except trackers, which always burn red. CDN hosts wear a breathing halo ring: an anycast network answers from the edge nearest each visitor, so its pin shows the edge nearest our lookup rather than a fixed home, and we would rather show you an honest halo than a fake city.

Click any pin for the full story on that host: location, network, request count, measured bytes, and one-click deep links into our IP Lookup and DNS Lookup tools. The tables below the globe list every country and every host, sorted by weight, so the heaviest dependency is always at the top.

The Third-Party Weight score

The A to F grade uses the same scorecard scale as our SEO Analyzer and Security Scanner. Four sections feed it: the share of measurable bytes served by third parties, the raw third-party request count, the number of tracker hosts, and render-blocking third-party resources in the head of your page. Each fix pill under the score is concrete: which hosts to cut, which scripts to defer, what to self-host. When byte sizes cannot be measured (some servers refuse HEAD requests), that section is marked not applicable and its weight redistributes fairly instead of guessing.

What to do about a heavy page

Start with the biggest host in the table. If it is a widget or embed, ask whether it earns its bytes; many can be replaced with a static screenshot that loads the real thing on click. Move every analytics and marketing script to async or defer so nothing third-party blocks first paint. Self-host your fonts (font CDNs are two extra connections for something that almost never changes). And audit your trackers annually: they accumulate like barnacles, and every one you remove is a speed, privacy and resilience win at once.

For AI agents

This tool exposes a plain-text endpoint designed for language models and agents:

GET https://nitrosites.com/tools/page-atlas/scan.php?url=<target>&format=agent

It returns a token-cheap digest of the same analysis shown on this page: the Third-Party Weight score, resource and host counts, measured bytes, per-host classification (first or third party, tracker, CDN) and the findings list. Soft rate limits apply; results are cached briefly. No key or login required.

Frequently asked questions

What counts as a third-party resource?

Anything your page loads from a different registrable domain than the page itself, such as analytics scripts, ad tags, CDN-hosted libraries, embedded fonts and iframes. Each one adds latency, a privacy surface and a supply-chain dependency you do not control.

How accurate is the server location on the globe?

We resolve each hostname to its IP address and geolocate it with public IP databases, which is city-accurate for most ordinary hosts. CDN and anycast hosts answer from the edge nearest the viewer, so we badge those as CDN with a halo ring rather than pinning a false city.

Why do some hosts show in red?

Hosts on our curated tracker list (analytics, advertising and session-recording domains) are highlighted in red because they typically receive data about your visitors. Fewer trackers means faster pages and simpler privacy compliance.

Does this tool see everything the page loads?

It analyses the page's HTML, so resources injected later by JavaScript (for example tags loaded by Google Tag Manager) are not shown. Pair it with our Tag Explorer for tag-level depth, and our Nitro Speed Test for a full lab load.

What is a good Third-Party Weight score?

90 or above (an A) means a lean page that mostly serves itself. Below 60 usually means heavy tracker or ad load. The fix list under the score shows exactly which hosts to cut, defer or self-host first.