https://xabierlameiro.com/blog/storybook/deploying-my-storybook-is-very-simple
95
Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
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.7 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
80 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.111
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Opportunities
Opportunity
Estimated Savings
Properly size images
0.17s
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Next.jsUse 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
These suggestions can help your page load faster. They don't directly affect the Performance score.
Diagnostics
Page prevented back/forward cache restoration 2 failure reasons
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
Failure reason
Failure type
The page has an unload handler in a sub frame.
Actionable
about:blank
…1041036…/160x600_plt_temp.html?e=…
(s0.2mdn.net)
Serve static assets with an efficient cache policy 7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Next.jsConfigure caching for immutable assets and Server-side Rendered (SSR) pages. Learn more.
URL
Cache TTL
Transfer Size
Google/Doubleclick Ads
ad
129 KiB
/879366/html_inpage_rendering_lib_200_280.js
(s0.2mdn.net)
1d
61 KiB
/879366/Enabler_01_250.js
(s0.2mdn.net)
1d
41 KiB
…r20110914/abg_lite.js
(pagead2.googlesyndication.com)
14d
12 KiB
…client/qs_click_protection_fy2021.js
(tpc.googlesyndication.com)
14d
9 KiB
…html/omrhp.js
(pagead2.googlesyndication.com)
14d
4 KiB
…client/window_focus_fy2021.js
(tpc.googlesyndication.com)
14d
1 KiB
Cloudinary
content
41 KiB
…602756/13
(res.cloudinary.com)
7d
41 KiB
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.
Next.jsConsider 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
455.77 ms
Next.js-hydration
Measure
455.77 ms
92.92 ms
beforeRender
Mark
455.77 ms
routeChange
Mark
548.27 ms
afterHydrate
Mark
548.69 ms
beforeRender
Mark
586.77 ms
afterRender
Mark
989.81 ms
Keep request counts low and transfer sizes small 153 requests • 1,832 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
153.0
1,832.4 KiB
Script
48.0
998.4 KiB
Other
59.0
452.6 KiB
Image
27.0
292.8 KiB
Document
12.0
62.6 KiB
Font
1.0
14.6 KiB
Stylesheet
6.0
11.3 KiB
Media
0.0
0.0 KiB
Third-party
83.0
1,110.6 KiB
Largest Contentful Paint element 660 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…">
Phase
% of LCP
Timing
TTFB
28%
180 ms
Load Delay
11%
70 ms
Load Time
4%
30 ms
Render Delay
57%
370 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
Once you've created your components in Storybook, you are able to share them in…
<p>
0.023
Once you've configured your Storybook, you can start writing stories for your c…
<p>
0.023
Deploying React components with Storybook is a great way to showcase your work …
<p>
0.023
Storybook is easy to set up and manage. You will need Node.js and a few develop…
<p>
0.019
1. Storybook commands
<h2>
0.017
Avoid long main-thread tasks 2 long tasks 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
189 ms
…storybook/deploying-my-storybook-is-very-simple
(xabierlameiro.com)
317 ms
126 ms
…chunks/framework-2c79e2a64abdb08b.js
(xabierlameiro.com)
1,133 ms
63 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (32)
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
Next.jsUse the next/script component to defer loading of non-critical third-party scripts. Learn more.
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.
Next.jsUse 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
Next.jsConsider setting up PurgeCSS in Next.js configuration to remove unused rules from stylesheets. Learn more.
Reduce unused JavaScript Potential savings of 154 KiB
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
Next.jsUse Webpack Bundle Analyzer to detect unused JavaScript code. Learn more
URL
Transfer Size
Potential Savings
Google/Doubleclick Ads
ad
190.7 KiB
118.9 KiB
…m202…/show_ads_impl_fy2021.js
(pagead2.googlesyndication.com)
139.5 KiB
96.9 KiB
…js/adsbygoogle.js
(pagead2.googlesyndication.com)
51.2 KiB
22.0 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
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Next.jsUse 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.
Next.jsUse 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
Next.jsEnable 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 170 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
170 ms
…storybook/deploying-my-storybook-is-very-simple
(xabierlameiro.com)
170 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
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
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
Next.jsUse the next/image component and set "priority" to true to preload LCP image. Learn more.
Avoids enormous network payloads Total size was 1,832 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
532.6 KiB
…prod/model_per….json
(www.googletagservices.com)
153.6 KiB
…m202…/show_ads_impl_fy2021.js
(pagead2.googlesyndication.com)
139.5 KiB
…current/ufs_web_display.js
(pagead2.googlesyndication.com)
64.2 KiB
…current/reach_worklet.js
(www.googleadservices.com)
63.2 KiB
/879366/html_inpage_rendering_lib_200_280.js
(s0.2mdn.net)
61.0 KiB
…js/adsbygoogle.js
(pagead2.googlesyndication.com)
51.2 KiB
xabierlameiro.com
1st party
279.7 KiB
/_next/image?url=…
(xabierlameiro.com)
222.8 KiB
…pages/_app-53daae1d8c7850d1.js
(xabierlameiro.com)
57.0 KiB
Google Tag Manager
tag-manager
94.2 KiB
/gtag/js?id=G-05B334ER0M
(www.googletagmanager.com)
94.2 KiB
Integral Ad Science
ad
86.4 KiB
…creative/adj?p=APEucNV6W…&d=CrkBAKAmf…
(fw.adsafeprotected.com)
86.4 KiB
Avoids an excessive DOM size 769 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
769
Maximum DOM Depth
"scripts"
<span style="color: rgb(152, 195, 121);">
21
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: 181.259 ms
Initial Navigation
…storybook/deploying-my-storybook-is-very-simple
(xabierlameiro.com)
- 181.259 ms, 24.29 KiB
JavaScript execution time 0.4 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
622 ms
289 ms
2 ms
…chunks/framework-2c79e2a64abdb08b.js
(xabierlameiro.com)
322 ms
288 ms
2 ms
…storybook/deploying-my-storybook-is-very-simple
(xabierlameiro.com)
300 ms
1 ms
0 ms
Unattributable
160 ms
13 ms
0 ms
Unattributable
160 ms
13 ms
0 ms
Google/Doubleclick Ads
ad
103 ms
71 ms
7 ms
…m202…/show_ads_impl_fy2021.js
(pagead2.googlesyndication.com)
103 ms
71 ms
7 ms
Google Tag Manager
tag-manager
58 ms
52 ms
5 ms
/gtag/js?id=G-05B334ER0M
(www.googletagmanager.com)
58 ms
52 ms
5 ms
Minimizes main-thread work 1.1 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
526 ms
Other
356 ms
Style & Layout
103 ms
Rendering
40 ms
Script Parsing & Compilation
29 ms
Garbage Collection
14 ms
Parse HTML & CSS
9 ms
All text remains visible during webfont loads
Warnings: Lighthouse was unable to automatically check the `font-display` value for the origin https://fonts.gstatic.com.
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
816 KiB
0 ms
…prod/model_per….json
(www.googletagservices.com)
154 KiB
0 ms
…m202…/show_ads_impl_fy2021.js
(pagead2.googlesyndication.com)
140 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
/879366/html_inpage_rendering_lib_200_280.js
(s0.2mdn.net)
61 KiB
0 ms
Other resources
334 KiB
0 ms
Integral Ad Science
ad
114 KiB
0 ms
…creative/adj?p=APEucNV6W…&d=CrkBAKAmf…
(fw.adsafeprotected.com)
86 KiB
0 ms
/sca.17.6.4.js
(static.adsafeprotected.com)
23 KiB
0 ms
Google Tag Manager
tag-manager
94 KiB
0 ms
/gtag/js?id=G-05B334ER0M
(www.googletagmanager.com)
94 KiB
0 ms
Cloudinary
content
41 KiB
0 ms
…602756/13
(res.cloudinary.com)
41 KiB
0 ms
Cloudflare CDN
cdn
25 KiB
0 ms
…plugins/CSSPlugin.min.js
(cdnjs.cloudflare.com)
14 KiB
0 ms
…latest/TweenLite.min.js
(cdnjs.cloudflare.com)
9 KiB
0 ms
Google Fonts
cdn
16 KiB
0 ms
…v26/JTUHjIg1_….woff2
(fonts.gstatic.com)
15 KiB
0 ms
Index Exchange
ad
3 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…">
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
Next.jsUse 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