stats

Type: <boolean>
Default: false
Get perfomance metrics over the website powered by .
microlink-api https://zeit.co&stats
Enabling it adds a new field stats present into the data payload with a set of perfomance metrics oriented to detect bottlenecks and improve the perceive page load.
These metrics are:
  • : First Contentful Paint marks the time at which the first text or image is painted.
  • : First Meaningful Paint measures when the primary content of a page is visible.
  • : Speed Index shows how quickly the contents of a page are visibly populated.
  • : 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.
  • total-blocking-time: Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
  • : The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task.
  • : Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns.
  • : Time To First Byte identifies the time at which your server sends a response.
  • : First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input..
  • : Time to interactive is the amount of time it takes for the page to become fully interactive.
  • : Redirects introduce additional delays before the page can be loaded.
  • : Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
  • : Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load.
  • : Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins.
  • : 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.
  • : 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.
  • : To set budgets for the quantity and size of page resources, add a budget.json file.
  • : Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute.
  • : A large DOM will increase memory usage, cause longer , and produce costly .
  • : HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push.
  • : Meta descriptions may be included in search results to concisely summarize page content.

stats

Type: <boolean>
Default: false
Get perfomance metrics over the website powered by .
microlink-api https://zeit.co&stats
Enabling it adds a new field stats present into the data payload with a set of perfomance metrics oriented to detect bottlenecks and improve the perceive page load.
These metrics are:
  • : First Contentful Paint marks the time at which the first text or image is painted.
  • : First Meaningful Paint measures when the primary content of a page is visible.
  • : Speed Index shows how quickly the contents of a page are visibly populated.
  • : 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.
  • total-blocking-time: Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
  • : The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task.
  • : Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns.
  • : Time To First Byte identifies the time at which your server sends a response.
  • : First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input..
  • : Time to interactive is the amount of time it takes for the page to become fully interactive.
  • : Redirects introduce additional delays before the page can be loaded.
  • : Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
  • : Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load.
  • : Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins.
  • : 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.
  • : 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.
  • : To set budgets for the quantity and size of page resources, add a budget.json file.
  • : Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute.
  • : A large DOM will increase memory usage, cause longer , and produce costly .
  • : HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push.
  • : Meta descriptions may be included in search results to concisely summarize page content.
By using this website you agree to ourprivacy.