1 teknobilmedya.com Last Updated: 3 years

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

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

Minifying CSS files can reduce network payload sizes

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

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

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

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

This is the largest contentful element painted within the viewport

Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement

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

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

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

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

Remove unused JavaScript to reduce bytes consumed by network activity

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

Animations which are not composited can be janky and increase CLS

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

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

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

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

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)

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

Redirects introduce additional delays before the page can be loaded

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

Preload the image used by the LCP element in order to improve your LCP time

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).

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

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

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

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

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

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

Optimized images load faster and consume less cellular data

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

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