Executive Summary

Performance

Score: 83/100

Good overall performance; minor tweaks possible.

Among the detected issues:

• Some CSS rules are unused.
• Stylesheets are unminified, impacting load time.
• Scripts are unminified, increasing payload size.
• Text compression (gzip, brotli) not enabled.
• Unused JavaScript detected.
• There are resources blocking the initial render; inline or defer them.
• Server response time is slow (TTFB).
• Images are not compressed/optimized, affecting load times.

Accessibility

Score: 80/100

Good overall performance; minor tweaks possible.

Best Practices

Score: 96/100

Excellent result in this category.

Among the detected issues:

• Missing adequate CSP headers against XSS.
• Potential vulnerabilities in third‑party JS libraries.

SEO

Score: 92/100

Excellent result in this category.

Technical Analysis

Opportunities

Reduce unused CSS

• Description: Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
• Potential Savings: Potential savings of 13 KiB

Minify CSS

• Description: Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Properly size images

• Description: Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

Use video formats for animated content

• Description: Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats

Avoid serving legacy JavaScript to modern browsers

• Description: Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScript
• Potential Savings: Potential savings of 0 KiB

Remove duplicate modules in JavaScript bundles

• Description: Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Minify JavaScript

• Description: Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Preconnect to required origins

• Description: Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.

Enable text compression

• Description: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

Reduce unused JavaScript

• Description: Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Eliminate render-blocking resources

• Description: Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
• Potential Savings: Potential savings of 0 ms

Initial server response time was short

• Description: Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
• Potential Savings: 63 ms

Efficiently encode images

• Description: Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

Avoid multiple page redirects

• Description: Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
• Potential Savings: 780 ms

Serve images in next-gen formats

• Description: Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

Defer offscreen images

• Description: Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

Diagnostics

Mitigate clickjacking with XFO or CSP

• Description: The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.

Final Screenshot

• Description: The last screenshot captured of the pageload.

Identical links have the same purpose.

• Description: Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.

Diagnostics

• Description: Collection of useful page vitals.

Ensure CSP is effective against XSS attacks

• Description: A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS

Resources Summary

• Description: Aggregates all network requests and groups them by type

Network Requests

• Description: Lists the network requests that were made during page load.

Minimize third-party usage

• Description: Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
• Display Value: Third-party code blocked the main thread for 0 ms

Ensure proper origin isolation with COOP

• Description: The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.

Network Round Trip Times

• Description: Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
• Display Value: 0 ms
• Numeric Value: 0.0020448538795496633

Tasks

• Description: Lists the toplevel main thread tasks that executed during page load.

Screenshot Thumbnails

• Description: This is what the load of your site looked like.

Avoid large layout shifts

• Description: These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
• Display Value: 2 layout shifts found

Metrics

• Description: Collects all available metrics.
• Numeric Value: 2883

Use a strong HSTS policy

• Description: Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.

Script Treemap Data

• Description: Used for treemap app

Detected JavaScript libraries

• Description: All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.

Avoid chaining critical requests

• Description: The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
• Display Value: 8 chains found

Document has a main landmark.

• Description: One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Server Backend Latencies

• Description: Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
• Display Value: 0 ms
• Numeric Value: 2

Report generated on 26/4/2025, 12:47:26