Resource Analysis — Third-Party Domains, Images & CSS

What's actually loading on your page?

A typical webpage pulls in far more than just its own content — analytics scripts, fonts, chat widgets, ad networks, and images all add up. This module maps out exactly what your page depends on, which is useful both for performance (fewer, lighter resources load faster) and for understanding your privacy footprint (each third-party domain is a separate party potentially collecting data on your visitors).

What's reported

• Third-party domains — every external domain your page makes requests to, beyond your own.
• Image optimization — whether images are served in efficient, modern formats and reasonably sized for how they're displayed.
• CSS files — how many separate stylesheet files load, and whether they're reasonably organized rather than fragmented across many small requests.
• Inline CSS blocks — <style> blocks embedded directly in the page, counted separately from external files. A few are normal (critical above-the-fold CSS); a large number scattered through the page usually means styles that should be consolidated into a proper stylesheet.

Why this matters

Each third-party domain adds a DNS lookup, connection, and potential privacy consideration. It's worth periodically auditing which ones are still genuinely needed — scripts added for a one-time campaign or an abandoned integration often quietly linger long after they stopped providing value.