---
title: "Resource hint (LCP) (Help Center / Filters / Metric)"
ai_context: "Use this article for questions about the RUMvision Resource hint filter, preload strategies and whether Largest Contentful Paint (LCP) resources are being discovered and requested early enough. It explains how resource hints such as `link[rel=\"preload\"]` can reduce LCP Resource Load Delay, how RUMvision reports related attributes such as `as` and `fetchpriority`, and how the filter can reveal missing or inconsistent preload strategies for LCP resources. Relevant for questions about image preloading, resource discovery, `fetchpriority=\"high\"`, preload effectiveness, `crossorigin` mismatches, request reuse, LCP scheduling and comparing different resource hint configurations."
canonical: "https://www.rumvision.com/help-center/filters/metric/metric_resourcehint/"
---

Breadcrumbs: [Home](https://www.rumvision.com/?format=md) > [Help Center](https://www.rumvision.com/help-center/?format=md) > [Filters](https://www.rumvision.com/help-center/filters/?format=md) > [Metric](https://www.rumvision.com/help-center/filters/metric/?format=md) > Resource hint (LCP)

# Resource hint (LCP)

> This filter works with the [Largest Contentful Paint metric](https://www.rumvision.com/help-center/glossary/metrics/largest-contentful-paint/?format=md)

When an LCP resource is discovered too late, a resource hint such as `link[rel="preload"]` can help the browser discover and request it earlier. This can reduce LCP Resource Load Delay, especially for important images that would otherwise only be discovered later in the loading process.

The Resource hint filter shows whether a resource hint was found for the LCP resource and can include related attributes such as `as` and `fetchpriority`. This allows you to compare different preload strategies and identify LCP resources that are missing an expected resource hint or attribute.

For LCP images, a preload should generally use `fetchpriority="high"` as well. Also review attributes such as `crossorigin` carefully, as an unnecessary or mismatching `crossorigin` value can prevent the preload request from being reused for the actual image request.