lighthouse 12.2.3-dev.20241210 → 12.2.3

package/shared/localization/locales/ja.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Lighthouse ユーザーフロー レポート"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "レイアウト シフトは、ユーザーの操作なしで要素が移動する場合に発生します。[レイアウト シフトの原因を調査](https://web.dev/articles/optimize-cls)してください。たとえば、ページの読み込み時に要素が追加、削除される、フォントが変更されるなどの原因が考えられます。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "レイアウト シフトの原因"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "最初のネットワーク リクエストは最も重要です。リダイレクトを回避し、サーバー応答を高速に保ち、テキスト圧縮を有効にして、レイテンシを削減します。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "ドキュメント リクエストのレイテンシ"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "テキストの表示を統一するため、[font-display](https://developer.chrome.com/blog/font-display) を swap または optional に設定することを検討してください。swap をさらに最適化して、[フォント指標のオーバーライド](https://developer.chrome.com/blog/font-fallbacks)でレイアウト シフトを軽減できます。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "フォント表示"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "最も長いフェーズから調査を開始します。[遅延を最小限に抑えることができます](https://web.dev/articles/optimize-inp#optimize_interactions)。処理期間を削減するには、[メインスレッドのコスト（通常は JS）を最適化](https://web.dev/articles/optimize-long-tasks)します。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "フェーズ別の INP"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "LCP 画像を HTML からすぐに[検出できる](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay)ようにし、[遅延読み込みを回避](https://web.dev/articles/lcp-lazy-loading)して、LCP を最適化します"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "LCP リクエストの検出"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "各[フェーズには、それに適した改善戦略があります](https://web.dev/articles/optimize-lcp#lcp-breakdown)。理想的なのは、LCP 時間のほとんどがリソースの読み込みに使われ、遅延に費やされないことです。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "フェーズ別の LCP"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "リクエストがページの最初のレンダリングをブロックしているため、LCP が遅れる可能性があります。これらのネットワーク リクエストを[遅らせるかインライン化](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/)すると、クリティカル パスから移動できます。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "レンダリングをブロックしているリクエスト"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "スタイルの再計算のコストが引き続き高い場合は、セレクタの最適化によってコストを削減できます。経過時間が長く、遅いパスの割合（%）が高い[セレクタを最適化](https://developer.chrome.com/docs/devtools/performance/selector-stats)します。セレクタの複雑さや数、DOM のサイズや深さを抑えて、一致コストを削減します。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "CSS セレクタのコスト"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "サードパーティのコードによって、読み込み速度が著しく低下する可能性があります。ページのコンテンツを優先させるには、[サードパーティのコードの読み込みを減らして遅らせ](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/)ます。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "サードパーティ"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "ページのビューポートはモバイル向けに最適化されていないため、タップ操作が[最大 300 ミリ秒遅延](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)する可能性があります。"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "ビューポートがモバイル向けに最適化されていません"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "アニメーション コンテンツの場合は、[`amp-anim`](https://amp.dev/documentation/components/amp-anim/) を使用して、コンテンツが画面外にあるときの CPU 使用量を最小限に抑えることができます。"
   },

package/shared/localization/locales/ko.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Lighthouse 사용자 플로우 보고서"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "레이아웃 변경은 사용자 상호작용 없이 요소가 이동할 때 발생합니다. 페이지가 로드될 때 요소가 추가되거나 삭제되거나 글꼴이 변경되는 등 [레이아웃이 변경되는 이유를 조사](https://web.dev/articles/optimize-cls)하세요."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "레이아웃 변경 원인"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "첫 번째 네트워크 요청이 가장 중요합니다.  리디렉션을 방지하고 서버 응답 속도를 높이며 텍스트 압축을 사용 설정하여 지연 시간을 줄이세요."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "문서 요청 지연 시간"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "[font-display](https://developer.chrome.com/blog/font-display)를 swap 또는 optional로 설정하여 텍스트가 일관되게 표시되도록 하세요. swap은 [글꼴 측정항목 재정의](https://developer.chrome.com/blog/font-fallbacks)를 통해 레이아웃 변화를 완화하도록 추가로 최적화할 수 있습니다."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "글꼴 표시"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "가장 긴 단계부터 조사를 시작하세요. [지연을 최소화할 수 있습니다](https://web.dev/articles/optimize-inp#optimize_interactions). 처리 시간을 줄이려면 [주 스레드 비용(JS인 경우가 많음)을 최적화](https://web.dev/articles/optimize-long-tasks)하세요."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "단계별 INP"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "HTML에서 LCP 이미지를 즉시 [검색 가능](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay)하게 만들고 [지연 로드](https://web.dev/articles/lcp-lazy-loading)를 방지하여 LCP를 최적화합니다."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "LCP 요청 탐색"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "각 [단계에는 해당 단계에 맞는 개선 전략이 있습니다](https://web.dev/articles/optimize-lcp#lcp-breakdown). 이상적으로는 대부분의 LCP 시간이 지연이 아닌 리소스 로드에 소요되어야 합니다."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "단계별 LCP"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "요청으로 인해 페이지의 초기 렌더링이 차단되어 LCP가 지연될 수 있습니다. [지연 또는 인라인 처리](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/)하면 이러한 네트워크 요청이 주요 경로에서 벗어날 수 있습니다."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "렌더링 차단 요청"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "스타일 재계산 비용이 여전히 높다면 선택자 최적화를 통해 비용을 줄일 수 있습니다. 경과 시간이 길고 느린 경로 비율이 높은 경우 [선택자를 최적화](https://developer.chrome.com/docs/devtools/performance/selector-stats)하세요. 선택자가 간단하고 선택자 수가 적으며 DOM이 작고 DOM이 얕으면 일치 비용이 줄어듭니다."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "CSS 선택자 비용"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "서드 파티 코드는 로드 성능에 크게 영향을 미칠 수 있습니다. [서드 파티 코드의 로드를 줄이고 연기](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/)하여 페이지 콘텐츠에 우선순위를 지정하세요."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "서드 파티"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "페이지 표시 영역이 모바일에 최적화되어 있지 않아 탭 상호작용이 [최대 300밀리초 지연될 수 있습니다](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "표시 영역이 모바일에 최적화되지 않음"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "애니메이션 콘텐츠의 경우 [`amp-anim`](https://amp.dev/documentation/components/amp-anim/)을 사용하여 콘텐츠가 화면에 표시되지 않을 때 CPU 사용량을 최소화하세요."
   },

package/shared/localization/locales/lt.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "„Lighthouse“ naudotojų srauto ataskaita"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Išdėstymo poslinkiai įvyksta, kai elementai juda be naudotojo sąveikos. [Išnagrinėkite išdėstymo poslinkių priežastis](https://web.dev/articles/optimize-cls), pvz., elementų pridėjimą, pašalinimą arba šriftų keitimą, kai puslapis įkeliamas."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Išdėstymo poslinkio priežastys"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Pirmoji tinklo užklausa yra svarbiausia.  Sumažinkite delsą vengdami peradresavimų, užtikrindami spartų serverio atsaką ir įgalindami teksto glaudinimą."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Dokumento užklausos delsa"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Apsvarstykite galimybę nustatyti [font-display](https://developer.chrome.com/blog/font-display) kaip swap arba optional, kad tekstas būtų nuolat matomas. swap galima toliau optimizuoti, kad būtų sumažinti išdėstymo poslinkiai naudojant [šrifto metrikos nepaisymą](https://developer.chrome.com/blog/font-fallbacks)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Šrifto pateikimas"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Pradėkite tyrimą nuo ilgiausios fazės. [Galite sumažinti vėlavimą](https://web.dev/articles/optimize-inp#optimize_interactions). Kad apdorojimo trukmė būtų trumpesnė, [optimizuokite pagrindinės grupės mokesčius](https://web.dev/articles/optimize-long-tasks), dažnai JS."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "SKŽ pagal etapą"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Optimizuokite DTŽ, kad DTŽ vaizdas būtų [aptinkamas](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) iš karto iš HTML ir [išvengtumėte asinchroninio įkėlimo](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "DTŽ užklausos aptikimas"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Kiekvienai [fazei taikomos konkrečios tobulinimo strategijos](https://web.dev/articles/optimize-lcp#lcp-breakdown). Idealiu atveju didžiąją DTŽ laiko dalį turėtų sudaryti šaltinių įkėlimas, o ne vėlavimai."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "DTŽ pagal etapą"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Užklausos blokuoja pradinį puslapio pateikimą, dėl kurio DTŽ gali vėluoti. [Atidėliojant arba įterpiant](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) šias tinklo užklausas galima pašalinti iš kritinio kelio."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Pateikimo blokavimo užklausos"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "Jei stiliaus perskaičiavimo mokesčiai išlieka dideli, juos galima sumažinti optimizavus parinkiklius. [Optimizuokite parinkiklius](https://developer.chrome.com/docs/devtools/performance/selector-stats), kai praėjęs laikas ir lėto kelio proc. yra dideli. Paprastesni parinkikliai, mažiau parinkiklių, mažesnis DOM ir seklesnis DOM sumažins atitikimo mokesčius."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "CSS kalbos parinkiklio mokesčiai"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Trečiosios šalies kodas gali smarkiai paveikti įkėlimo našumą. [Sumažinkite ir atidėkite trečiosios šalies kodo įkėlimą](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/), kad būtų nustatytas puslapio turinio prioritetas."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Trečiosios šalys"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "Puslapio peržiūros sritis neoptimizuota mobiliesiems, todėl sąveikos su palietimais gali būti [atidėtos iki 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Peržiūros sritis neoptimizuota mobiliesiems"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "Jei teikiate animuotą turinį, naudokite [„`amp-anim`“](https://amp.dev/documentation/components/amp-anim/), kad būtų naudojama mažiau centrinio procesoriaus galios, kai turinys nerodomas ekrane."
   },

package/shared/localization/locales/lv.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Lighthouse lietotāju plūsmas pārskats"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Izkārtojuma nobīdes rodas, ja elementi pārvietojas bez lietotāja mijiedarbības. [Izpētiet izkārtojuma nobīdes cēloņus](https://web.dev/articles/optimize-cls), piemēram, elementu pievienošanu un noņemšanu vai to fonta izmaiņas lapas ielādes laikā."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Izkārtojuma nobīdes cēloņi"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Jūsu pirmais tīkla pieprasījums ir vissvarīgākais.  Samaziniet latentumu, novēršot novirzīšanu, nodrošinot ātru servera atbildi un iespējojot teksta saspiešanu."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Dokumenta pieprasījuma latentums"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Lai teksts vienmēr būtu redzams, ieteicams parametram [font-display](https://developer.chrome.com/blog/font-display) iestatīt vērtību swap vai optional. Lai mazinātu izkārtojuma nobīdes, swap var optimizēt vēl vairāk, izmantojot [fonta rādītāju ignorēšanu](https://developer.chrome.com/blog/font-fallbacks)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Fonta attēlojums"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Vispirms izpētiet garāko posmu. [Aizkaves var samazināt](https://web.dev/articles/optimize-inp#optimize_interactions). Lai samazinātu apstrādes ilgumu, [optimizējiet galvenā pavediena izmaksas](https://web.dev/articles/optimize-long-tasks) (parasti JS)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP pēc posma"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Optimizējiet LCP, padarot LCP attēlu nekavējoties [atklājamu](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) HTML struktūrā un [novēršot atlikto ielādi](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "LCP pieprasījuma atklāšana"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Katram [posmam ir noteiktas uzlabošanas stratēģijas](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideālā gadījumā lielāko daļu LCP laika ir jāveido resursu ielādei, nevis aizkavei."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP pēc fāzes"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Pieprasījumi bloķē lapas sākotnējo atveidi, un tas var aizkavēt LCP. [Atliekot vai iekļaujot](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) šos tīkla pieprasījumus, tos varat pārvietot ārpus kritiskā ceļa."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Atveidošanas bloķēšanas pieprasījumi"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "Ja izmaksas par stila pārrēķināšanu saglabājas augstas, tās var samazināt atlasītāja optimizācija. [Optimizējiet atlasītājus](https://developer.chrome.com/docs/devtools/performance/selector-stats), iestatot augstu pagājušā laika vērtību un augstu lēna ceļa % vērtību. Atbilstības izmaksas arī var samazināt, izmantojot vienkāršāku atlasītāju, mazāku skaitu atlasītāju, mazāku DOM un DOM koku ar mazāku līmeņu skaitu."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "CSS atlasītāja izmaksas"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Trešo pušu kods var ievērojami ietekmēt ielādes veiktspēju. Lai piešķirtu prioritāti savas lapas saturam, [ierobežojiet un atlieciet trešās puses koda ielādi](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Trešās puses"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "Lapas skatvieta nav optimizēta mobilajām ierīcēm, tāpēc mijiedarbība ar pieskārieniem var būt [aizkavēta līdz pat 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Skatvieta nav optimizēta mobilajām ierīcēm"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "Animētam saturam izmantojiet komponentu [`amp-anim`](https://amp.dev/documentation/components/amp-anim/), lai samazinātu centrālā procesora lietojumu, kamēr saturs nav redzams ekrānā."
   },

package/shared/localization/locales/nl.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Lighthouse-rapport over gebruikersstroom"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Indelingsverschuivingen komen voor als elementen bewegen zonder gebruikersinteractie. [Stel vast wat de oorzaak is van de indelingsverschuiving](https://web.dev/articles/optimize-cls), zoals elementen die worden toegevoegd of verwijderd, of het lettertype dat verandert terwijl de pagina wordt geladen."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Oorzaken van indelingsverschuivingen"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Je eerste netwerkverzoek is het belangrijkst.  Verminder de vertraging door omleidingen te vermijden, een snelle serverreactie te garanderen en tekstcompressie aan te zetten."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Vertraging van documentverzoek"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Overweeg [font-display](https://developer.chrome.com/blog/font-display) in te stellen op swap of optional om te zorgen dat tekst consistent zichtbaar is. swap kan verder worden geoptimaliseerd om indelingsverschuivingen te verminderen met [overschrijvingen van lettertypestatistieken](https://developer.chrome.com/blog/font-fallbacks)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Lettertypeweergave"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Onderzoek eerst de langste fase. [Je kunt vertraging tot een minimum beperken](https://web.dev/articles/optimize-inp#optimize_interactions). [Optimaliseer de kosten van de hoofdthread](https://web.dev/articles/optimize-long-tasks) (vaak JS) om de verwerkingsduur te verkorten."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP per fase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Optimaliseer LCP door de LCP-afbeelding [vindbaar](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) te maken vanuit de HTML en [lazy loading te voorkomen](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "LCP-verzoekdetectie"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Elke [fase heeft specifieke verbeteringsstrategieën](https://web.dev/articles/optimize-lcp#lcp-breakdown). Idealiter wordt het grootste deel van de LCP-tijd besteed aan het laden van de resources, niet aan vertragingen."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP per fase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Verzoeken blokkeren de eerste keer renderen van de pagina, waardoor LCP kan worden vertraagd. Door [verzoeken uit te stellen of in te sluiten](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) kun je deze netwerkverzoeken van de kritieke route verwijderen."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Verzoeken voor renderblokkering"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "Als de kosten van Stijl opnieuw berekenen hoog blijven, kun je ze verlagen met selectoroptimalisatie. [Optimaliseer de selectors](https://developer.chrome.com/docs/devtools/performance/selector-stats) met zowel een lange verstreken tijd als een hoog percentage langzame paden. Eenvoudigere selectors, minder selectors, een kleiner DOM en een minder diep DOM verlagen de kosten voor het zoeken naar overeenkomsten."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "Kosten van css-kiezer"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Code van derden kan van grote invloed zijn op de laadprestaties. [Verminder het laden van code van derden en stel dit uit](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/) om prioriteit te geven aan de content van je pagina."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Derden"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "Het kijkvenster van de pagina is niet geoptimaliseerd voor mobiele apparaten. Tikinteracties kunnen daarom [tot 300 ms vertraagd](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/) worden."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Kijkvenster niet geoptimaliseerd voor mobiel"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "Gebruik in het geval van content met animatie [`amp-anim`](https://amp.dev/documentation/components/amp-anim/) om het CPU-gebruik te minimaliseren als de content niet in beeld is."
   },

package/shared/localization/locales/no.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Lighthouse-rapport over brukerflyt"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Utseendeforskyvninger oppstår når elementer beveger seg uten at brukeren har gjort noe. [Undersøk årsakene til utseendeforskyvninger](https://web.dev/articles/optimize-cls), for eksempel elementer som legges til, fjernes eller endrer skrifttype mens siden lastes inn."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Årsaker til utseendeforskyvning"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Den første nettverksforespørselen er den viktigste.  Reduser tidsforsinkelsen ved å unngå omdirigeringer, sikre rask tjenerrespons og slå på tekstkomprimering."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Tidsforsinkelse for dokumentforespørsel"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Vurder å sette [font-display](https://developer.chrome.com/blog/font-display) til swap eller optional for å sikre at teksten er synlig hele tiden. swap kan optimaliseres ytterligere for å motvirke utseendeforskyvninger med [overstyring av skrifttypeverdier](https://developer.chrome.com/blog/font-fallbacks)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Visning av skrifttype"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Begynn med å undersøke den lengste fasen. [Forsinkelser kan minimeres.](https://web.dev/articles/optimize-inp#optimize_interactions) For å redusere behandlingstiden må du [optimalisere kostnadene på hovedtråden](https://web.dev/articles/optimize-long-tasks). Ofte er dette JS."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP (tid fra interaksjon til neste opptegning) etter fase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Optimaliser LCP (største innholdsrike opptegning) ved å gjøre LCP-bildet [synlig](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) umiddelbart i HTML-koden og [unngå bruk av utsatt innlasting](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "Oppdagelse av forespørsel med LCP (største innholdsrike opptegning)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Hver [fase har spesifikke forbedringsstrategier](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideelt sett bør mesteparten av LCP-tiden brukes på innlasting av ressurser, ikke på forsinkelser."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP (største innholdsrike opptegning) etter fase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Forespørsler blokkerer den innledende gjengivelsen av siden, noe som kan forsinke LCP (største innholdsrike opptegning). [Hvis du utsetter eller fletter inn disse](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/), flyttes disse nettverksforespørslene ut av den kritiske banen."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Forespørsler som blokkerer gjengivelse"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "Hvis kostnadene for omberegning av stiler fortsetter å være høye, kan du senke dem ved å optimalisere velgere. [Optimaliser velgere](https://developer.chrome.com/docs/devtools/performance/selector-stats) som både har lang forløpstid og følger den langsomme banen en stor prosentandel av tiden. Både enklere velgere, færre velgere, en mindre DOM og en mindre omfattende DOM er med på å senke kostnadene ved å beregne elementsamsvar."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "Kostnader for CSS-velger"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Tredjepartskode kan ha betydelig innvirkning på hvor lang tid det tar å laste inn siden. [Reduser og utsett innlasting av tredjepartskode](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/) for å prioritere innholdet på siden din."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Tredjeparter"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "Sidens synlige område er ikke mobiloptimalisert, så det kan [oppstå forsinkelser på opptil 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/) når brukeren trykker på siden."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Det synlige området er ikke optimalisert for mobil"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "For animert innhold, bruk [`amp-anim`‏](https://amp.dev/documentation/components/amp-anim/) for å minimere prosessorbruken når innholdet er utenfor skjermen."
   },

package/shared/localization/locales/pl.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Raport Lighthouse dotyczący przepływu użytkowników"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Przesunięcia układu występują, gdy elementy poruszają się bez interakcji ze strony użytkownika. [Zbadaj przyczyny przesunięć układu](https://web.dev/articles/optimize-cls) takie jak dodanie lub usunięcie elementów lub zmiana czcionek podczas wczytywania strony."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Przyczyny problemów związanych z przesunięciem układu"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Pierwsze żądanie sieciowe jest najważniejsze.  Zmniejsz jego opóźnienie, unikając przekierowań, zapewniając szybką reakcję serwera i włączając kompresję tekstu."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Czas oczekiwania w przypadku żądania dokumentu"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Sugerujemy ustawienie właściwości [font-display](https://developer.chrome.com/blog/font-display) na swap lub optional, aby tekst był zawsze widoczny. Element swap można dodatkowo zoptymalizować za pomocą [zastąpień danych o czcionkach](https://developer.chrome.com/blog/font-fallbacks) – pozwoli to zmniejszyć przesunięcia układu."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Wyświetlanie czcionki"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Zacznij analizę od najdłuższego etapu. [Można zminimalizować opóźnienia](https://web.dev/articles/optimize-inp#optimize_interactions). Aby skrócić czas przetwarzania, [zoptymalizuj koszty wątku głównego](https://web.dev/articles/optimize-long-tasks), często JS."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP według etapu"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Zoptymalizuj LCP, zapewniając natychmiastową [wykrywalność](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) obrazu LCP w kodzie HTML i [unikając leniwego ładowania](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "Wykrywanie żądań LCP"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Każdy [etap ma określone strategie poprawy](https://web.dev/articles/optimize-lcp#lcp-breakdown). W idealnym przypadku większość czasu LCP powinna być poświęcona na ładowanie zasobów, a nie na opóźnienia."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP według etapu"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Żądania blokują początkowe renderowanie strony, co może opóźniać LCP. [Opóźnianie lub wstawianie](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) może skierować te żądania sieciowe poza ścieżkę krytyczną."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Prośby o zablokowanie renderowania"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "Jeśli koszty ponownego obliczania stylu są wysokie, optymalizacja selektora może je obniżyć. [Zoptymalizuj selektory](https://developer.chrome.com/docs/devtools/performance/selector-stats), które mają zarówno długi czas działania, jak i wysoki odsetek ścieżek powolnych. Prostsze selektory, mniejsza ich liczba oraz mniejszy i płytszy DOM pozwolą zmniejszyć koszty dopasowywania."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "Koszty selektora CSS"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Kod spoza witryny może znacznie spowalniać wczytywanie stron. [Ogranicz i opóźnij wczytywanie kodu spoza witryny](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/), aby nadać priorytet treściom ze swojej strony."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Spoza witryny"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "Widoczny obszar strony nie jest zoptymalizowany pod kątem urządzeń mobilnych, więc interakcje dotykowe mogą być [opóźnione nawet o 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Widoczny obszar niezoptymalizowany pod kątem urządzeń mobilnych"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "W przypadku treści animowanych stosuj atrybut [`amp-anim`](https://amp.dev/documentation/components/amp-anim/), by zminimalizować wykorzystanie procesora, gdy te treści znajdują się poza ekranem."
   },

package/shared/localization/locales/pt-PT.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Relatório do fluxo do utilizador do Lighthouse"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "As mudanças de esquema ocorrem quando os elementos se movem sem nenhuma interação do utilizador. [Investigue as causas das mudanças de esquema](https://web.dev/articles/optimize-cls), como a adição ou a remoção de elementos ou a alteração dos respetivos tipos de letra à medida que a página é carregada."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Causas da mudança de esquema"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "O primeiro pedido de rede é o mais importante.  Reduza a latência evitando redirecionamentos, assegurando uma resposta rápida do servidor e ativando a compressão de texto."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Latência do pedido de documento"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Considere definir [font-display](https://developer.chrome.com/blog/font-display) como swap ou optional para garantir que o texto é visível de forma consistente. É possível otimizar ainda mais o swap para mitigar as mudanças de esquema com [substituições de métricas de tipos de letra](https://developer.chrome.com/blog/font-fallbacks)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Apresentação do tipo de letra"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Comece a investigar com a fase mais longa. [Os atrasos podem ser minimizados](https://web.dev/articles/optimize-inp#optimize_interactions). Para reduzir a duração do processamento, [otimize os custos da thread principal](https://web.dev/articles/optimize-long-tasks), muitas vezes JS."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP por fase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Otimize o LCP tornando a imagem do LCP [detetável](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) imediatamente a partir do HTML e [evitando o carregamento em diferido](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "Deteção de pedidos de LCP"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Cada [fase tem estratégias de melhoria específicas](https://web.dev/articles/optimize-lcp#lcp-breakdown). Idealmente, a maior parte do tempo de LCP deve ser gasto no carregamento dos recursos e não nos atrasos."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP por fase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Os pedidos estão a bloquear a renderização inicial da página, o que pode atrasar o LCP. [Adiar ou colocar inline](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) pode remover estes pedidos de rede do caminho crítico."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Pedidos de bloqueio de renderização"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "Se os custos de Recalcular estilo permanecerem elevados, a otimização do seletor pode reduzi-los. [Otimize os seletores](https://developer.chrome.com/docs/devtools/performance/selector-stats) com um tempo decorrido elevado e uma percentagem de caminho lento elevada. Seletores mais simples, menos seletores, um DOM menor e um DOM mais superficial reduzem os custos de correspondência."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "Custos do seletor CSS"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "O código de terceiros pode afetar significativamente o desempenho de carregamento. [Reduza e adie o carregamento de código de terceiros](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/) para dar prioridade ao conteúdo da sua página."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Terceiros"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "A área visível da página não está otimizada para dispositivos móveis e, por isso, as interações com toques podem ter um [atraso de até 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Área visível não otimizada para dispositivos móveis"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "Para conteúdo animado, utilize [`amp-anim`](https://amp.dev/documentation/components/amp-anim/) para minimizar a utilização da CPU quando o conteúdo não está visível."
   },