Lighthouse Report

Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.

0–49 50–89 90–100

First Contentful Paint

0.3 s

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

Largest Contentful Paint

0.6 s

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

Total Blocking Time

90 ms

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

Cumulative Layout Shift

0.097

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

Speed Index

1.0 s

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

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCP

Use Webpack Bundle Analyzer to detect unused JavaScript code. Learn more

URL	Transfer Size	Potential Savings
Google/Doubleclick Ads ad	188.8 KiB	116.5 KiB
…m202…/show_ads_impl_fy2021.js?bust=31087333 (pagead2.googlesyndication.com)	137.4 KiB	95.4 KiB
…js/adsbygoogle.js (pagead2.googlesyndication.com)	51.3 KiB	21.1 KiB
Google Tag Manager tag-manager	94.2 KiB	34.7 KiB
/gtag/js?id=G-05B334ER0M (www.googletagmanager.com)	94.2 KiB	34.7 KiB

These suggestions can help your page load faster. They don't directly affect the Performance score.

User Timing marks and measures 7 user timings

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

Consider using Next.js Analytics to measure your app's real-world performance. Learn more.

Name	Type	Start Time	Duration
Next.js-before-hydration	Measure	0.00 ms	894.66 ms
Next.js-hydration	Measure	894.66 ms	60.88 ms
beforeRender	Mark	894.66 ms
routeChange	Mark	955.14 ms
afterHydrate	Mark	955.54 ms
beforeRender	Mark	981.98 ms
afterRender	Mark	1,176.47 ms

Keep request counts low and transfer sizes small 151 requests • 1,694 KiB

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

Resource Type	Requests	Transfer Size
Total	151.0	1,694.5 KiB
Script	43.0	655.6 KiB
Other	68.0	475.8 KiB
Image	23.0	417.8 KiB
Document	13.0	135.5 KiB
Stylesheet	4.0	9.7 KiB
Media	0.0	0.0 KiB
Font	0.0	0.0 KiB
Third-party	79.0	943.0 KiB

Largest Contentful Paint element 640 ms

This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP

Element
This is the background image <img data-testid="background-image" alt="This is the background image" loading="eager" decoding="async" data-nimg="fill" style="position: absolute; height: 100%; width: 100%; inset: 0px;" sizes="100vw" srcset="/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fbackground-image.7b4fa07f.jpe…" src="https://xabierlameiro.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fback…">

Element

This is the background image

Phase	% of LCP	Timing
TTFB	27%	170 ms
Load Delay	0%	0 ms
Load Time	0%	0 ms
Render Delay	73%	470 ms

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page. Learn how to improve CLSCLS

Element	CLS Contribution
MAKINOTE$ yarn start yarn run v1.22.19 $ next start Error: listen EADDRINUSE… <div class="ch-codeblock not-prose " style="max-width: max-content; margin: 20px 0px;">	0.050
MAKINOTE$ lsof -i :3000 COMMAND PID USER FD TYPE … <div class="ch-codeblock not-prose " style="max-width: max-content; margin: 20px 0px;">	0.015
Find the process that is using the port <h2>	0.012
When you try to start a server on a port that is already being used by another … <p>	0.008
Kill the process <h2>	0.007

Avoid long main-thread tasks 1 long task found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT

URL	Start Time	Duration
xabierlameiro.com 1st party		143 ms
…error/solve-address-in-use-error (xabierlameiro.com)	296 ms	143 ms

More information about the performance of your application. These numbers don't directly affect the Performance score.

Show Hide

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 how to eliminate render-blocking resources.FCPLCP

Use the next/script component to defer loading of non-critical third-party scripts. Learn more.

Properly size images Potential savings of 146 KiB

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

Use the next/image component to set the appropriate sizes. Learn more.

	URL	Resource Size	Potential Savings
xabierlameiro.com 1st party		222.4 KiB	145.9 KiB
This is the background image <img data-testid="background-image" alt="This is the background image" loading="eager" decoding="async" data-nimg="fill" style="position: absolute; height: 100%; width: 100%; inset: 0px;" sizes="100vw" srcset="/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fbackground-image.7b4fa07f.jpe…" src="https://xabierlameiro.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fback…">	/_next/image?url=… (xabierlameiro.com)	222.4 KiB	145.9 KiB

Defer offscreen images

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

Use the next/image component instead of <img> to automatically lazy-load images. Learn more.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.FCPLCP

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.FCPLCP

Reduce unused CSS

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

Consider setting up PurgeCSS in Next.js configuration to remove unused rules from stylesheets. Learn more.

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

Use the next/image component instead of <img> to adjust image quality. Learn more.

Serve images in next-gen formats

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

Use the next/image component instead of <img> to automatically optimize image format. Learn more.

Enable text compression

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

Enable compression on your Next.js server. Learn more.

Preconnect to required origins

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

Initial server response time was short Root document took 10 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.FCPLCP

URL	Time Spent
xabierlameiro.com 1st party	10 ms
…error/solve-address-in-use-error (xabierlameiro.com)	10 ms

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.FCPLCP

Preload key requests

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

Use HTTP/2

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

Use video formats for animated content Potential savings of 192 KiB

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 about efficient video formatsLCP

URL	Resource Size	Potential Savings
Google/Doubleclick Ads ad	362.9 KiB	192.3 KiB
/simgad/1743339… (s0.2mdn.net)	181.4 KiB	96.2 KiB
/simgad/1743339… (s0.2mdn.net)	181.4 KiB	96.2 KiB

Remove duplicate modules in JavaScript bundles

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

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 how to use modern JavaScriptTBT

Preload Largest Contentful Paint image

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP

Use the next/image component and set "priority" to true to preload LCP image. Learn more.

Avoids enormous network payloads Total size was 1,694 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.LCP

URL	Transfer Size
Google/Doubleclick Ads ad	651.7 KiB
/simgad/1743339… (s0.2mdn.net)	182.0 KiB
…prod/model_per….json (www.googletagservices.com)	153.6 KiB
…m202…/show_ads_impl_fy2021.js?bust=31087333 (pagead2.googlesyndication.com)	137.4 KiB
…current/ufs_web_display.js (pagead2.googlesyndication.com)	64.2 KiB
…current/reach_worklet.js (www.googleadservices.com)	63.2 KiB
…js/adsbygoogle.js (pagead2.googlesyndication.com)	51.3 KiB
xabierlameiro.com 1st party	325.9 KiB
/_next/image?url=… (xabierlameiro.com)	222.8 KiB
…pages/_app-53daae1d8c7850d1.js (xabierlameiro.com)	57.0 KiB
…chunks/framework-2c79e2a64abdb08b.js (xabierlameiro.com)	46.1 KiB
Google Tag Manager tag-manager	94.2 KiB
/gtag/js?id=G-05B334ER0M (www.googletagmanager.com)	94.2 KiB

Uses efficient cache policy on static assets 8 resources found

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

Configure caching for immutable assets and Server-side Rendered (SSR) pages. Learn more.

URL	Cache TTL	Transfer Size
Google/Doubleclick Ads ad		23 KiB
…r20110914/abg_lite_fy2021.js (pagead2.googlesyndication.com)	14d	9 KiB
…client/qs_click_protection_fy2021.js (tpc.googlesyndication.com)	14d	9 KiB
…html/omrhp_fy2021.js (pagead2.googlesyndication.com)	14d	3 KiB
…client/window_focus_fy2021.js (tpc.googlesyndication.com)	14d	1 KiB
…r20110914/abg_lite_fy2021.js (pagead2.googlesyndication.com)	14d	0 KiB
…html/omrhp_fy2021.js (pagead2.googlesyndication.com)	14d	0 KiB
…client/qs_click_protection_fy2021.js (tpc.googlesyndication.com)	14d	0 KiB
…client/window_focus_fy2021.js (tpc.googlesyndication.com)	14d	0 KiB

Avoids an excessive DOM size 614 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT

Statistic	Element	Value
Total DOM Elements		614
Maximum DOM Depth	MAKINOTE$ <span style="color: rgb(171, 178, 191);">	19
Maximum Child Elements	body <body>	27

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 how to avoid chaining critical requests.FCPLCP

Maximum critical path latency: 23.002 ms

Initial Navigation

…error/solve-address-in-use-error

(xabierlameiro.com)

- 23.002 ms, 23.61 KiB

JavaScript execution time 0.3 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT

URL	Total CPU Time	Script Evaluation	Script Parse
xabierlameiro.com 1st party	534 ms	194 ms	2 ms
…error/solve-address-in-use-error (xabierlameiro.com)	325 ms	2 ms	0 ms
…chunks/framework-2c79e2a64abdb08b.js (xabierlameiro.com)	209 ms	193 ms	2 ms
Unattributable	162 ms	11 ms	0 ms
Unattributable	162 ms	11 ms	0 ms
Google/Doubleclick Ads ad	96 ms	78 ms	7 ms
…m202…/show_ads_impl_fy2021.js?bust=31087333 (pagead2.googlesyndication.com)	96 ms	78 ms	7 ms

Minimizes main-thread work 1.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT

Category	Time Spent
Script Evaluation	418 ms
Other	356 ms
Style & Layout	105 ms
Rendering	32 ms
Script Parsing & Compilation	24 ms
Garbage Collection	15 ms
Parse HTML & CSS	8 ms

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 about font-display.FCPLCP

Minimize third-party usage Third-party code blocked the main thread for 0 ms

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 how to minimize third-party impact.TBT

Third-Party	Transfer Size	Main-Thread Blocking Time
Google/Doubleclick Ads ad	841 KiB	0 ms
/simgad/1743339… (s0.2mdn.net)	182 KiB	0 ms
…prod/model_per….json (www.googletagservices.com)	154 KiB	0 ms
…m202…/show_ads_impl_fy2021.js?bust=31087333 (pagead2.googlesyndication.com)	137 KiB	0 ms
…current/ufs_web_display.js (pagead2.googlesyndication.com)	64 KiB	0 ms
…current/reach_worklet.js (www.googleadservices.com)	63 KiB	0 ms
Other resources	241 KiB	0 ms
Google Tag Manager tag-manager	94 KiB	0 ms
/gtag/js?id=G-05B334ER0M (www.googletagmanager.com)	94 KiB	0 ms
Index Exchange ad	5 KiB	0 ms
AppNexus ad	1 KiB	0 ms
Other Google APIs/SDKs utility	1 KiB	0 ms
Google Analytics analytics	0 KiB	0 ms

Lazy load third-party resources with facades

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT

Largest Contentful Paint image was not lazily loaded

Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP

Element
This is the background image <img data-testid="background-image" alt="This is the background image" loading="eager" decoding="async" data-nimg="fill" style="position: absolute; height: 100%; width: 100%; inset: 0px;" sizes="100vw" srcset="/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fbackground-image.7b4fa07f.jpe…" src="https://xabierlameiro.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fback…">

Element

This is the background image

Uses 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 about adopting passive event listeners.

Avoids document.write()

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

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS

Image elements have explicit width and height

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

Use the next/image component to make sure images are always sized appropriately. Learn more.

Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.TBT

Page didn't prevent back/forward cache restoration

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache