ABCDEFGHIJKLMNOPQRSTUVWXY
1
appidnum_pagestotaltotal_applicablepctmedian_weightaudit_groupdescription
2
Wagtail
total-blocking-time
886478844170.200588634830metricsSum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more](https://web.dev/lighthouse-total-blocking-time/).20230301 data
3
Wagtail
cumulative-layout-shift
3829478846010.83221038925metricsCumulative Layout Shift measures the movement of visible elements within the viewport. [Learn more](https://web.dev/cls/).SUM of pctappSUM of pct
4
Wagtail
largest-contentful-paint
784478845940.170657379225metricsLargest Contentful Paint marks the time at which the largest text or image is painted. [Learn more](https://web.dev/lighthouse-largest-contentful-paint/)idAllDjangoFlaskNext.jsWagtailidDjangoFlaskNext.jsWagtail
5
Wagtail
first-contentful-paint
1304478846010.283416648610metricsFirst Contentful Paint marks the time at which the first text or image is painted. [Learn more](https://web.dev/first-contentful-paint/).0
6
Wagtailspeed-index1678478846000.364782608710metricsSpeed Index shows how quickly the contents of a page are visibly populated. [Learn more](https://web.dev/speed-index/).bf-cache0.52832537820.61963589080.56187624750.43224850330.6614139693bf-cache9.1%3.4%-9.6%13.3%
7
Wagtailbf-cache3106478646960.66141396930Many 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](https://developer.chrome.com/docs/lighthouse/performance/bf-cache/)bootup-time0.50567303180.60735226490.77139979860.28287390680.5659926071bootup-time10.2%26.6%-22.3%6.0%
8
Wagtailbootup-time2603478845990.56599260710Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn more](https://web.dev/bootup-time/).
critical-request-chains
00000
critical-request-chains
0.0%0.0%0.0%0.0%
9
Wagtail
critical-request-chains
0478800The 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 more](https://web.dev/critical-request-chains/).
cumulative-layout-shift
0.80127902580.78107766540.86826347310.86568176960.832210389
cumulative-layout-shift
-2.0%6.7%6.4%3.1%
10
Wagtaildiagnostics0478800hiddenCollection of useful page vitals.diagnostics00000diagnostics0.0%0.0%0.0%0.0%
11
Wagtaildom-size4135478847100.87791932060A 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). [Learn more](https://web.dev/dom-size/).dom-size0.86490539440.8685325350.94710578840.87261850380.8779193206dom-size0.4%8.2%0.8%1.3%
12
Wagtail
duplicated-javascript
4594478846000.99869565220Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
duplicated-javascript
0.9984945450.99859256070.9990019960.99904111410.9986956522
duplicated-javascript
0.0%0.1%0.1%0.0%
13
Wagtail
efficient-animated-content
4508478846010.97978700280Large 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](https://web.dev/efficient-animated-content/)
efficient-animated-content
0.97960695230.98359949450.99101796410.98574252460.9797870028
efficient-animated-content
0.4%1.1%0.6%0.0%
14
Wagtail
first-meaningful-paint
2168478846010.47120191260hiddenFirst Meaningful Paint measures when the primary content of a page is visible. [Learn more](https://web.dev/first-meaningful-paint/).
first-contentful-paint
0.35340044590.26980525080.086826347310.52166724490.2834166486
first-contentful-paint
-8.4%-26.7%16.8%-7.0%
15
Wagtailfont-display1828478846890.38984858180Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. [Learn more](https://web.dev/font-display/).
first-meaningful-paint
0.46026111050.42103297710.17764471060.59587534510.4712019126
first-meaningful-paint
-3.9%-28.3%13.6%1.1%
16
Wagtailinteractive927478844170.20987095310metricsTime to interactive is the amount of time it takes for the page to become fully interactive. [Learn more](https://web.dev/interactive/).font-display0.37174308210.31905314720.370.70271128840.3898485818font-display-5.3%-0.2%33.1%1.8%
17
Wagtail
largest-contentful-paint-element
0478800This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/)interactive0.24454467810.24375276590.20507614210.14341238060.2098709531interactive-0.1%-3.9%-10.1%-3.5%
18
Wagtail
layout-shift-elements
0478800These DOM elements contribute most to the CLS of the page. [Learn how to improve CLS](https://web.dev/optimize-cls/)
largest-contentful-paint
0.22816417170.21910322410.09990009990.2735286070.1706573792
largest-contentful-paint
-0.9%-12.8%4.5%-5.8%
19
Wagtaillcp-lazy-loaded3130478832510.96278068290Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. [Learn more](https://web.dev/lcp-lazy-loading/).
largest-contentful-paint-element
00000
largest-contentful-paint-element
0.0%0.0%0.0%0.0%
20
Wagtaillegacy-javascript4222478845910.9196253540Polyfills 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 JavaScript](https://web.dev/publish-modern-javascript/)
layout-shift-elements
00000
layout-shift-elements
0.0%0.0%0.0%0.0%
21
Wagtaillong-tasks0478800Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. [Learn more](https://web.dev/long-tasks-devtools/)lcp-lazy-loaded0.92492791380.97897422360.91828793770.89467359460.9627806829lcp-lazy-loaded5.4%-0.7%-3.0%3.8%
22
Wagtail
main-thread-tasks
0478800hiddenLists the toplevel main thread tasks that executed during page load.legacy-javascript0.93653792150.93057513590.7580.93928196640.919625354legacy-javascript-0.6%-17.9%0.3%-1.7%
23
Wagtail
mainthread-work-breakdown
798478845990.17351598170Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn more](https://web.dev/mainthread-work-breakdown/)long-tasks00000long-tasks0.0%0.0%0.0%0.0%
24
Wagtailmax-potential-fid537478846010.11671375790hiddenThe maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more](https://web.dev/lighthouse-max-potential-fid/).
main-thread-tasks
00000
main-thread-tasks
0.0%0.0%0.0%0.0%
25
Wagtailmetrics0478800hiddenCollects all available metrics.
mainthread-work-breakdown
0.17674361540.23016785470.29909365560.078002878330.1735159817
mainthread-work-breakdown
5.3%12.2%-9.9%-0.3%
26
Wagtail
modern-image-formats
1411478846000.30673913040Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more](https://web.dev/uses-webp-images/).max-potential-fid0.13977425180.16286551390.21457085830.037665798160.1167137579max-potential-fid2.3%7.5%-10.2%-2.3%
27
Wagtail
network-requests
0478800hiddenLists the network requests that were made during page load.metrics00000metrics0.0%0.0%0.0%0.0%
28
Wagtailnetwork-rtt0478800hiddenNetwork 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. [Learn more](https://hpbn.co/primer-on-latency-and-bandwidth/).
modern-image-formats
0.41614059980.36344296230.34465534470.61611314840.3067391304
modern-image-formats
-5.3%-7.1%20.0%-10.9%
29
Wagtail
network-server-latency
0478800hiddenServer 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. [Learn more](https://hpbn.co/primer-on-web-performance/#analyzing-the-resource-waterfall).
network-requests
00000
network-requests
0.0%0.0%0.0%0.0%
30
Wagtail
no-document-write
4387478847090.93162030160For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. [Learn more](https://web.dev/no-document-write/).network-rtt00000network-rtt0.0%0.0%0.0%0.0%
31
Wagtail
no-unload-listeners
22210The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. [Learn more](https://web.dev/bfcache/#never-use-the-unload-event)
network-server-latency
00000
network-server-latency
0.0%0.0%0.0%0.0%
32
Wagtail
non-composited-animations
0478800Animations which are not composited can be janky and increase CLS. [Learn more](https://web.dev/non-composited-animations)
no-document-write
0.84419966040.91165588730.97504990020.94626175110.9316203016
no-document-write
6.7%13.1%10.2%8.7%
33
Wagtail
offscreen-images
2383478846010.51793088460Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn more](https://web.dev/offscreen-images/).
no-unload-listeners
0.84049360150.81818181820.85714285711
no-unload-listeners
-2.2%-84.0%1.7%16.0%
34
Wagtail
performance-budget
0478800budgetsKeep the quantity and size of network requests under the targets set by the provided performance budget. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/budgets).
non-composited-animations
00000
non-composited-animations
0.0%0.0%0.0%0.0%
35
Wagtail
preload-lcp-image
22210Preload the image used by the LCP element in order to improve your LCP time. [Learn more](https://web.dev/optimize-lcp/#preload-important-resources).
offscreen-images
0.63305980570.55595771570.64935064940.75332349690.5179308846
offscreen-images
-7.7%1.6%12.0%-11.5%
36
Wagtail
prioritize-lcp-image
3564478635840.99441964290If 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](https://web.dev/optimize-lcp/#optimize-when-the-resource-is-discovered).
performance-budget
00000
performance-budget
0.0%0.0%0.0%0.0%
37
Wagtailredirects4410478846010.95848728540Redirects introduce additional delays before the page can be loaded. [Learn more](https://web.dev/redirects/).
preload-lcp-image
0.994996873111
preload-lcp-image
0.5%-99.5%0.5%0.5%
38
Wagtail
render-blocking-resources
2005478845770.43805986450Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources/).
prioritize-lcp-image
0.99790680520.99847195840.99872448980.99282496250.9944196429
prioritize-lcp-image
0.1%0.1%-0.5%-0.3%
39
Wagtail
resource-summary
0478800To set budgets for the quantity and size of page resources, add a budget.json file. [Learn more](https://web.dev/use-lighthouse-for-performance-budgets/).redirects0.96949886520.92637596230.8792415170.94094113310.9584872854redirects-4.3%-9.0%-2.9%-1.1%
40
Wagtail
script-treemap-data
0478800hiddenUsed for treemap app
render-blocking-resources
0.42156622050.39592577650.1870.88724508710.4380598645
render-blocking-resources
-2.6%-23.5%46.6%1.6%
41
Wagtail
server-response-time
2560478847100.54352441610Keep the server response time for the main document short because all other requests depend on it. [Learn more](https://web.dev/time-to-first-byte/).
resource-summary
00000
resource-summary
0.0%0.0%0.0%0.0%
42
Wagtail
third-party-facades
0478856700Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. [Learn more](https://web.dev/third-party-facades/).
script-treemap-data
00000
script-treemap-data
0.0%0.0%0.0%0.0%
43
Wagtail
third-party-summary
1217478844560.27311490130Third-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 more](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/).
server-response-time
0.63186942970.62765476730.80039920160.73460396510.5435244161
server-response-time
-0.4%16.9%10.3%-8.8%
44
Wagtailtiming-budget0478800budgetsSet a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/budgets).speed-index0.38359513890.3813247470.25948103790.37434798670.3647826087speed-index-0.2%-12.4%-0.9%-1.9%
45
Wagtailtotal-byte-weight3371478847100.71571125270Large network payloads cost users real money and are highly correlated with long load times. [Learn more](https://web.dev/total-byte-weight/).
third-party-facades
00000
third-party-facades
0.0%0.0%0.0%0.0%
46
Wagtailunminified-css4131478845800.90196506550Minifying CSS files can reduce network payload sizes. [Learn more](https://web.dev/unminified-css/).
third-party-summary
0.32017632750.27713893550.62397179790.25575129220.2731149013
third-party-summary
-4.3%30.4%-6.4%-4.7%
47
Wagtail
unminified-javascript
4005478846010.87046294280Minifying JavaScript files can reduce payload sizes and script parse time. [Learn more](https://web.dev/unminified-javascript/).timing-budget00000timing-budget0.0%0.0%0.0%0.0%
48
Wagtailunsized-images962478846340.20759602930Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn more](https://web.dev/optimize-cls/#images-without-dimensions)
total-blocking-time
0.20835619750.23681958990.37969543150.077433698090.2005886348
total-blocking-time
2.8%17.1%-13.1%-0.8%
49
Wagtail
unused-css-rules
2309478845800.50414847160Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn more](https://web.dev/unused-css-rules/).total-byte-weight0.75236865460.76835743330.70059880240.797312430.7157112527total-byte-weight1.6%-5.2%4.5%-3.7%
50
Wagtail
unused-javascript
1004478846000.21826086960Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn more](https://web.dev/unused-javascript/).unminified-css0.89688324580.88213442380.6830.98200470410.9019650655unminified-css-1.5%-21.4%8.5%0.5%
51
Wagtailuser-timings0478800Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. [Learn more](https://web.dev/user-timings/).
unminified-javascript
0.83846038740.83447265630.96906187620.97018690350.8704629428
unminified-javascript
-0.4%13.1%13.2%3.2%
52
Wagtailuses-http22877478846010.62529884810HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. [Learn more](https://web.dev/uses-http2/).unsized-images0.27278527580.1335268080.032359081420.41814071430.2075960293unsized-images-13.9%-24.0%14.5%-6.5%
53
Wagtail
uses-long-cache-ttl
1021478847100.21677282380A long cache lifetime can speed up repeat visits to your page. [Learn more](https://web.dev/uses-long-cache-ttl/).
unused-css-rules
0.52261757450.47681852210.3290.79383441070.5041484716
unused-css-rules
-4.6%-19.4%27.1%-1.8%
54
Wagtail
uses-optimized-images
3743478846000.81369565220Optimized images load faster and consume less cellular data. [Learn more](https://web.dev/uses-optimized-images/).
unused-javascript
0.32853004540.24644549760.28443113770.2700739080.2182608696
unused-javascript
-8.2%-4.4%-5.8%-11.0%
55
Wagtail
uses-passive-event-listeners
2944478847090.62518581440Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. [Learn more](https://web.dev/uses-passive-event-listeners/).user-timings00000user-timings0.0%0.0%0.0%0.0%
56
Wagtail
uses-rel-preconnect
4091478845940.890509360Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. [Learn more](https://web.dev/uses-rel-preconnect/).uses-http20.72305013020.62362132350.44810379240.86115741490.6252988481uses-http2-9.9%-27.5%13.8%-9.8%
57
Wagtailuses-rel-preload0478800Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. [Learn more](https://web.dev/uses-rel-preload/).
uses-long-cache-ttl
0.31192088370.2465544510.53892215570.41814993810.2167728238
uses-long-cache-ttl
-6.5%22.7%10.6%-9.5%
58
Wagtail
uses-responsive-images
2427478846010.5274940230Serve images that are appropriately-sized to save cellular data and improve load time. [Learn more](https://web.dev/uses-responsive-images/).
uses-optimized-images
0.68211189920.735999310.75924075920.86467143790.8136956522
uses-optimized-images
5.4%7.7%18.3%13.2%
59
Wagtail
uses-text-compression
2995478846010.65094544660Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more](https://web.dev/uses-text-compression/).
uses-passive-event-listeners
0.54617542550.59123902050.77844311380.81133409950.6251858144
uses-passive-event-listeners
4.5%23.2%26.5%7.9%
60
Wagtailviewport4672478847100.99193205940A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents [a 300 millisecond delay to user input](https://developers.google.com/web/updates/2013/12/300ms-tap-delay-gone-away). [Learn more](https://web.dev/viewport/).
uses-rel-preconnect
0.92251220530.91981362710.92207792210.9179367720.89050936
uses-rel-preconnect
-0.3%0.0%-0.5%-3.2%
61
Next.js
total-blocking-time
392885504165073760.0774336980930metricsSum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more](https://web.dev/lighthouse-total-blocking-time/).uses-rel-preload00000uses-rel-preload0.0%0.0%0.0%0.0%
62
Next.js
cumulative-layout-shift
4694805504165423240.865681769625metricsCumulative Layout Shift measures the movement of visible elements within the viewport. [Learn more](https://web.dev/cls/).
uses-responsive-images
0.58184565140.55940480290.52447552450.62514939140.527494023
uses-responsive-images
-2.2%-5.7%4.3%-5.4%
63
Next.js
largest-contentful-paint
1479565504165409160.27352860725metricsLargest Contentful Paint marks the time at which the largest text or image is painted. [Learn more](https://web.dev/lighthouse-largest-contentful-paint/)
uses-text-compression
0.82715922410.67621208640.55089820360.87995840030.6509454466
uses-text-compression
-15.1%-27.6%5.3%-17.6%
64
Next.js
first-contentful-paint
2827045504165419240.521667244910metricsFirst Contentful Paint marks the time at which the first text or image is painted. [Learn more](https://web.dev/first-contentful-paint/).viewport0.92569219510.96060212380.97005988020.99869598850.9919320594viewport3.5%4.4%7.3%6.6%
65
Next.jsspeed-index2026725504165414000.374347986710metricsSpeed Index shows how quickly the contents of a page are visibly populated. [Learn more](https://web.dev/speed-index/).
66
Next.jsbf-cache2345005503325425120.43224850330Many 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](https://developer.chrome.com/docs/lighthouse/performance/bf-cache/)
67
Next.jsbootup-time1533125504165419800.28287390680Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn more](https://web.dev/bootup-time/).
68
Next.js
critical-request-chains
055041600The 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 more](https://web.dev/critical-request-chains/).
69
Next.jsdiagnostics055041600hiddenCollection of useful page vitals.
70
Next.jsdom-size4737765504165429360.87261850380A 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). [Learn more](https://web.dev/dom-size/).
71
Next.js
duplicated-javascript
5417765504165422960.99904111410Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
72
Next.js
efficient-animated-content
5345805504165423120.98574252460Large 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](https://web.dev/efficient-animated-content/)
73
Next.js
first-meaningful-paint
3229125504165419120.59587534510hiddenFirst Meaningful Paint measures when the primary content of a page is visible. [Learn more](https://web.dev/first-meaningful-paint/).
74
Next.jsfont-display3804765504165414400.70271128840Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. [Learn more](https://web.dev/font-display/).
75
Next.jsinteractive727645504165073760.14341238060metricsTime to interactive is the amount of time it takes for the page to become fully interactive. [Learn more](https://web.dev/interactive/).
76
Next.js
largest-contentful-paint-element
055041600This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/)
77
Next.js
layout-shift-elements
055041600These DOM elements contribute most to the CLS of the page. [Learn how to improve CLS](https://web.dev/optimize-cls/)
78
Next.jslcp-lazy-loaded3126925504163495040.89467359460Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. [Learn more](https://web.dev/lcp-lazy-loading/).
79
Next.jslegacy-javascript5083925504165412560.93928196640Polyfills 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 JavaScript](https://web.dev/publish-modern-javascript/)
80
Next.jslong-tasks055041600Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. [Learn more](https://web.dev/long-tasks-devtools/)
81
Next.js
main-thread-tasks
055041600hiddenLists the toplevel main thread tasks that executed during page load.
82
Next.js
mainthread-work-breakdown
422765504165419800.078002878330Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn more](https://web.dev/mainthread-work-breakdown/)
83
Next.jsmax-potential-fid204125504165419240.037665798160hiddenThe maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more](https://web.dev/lighthouse-max-potential-fid/).
84
Next.jsmetrics055041600hiddenCollects all available metrics.
85
Next.js
modern-image-formats
3333325504165410240.61611314840Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more](https://web.dev/uses-webp-images/).
86
Next.js
network-requests
055041600hiddenLists the network requests that were made during page load.
87
Next.jsnetwork-rtt055041600hiddenNetwork 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. [Learn more](https://hpbn.co/primer-on-latency-and-bandwidth/).
88
Next.js
network-server-latency
055041600hiddenServer 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. [Learn more](https://hpbn.co/primer-on-web-performance/#analyzing-the-resource-waterfall).
89
Next.js
no-document-write
5137525504165429280.94626175110For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. [Learn more](https://web.dev/no-document-write/).
90
Next.js
no-unload-listeners
7284840.85714285710The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. [Learn more](https://web.dev/bfcache/#never-use-the-unload-event)
91
Next.js
non-composited-animations
055041600Animations which are not composited can be janky and increase CLS. [Learn more](https://web.dev/non-composited-animations)
92
Next.js
offscreen-images
4084525504165422000.75332349690Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn more](https://web.dev/offscreen-images/).
93
Next.js
performance-budget
055041600budgetsKeep the quantity and size of network requests under the targets set by the provided performance budget. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/budgets).
94
Next.js
preload-lcp-image
72847210Preload the image used by the LCP element in order to improve your LCP time. [Learn more](https://web.dev/optimize-lcp/#preload-important-resources).
95
Next.js
prioritize-lcp-image
3808005503323835520.99282496250If 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](https://web.dev/optimize-lcp/#optimize-when-the-resource-is-discovered).
96
Next.jsredirects5098965504165419000.94094113310Redirects introduce additional delays before the page can be loaded. [Learn more](https://web.dev/redirects/).
97
Next.js
render-blocking-resources
4785805504165394000.88724508710Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources/).
98
Next.js
resource-summary
055041600To set budgets for the quantity and size of page resources, add a budget.json file. [Learn more](https://web.dev/use-lighthouse-for-performance-budgets/).
99
Next.js
script-treemap-data
055041600hiddenUsed for treemap app
100
Next.js
server-response-time
3988405504165429320.73460396510Keep the server response time for the main document short because all other requests depend on it. [Learn more](https://web.dev/time-to-first-byte/).