26 superhaber.tv Last Updated: 3 years

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

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

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

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

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

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

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

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

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

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

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

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

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

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

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

Animations which are not composited can be janky and increase CLS

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

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

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

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

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

Cumulative Layout Shift measures the movement of visible elements within the viewport

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

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

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

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

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

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

This is the largest contentful element painted within the viewport

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

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

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