Chrome's field data for the site as a whole — every page Chrome users visited over the last 28 days — misses the good threshold on at least one Core Web Vital. Pages without enough traffic for their own record are assessed by Google using this origin-level figure, so a failing origin affects the long tail of the site, not only its busiest pages. A site-wide failure points to something shared: the server, the template, a common script or a global stylesheet.
One slow template element — a render-blocking tag manager in the shared head, an unsized header banner — is repeated on every page, so every page inherits the same cost:
<head>
<script src="https://tags.example/tm.js"></script>
<link rel="stylesheet" href="/all-pages.css">
</head>Find the metric that fails, then fix it in the shared layout rather than page by page. Start with the pages reported individually in this crawl: the cause they have in common is usually the site-wide one:
<head>
<link rel="stylesheet" href="/critical.css">
<script src="https://tags.example/tm.js" async></script>
</head>An origin's figures are the aggregate of all its page views, so they move when the experience of the typical page moves. A fix in the shared template reaches every page at once, which is the only way to shift an aggregate across thousands of URLs.
This issue can affect your site's search engine rankings and user experience. Addressing it promptly helps ensure optimal performance and visibility in search results.
bseoa automatically checks for this warning during site analysis, along with hundreds of other technical SEO issues.
Choose the license that fits your needs and start getting the deep, actionable insights you deserve.