This means that the URL in question is a resource URL that is being redirected to a different location.
Why is this important?
When a URL is redirected—usually via a 301 (permanent) or 302 (temporary) status code—it signifies that the page's location has been altered, necessitating a new URL to be visited by the user.
What does the Optimization check?
This Optimization will be activated for any page resource URL that is redirected.
Examples that trigger this Optimization:
Take the resource URL: https://example.com/css/body.css
This Optimization would activate if a 3XX HTTP header response, such as a 301, were to be returned by any URL;
HTTP/... 301 Moved Permanently...Location: https://example.com/css/body2.css
How do you resolve this issue?
Page resource redirects could be a sign of content failing to load correctly, which might lead to suboptimal experiences for visitors. Additionally, since search engines like Google prioritize rendering in their indexing, inaccessible resources essential for rendering could impact content ranking.
Resource URLs should aim for direct access without redirections to minimize loading times and potential rendering issues.
Presuming the final URL is accurate, remedying this issue would involve amending the href attribute within all tags pointing to the resource, redirecting them to the current URL.
How do you get more data from Sitebulb?
To tackle this problem, one must locate and modify every incoming URL that points to the erroneous resource.
This can be done by selecting the 'View' option found within the URL List, in the 'No. URLs Referencing Resource' column.