Your page performance is generally good, but there are opportunities to improve the Largest Contentful Paint (LCP) and initial load speed.
Performance Observations
Largest Contentful Paint (LCP): The LCP for the main navigation was 556 ms, with the LCP element being an icon image. The primary bottleneck is Resource Load Delay (126 ms) and Element Render Delay (127 ms).
Main Thread Efficiency: The main thread is frequently interrupted by third-party script execution, specifically from the Bitwarden Password Manager extension, which accounted for approximately 45 ms of activity during the initial load.
Network Protocol: The site is using HTTP/1.1. Modern protocols like HTTP/2 would allow for better multiplexing of resources, potentially reducing the time spent waiting for scripts and stylesheets to download.
Would you like to investigate how to optimize the LCP image delivery or how to reduce the impact of render-blocking resources?
Optimize LCP image discovery
To optimize LCP image discovery, focus on reducing the time between the start of navigation and when the browser begins downloading the LCP element.
Root Causes
Missing Fetch Priority: The LCP element (a PNG icon) does not use fetchpriority="high". This results in the browser assigning it a "Medium" priority, potentially delaying its download behind other resources.
Resource Load Delay: In NAVIGATION_2, there is a 126 ms delay between the document finishing its TTFB and the LCP image request being queued. This is often caused by the browser waiting for the preload scanner to find the URL or for main thread tasks to clear.
Protocol Overhead: The page uses HTTP/1.1 http://10.x.y.z:7990/img/heimdall-icon-small.png. This limits the number of concurrent requests the browser can handle, contributing to the queuing delay.
Suggestions
Add fetchpriority="high": Add this attribute directly to the ![]()
tag for the LCP element. This signals the browser to prioritize this request over other non-critical assets.
Use a Modern Protocol: Upgrade the server to support HTTP/2 or HTTP/3. This allows for request multiplexing, which would eliminate the head-of-line blocking seen with HTTP/1.1 and reduce the 126 ms load delay.
Optimize Image Format: The LCP element is a PNG. Consider using WebP or AVIF, which would reduce the 137 ms load duration by lowering the file size.
Improve Caching: The LCP resource currently has no Cache-Control header (or it's not being utilized for repeat visits), leading to wasted time re-downloading the same icon on every navigation.
Can any setting affect this ? Or do we need to fix it somehow?
Your page performance is generally good, but there are opportunities to improve the Largest Contentful Paint (LCP) and initial load speed.
Performance Observations
Largest Contentful Paint (LCP): The LCP for the main navigation was 556 ms, with the LCP element being an icon image. The primary bottleneck is Resource Load Delay (126 ms) and Element Render Delay (127 ms).
Main Thread Efficiency: The main thread is frequently interrupted by third-party script execution, specifically from the Bitwarden Password Manager extension, which accounted for approximately 45 ms of activity during the initial load.
Network Protocol: The site is using HTTP/1.1. Modern protocols like HTTP/2 would allow for better multiplexing of resources, potentially reducing the time spent waiting for scripts and stylesheets to download.
Would you like to investigate how to optimize the LCP image delivery or how to reduce the impact of render-blocking resources?
Optimize LCP image discovery
To optimize LCP image discovery, focus on reducing the time between the start of navigation and when the browser begins downloading the LCP element.
Root Causes![]()
tag for the LCP element. This signals the browser to prioritize this request over other non-critical assets.
Missing Fetch Priority: The LCP element (a PNG icon) does not use fetchpriority="high". This results in the browser assigning it a "Medium" priority, potentially delaying its download behind other resources.
Resource Load Delay: In NAVIGATION_2, there is a 126 ms delay between the document finishing its TTFB and the LCP image request being queued. This is often caused by the browser waiting for the preload scanner to find the URL or for main thread tasks to clear.
Protocol Overhead: The page uses HTTP/1.1 http://10.x.y.z:7990/img/heimdall-icon-small.png. This limits the number of concurrent requests the browser can handle, contributing to the queuing delay.
Suggestions
Add fetchpriority="high": Add this attribute directly to the
Use a Modern Protocol: Upgrade the server to support HTTP/2 or HTTP/3. This allows for request multiplexing, which would eliminate the head-of-line blocking seen with HTTP/1.1 and reduce the 126 ms load delay.
Optimize Image Format: The LCP element is a PNG. Consider using WebP or AVIF, which would reduce the 137 ms load duration by lowering the file size.
Improve Caching: The LCP resource currently has no Cache-Control header (or it's not being utilized for repeat visits), leading to wasted time re-downloading the same icon on every navigation.
Can any setting affect this ? Or do we need to fix it somehow?