Executive Summary

Performance

Score: 49/100

Very low score; major improvements required.

Among the detected issues:

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

Accessibility

Score: 72/100

Acceptable, but improvements are recommended.

Best Practices

Score: 82/100

Good overall performance; minor tweaks possible.

Among the detected issues:

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

SEO

Score: 85/100

Good overall performance; minor tweaks possible.

Technical Analysis

Opportunities

Preload Largest Contentful Paint image

• Description: If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.

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

Minify JavaScript

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

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: 600 ms

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.
• Potential Savings: 11100 ms

Avoid multiple page redirects

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

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.

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 26 KiB

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: Root document took 60 ms

Remove duplicate modules in JavaScript bundles

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

Properly size images

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

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.
• Potential Savings: 7800 ms

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.

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.

Minify CSS

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

Diagnostics

Screenshot Thumbnails

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

Detected JavaScript libraries

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

Tasks

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

Script Treemap Data

• Description: Used for treemap app

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.

Resources Summary

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

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: 40 ms
• Numeric Value: 43

Avoid long main-thread tasks

• Description: Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
• Display Value: 8 long tasks found

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

Network Requests

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

Diagnostics

• Description: Collection of useful page vitals.

Final Screenshot

• Description: The last screenshot captured of the pageload.

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.

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 140 ms

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: 1 layout shift found

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: 10 ms
• Numeric Value: 12.160619999999998

Metrics

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

User Timing marks and measures

• Description: Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
• Display Value: 5 user timings

Report generated on 26/4/2025, 11:36:39