WhoisIs a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

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

Initial server response time was short
Root document took 390 ms

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

Avoid enormous network payloads
Total size was 3,104 KB

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

Cumulative Layout Shift
1

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

JavaScript execution time
0.1 s

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

Estimated Input Latency
10 ms

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

Eliminate render-blocking resources
Potential savings of 440 ms

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

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Largest Contentful Paint element
1 element found

This is the element that was identified as the Largest Contentful Paint

Serve images in next-gen formats
Potential savings of 1,560 KB

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

First Contentful Paint
0.8 s

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

Remove unused JavaScript
Potential savings of 406 KB

Remove unused JavaScript to reduce bytes consumed by network activity

Avoid chaining critical requests
13 chains found

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

Remove unused CSS
Potential savings of 223 KB

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

Minify CSS
Potential savings of 49 KB

Minifying CSS files can reduce network payload sizes

First CPU Idle
0.8 s

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

Móvel

Minify CSS
Potential savings of 49 KB

Minifying CSS files can reduce network payload sizes

Avoid enormous network payloads
Total size was 3,105 KB

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

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

Server Backend Latencies
0 ms

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

Remove unused CSS
Potential savings of 223 KB

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

Estimated Input Latency
10 ms

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

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

Serve static assets with an efficient cache policy
35 resources found

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

Network Round Trip Times
0 ms

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

Avoid chaining critical requests
13 chains found

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

First CPU Idle
6.8 s

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

JavaScript execution time
0.6 s

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

Remove unused JavaScript
Potential savings of 400 KB

Remove unused JavaScript to reduce bytes consumed by network activity

Avoid large layout shifts
1 element found

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

Document uses legible font sizes
93.84% legible text

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

Links do not have descriptive text
1 link found

Descriptive link text helps search engines understand your content

Max Potential First Input Delay
210 ms

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

First Meaningful Paint
3.3 s

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