Report loading
www.silverback.agency
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Fair
Health Score
Score by category
The headline health score combines page-level quality and site-wide repeat patterns, then stays anchored to the weakest visible category so it never looks worse than every category beneath it.
Section 01
Summary language has been tempered to match the structured findings: this scan does not contain any CRITICAL severity findings.
Silverback Studios maintains a high-impact visual identity and exceptional initial loading speeds, but extreme page weight and third-party script bloat threaten long-term scalability and user experience.
The site excels in brand consistency and foundational SEO, utilizing a bold typography-driven design and comprehensive Organization schema to establish immediate authority. On both desktop and mobile, the hero sections deliver a high-impact visual hierarchy that clearly communicates value, supported by excellent Largest Contentful Paint (LCP) scores on the homepage.
However, massive payload sizes represent a serious failure in performance optimization. On the /the-troop page, the total weight reaches 10.8 MB—far exceeding the 2 MB industry standard—driven largely by heavy third-party loads and excessive HTTP requests. This bloat is compounded by significant Cumulative Layout Shift (CLS) on desktop, caused by images lacking explicit dimensions, which destabilizes the visual experience during loading. Furthermore, the DOM size is excessively large across all views, creating a heavy computational burden for browsers.
The primary opportunity lies in aggressive asset and script orchestration to reclaim performance margins. By auditing and pruning the 10+ MB of third-party dependencies and optimizing font-loading strategies, the agency can drastically reduce DNS overhead and prevent render-blocking delays. Streamlining these assets will stabilize the layout and ensure the premium brand experience remains fluid on slower mobile networks.
First 30 Days
webfont.js dependency with modern CSS loading techniques.5 highest-impact findings, ranked.
The loader element contains an image with `loading='eager'` and `fetchpriority='high'` for a `.gif` file (`mukunda-walks.gif`). Loading large, animated GIFs at high priority competes with the rendering of critical CSS and the LCP element, which can delay First Contentful Paint (FCP).
How to fix: Change the `loading` attribute to `loading='lazy'` for the loader GIF and remove `'high'` from `fetchpriority`. The loader should be visible only after the initial page load is complete.
On /services
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
How to fix: Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
On /the-troop
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
How to fix: Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
On /services
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
How to fix: Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
On /
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
How to fix: Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
On /