• Widgets
  • Reports
  • Pricing
  • FAQs
  • Sign up for a free trial!

Website Performance Audits

First Contentful Paint

First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. Learn more.

Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More

Time to Interactive

Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.

Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.

First CPU Idle

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.

Max Potential First Input Delay

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.

First Meaningful Paint

First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Estimated Input Latency

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.

Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn more.

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Remove unused CSS

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Remove unused JavaScript

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn more.

Serve images in next-gen formats

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Enable text compression

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

Preconnect to required origins

Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Initial server response time was short

Keep the server response time for the main document short because all other requests depend on it. Learn more.

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn more.

Preload key requests

Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn more.

Use HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more.

Use video formats for animated content

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

Remove duplicate modules in JavaScript bundles

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

Avoid serving legacy JavaScript to modern browsers

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 More

Avoids enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

Serve static assets with an efficient cache policy

A long cache lifetime can speed up repeat visits to your page. Learn more.

Avoids an excessive DOM size

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

Avoid chaining critical requests

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 more.

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Minimizes main-thread work

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

All text remains visible during webfont loads

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Performance budget

Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Timing budget

Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.

Keep request counts low and transfer sizes small

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Minimize third-party usage

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 more.

Largest Contentful Paint element

This is the largest contentful element painted within the viewport. Learn More

Avoid large layout shifts

These DOM elements contribute most to the CLS of the page.

Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more.

Avoid `document.write()`

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn more.

Avoid long main-thread tasks

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn more

Image elements do not have explicit `width` and `height`

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more

Avoids large JavaScript libraries with smaller alternatives

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size. Learn more.

Network Requests

Lists the network requests that were made during page load.

Network Round Trip Times

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.

Server Backend Latencies

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.


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


Collection of useful page vitals.


Collects all available metrics.

Screenshot Thumbnails

This is what the load of your site looked like.

Final Screenshot

The last screenshot captured of the pageload.


  • hello@webreports.io
  • Live chat

For customers