lighthouse 12.2.3-dev.20241210 → 12.2.3

package/shared/localization/locales/da.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Rapport over brugerflow i Lighthouse"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Layoutændringer opstår, når elementer bevæger sig uden brugerinteraktion. [Undersøg årsagerne til layoutændringer](https://web.dev/articles/optimize-cls), f.eks. elementer, der tilføjes eller fjernes eller ændrer skrifttyper, mens siden indlæses."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Årsager til layoutskift"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Din første netværksanmodning er den vigtigste.  Reducer forsinkelsen ved at undgå omdirigeringer, sikre en hurtig serversvartid og aktivere tekstkomprimering."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Forsinkelse for dokumentanmodning"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Overvej at angive [font-display](https://developer.chrome.com/blog/font-display) som swap eller optional for at sikre, at teksten er synlig hele tiden. swap kan optimeres yderligere for at mindske layoutskift med [tilsidesættelse af skriftmetrics](https://developer.chrome.com/blog/font-fallbacks)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Skrifttypevisning"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Start med at undersøge den længste fase. [Forsinkelser kan minimeres](https://web.dev/articles/optimize-inp#optimize_interactions). Hvis du vil reducere behandlingsvarigheden, skal du [optimere omkostningerne for hovedtråden](https://web.dev/articles/optimize-long-tasks) (typisk JS)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP efter fase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Optimer LCP ved at gøre LCP-billedet [synligt](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) i HTML med det samme, og [undgå lazy loading](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "Registrering af LCP-anmodning"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Hver [fase har specifikke forbedringsstrategier](https://web.dev/articles/optimize-lcp#lcp-breakdown). Det meste af LCP-tiden bør ideelt set bruges på at indlæse ressourcerne og ikke på forsinkelser."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP efter fase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Anmodninger blokerer for sidens oprindelige gengivelse, hvilket kan forsinke LCP. [Udsættelse eller indlejring](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) kan flytte disse netværksanmodninger væk fra den kritiske sti."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Anmodninger, der blokerer gengivelse"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "Hvis omkostningerne for Genberegn typografi forbliver høje, kan vælgeroptimering reducere dem. [Optimer vælgere](https://developer.chrome.com/docs/devtools/performance/selector-stats), der både har lang forløbstid og langsom vej en stor procentdel af tiden. Enklere vælgere, færre vælgere, en mindre DOM og en mindre omfattende DOM er med til at reducere omkostningerne ved matching."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "Omkostninger for CSS-vælger"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Kode fra tredjeparter kan have en væsentlig indvirkning på indlæsningen. [Reducer og udskyd indlæsningen af tredjepartskoden](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/) for at prioritere din sides indhold."
-  },
-  "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 viewport er ikke optimeret til brug på mobil, så trykinteraktioner kan blive [forsinket med op til 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Viewport er ikke optimeret til mobil"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "Ved animeret indhold bør du bruge [`amp-anim`](https://amp.dev/documentation/components/amp-anim/) til at minimere brugen af CPU, når indholdet er uden for skærmen."
   },

package/shared/localization/locales/de.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Lighthouse-Bericht zur Aufrufabfolge"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Layout Shifts treten auf, wenn sich Elemente ohne Nutzerinteraktion bewegen. [Untersuche die Ursachen von Layout Shifts](https://web.dev/articles/optimize-cls), beispielsweise Elemente, die hinzugefügt oder entfernt werden oder deren Schriftart sich beim Laden der Seite ändert."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Verursacher von Layout Shifts"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Deine erste Netzwerkanfrage ist die wichtigste.  Verringere die Latenz, indem du Weiterleitungen vermeidest, eine schnelle Serverantwort sicherstellst und die Textkomprimierung aktivierst."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Latenz der Dokumentanfrage"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Du kannst [font-display](https://developer.chrome.com/blog/font-display) auf „swap“ oder „optional“ setzen, damit der Text immer sichtbar ist. „swap“ kann weiter optimiert werden, um Layout Shifts durch [Überschreibungen von Messwerten zur Schriftart](https://developer.chrome.com/blog/font-fallbacks) zu reduzieren."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Schriftart-Anzeige"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Sieh dir zuerst die längste Phase an. [Verzögerungen können minimiert werden.](https://web.dev/articles/optimize-inp#optimize_interactions) Damit sich die Verarbeitungsdauer verringert, [musst du die Kosten des Hauptthreads](https://web.dev/articles/optimize-long-tasks), meist JS, optimieren."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP nach Phase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Optimiere den LCP, indem du das LCP-Bild im HTML-Code direkt [sichtbar](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) machst und [Lazy Loading vermeidest](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "LCP-Anfrageerkennung"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Für jede [Phase gibt es spezifische Verbesserungsstrategien](https://web.dev/articles/optimize-lcp#lcp-breakdown). Idealerweise sollte der Großteil der LCP-Zeit für das Laden der Ressourcen und nicht für Verzögerungen aufgewendet werden."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP nach Phase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Anfragen blockieren das erste Rendering der Seite, was den LCP verzögern kann. [Durch das Verschieben oder Einfügen](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) können diese Netzwerkanfragen aus dem kritischen Pfad entfernt werden."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Anfragen zum Blockieren des Renderings"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "Wenn die Kosten für die Stilneuberechnung hoch bleiben, kann eine Selector-Optimierung diese senken. [Optimiere die Selectors](https://developer.chrome.com/docs/devtools/performance/selector-stats), bei denen sowohl die verstrichene Zeit als auch der Prozentsatz der langsamen Pfade hoch ist. Einfachere Selectors, weniger Selectors, ein kleineres DOM sowie ein flacheres DOM reduzieren die Kosten für den Abgleich."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "Kosten für CSS-Selektor"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Code von Drittanbietern kann die Ladegeschwindigkeit erheblich beeinträchtigen. [Reduziere Drittanbietercode und stelle den Ladevorgang zurück](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/), um die Inhalte deiner Seite zu priorisieren."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Drittanbieter"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "Der Darstellungsbereich der Seite ist nicht für Mobilgeräte optimiert. Daher kann es bei Interaktionen durch Tippen zu einer [Verzögerung von bis zu 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/) kommen."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Darstellungsbereich nicht für Mobilgeräte optimiert"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "Verwende [`amp-anim`](https://amp.dev/documentation/components/amp-anim/) für animierte Inhalte, um die CPU-Last auf ein Mindestmaß zu reduzieren, wenn die Inhalte nicht zu sehen sind."
   },

package/shared/localization/locales/el.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). Για να μειώσετε τη διάρκεια επεξεργασίας, [βελτιστοποιήστε τα κόστη κύριου νήματος](https://web.dev/articles/optimize-long-tasks), συχνά σε JS."
-  },
-  "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 κάνοντας την εικόνα LCP [ανακαλύψιμη](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) απευθείας από το HTML και [αποφεύγοντας την αργή φόρτωση](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "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) με υψηλό χρόνο που έχει παρέλθει και υψηλό ποσοστό slow-path. Το κόστος αντιστοίχισης μπορεί να μειωθεί με τη χρήση λιγότερων και απλούστερων επιλογέων και 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 ms](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/en-GB.json

@@ -2621,66 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Lighthouse user flow report"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://web.dev/articles/optimize-cls), such as elements being added, removed or their fonts changing as the page loads."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Layout shift culprits"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Your first network request is the most important.  Reduce its latency by avoiding redirects, ensuring a fast server response and enabling text compression."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Document request latency"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure that text is consistently visible. swap can be further optimised to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Font display"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Start investigating with the longest phase. [Delays can be minimised](https://web.dev/articles/optimize-inp#optimize_interactions). To reduce processing duration, [optimise the main-thread costs](https://web.dev/articles/optimize-long-tasks), often JS."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP by phase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Optimise LCP by making the LCP image [discoverable](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) from the HTML immediately and [avoiding lazy loading](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "LCP request discovery"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Each [phase has specific improvement strategies](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP by phase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) can move these network requests out of the critical path."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Render blocking requests"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "If Recalculate Style costs remain high, selector optimisation can reduce them. [Optimise the selectors](https://developer.chrome.com/docs/devtools/performance/selector-stats) with both a high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM and a shallower DOM will all reduce matching costs."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "CSS selector costs"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Third-party code can significantly impact load performance. [Reduce and defer loading of third-party code](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/) to prioritise your page's content."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Third parties"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "The page's viewport is not mobile-optimised, so tap interactions may be [delayed by up to 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Viewport not optimised for mobile"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "For animated content, use [`amp-anim`](https://amp.dev/documentation/components/amp-anim/) to minimise CPU usage when the content is offscreen."
   },

package/shared/localization/locales/en-US.json

@@ -977,36 +977,6 @@
   "core/audits/font-display.js | undeclaredFontOriginWarning": {
     "message": "{fontCountForOrigin, plural, =1 {Lighthouse was unable to automatically check the `font-display` value for the origin {fontOrigin}.} other {Lighthouse was unable to automatically check the `font-display` values for the origin {fontOrigin}.}}"
   },
-  "core/audits/has-hsts.js | columnDirective": {
-    "message": "Directive"
-  },
-  "core/audits/has-hsts.js | columnSeverity": {
-    "message": "Severity"
-  },
-  "core/audits/has-hsts.js | description": {
-    "message": "Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. [Learn more about using a strong HSTS policy.](https://developer.chrome.com/docs/lighthouse/best-practices/has-hsts)"
-  },
-  "core/audits/has-hsts.js | invalidSyntax": {
-    "message": "Invalid syntax"
-  },
-  "core/audits/has-hsts.js | lowMaxAge": {
-    "message": "`max-age` is too low"
-  },
-  "core/audits/has-hsts.js | noHsts": {
-    "message": "No HSTS header found"
-  },
-  "core/audits/has-hsts.js | noMaxAge": {
-    "message": "No `max-age` directive"
-  },
-  "core/audits/has-hsts.js | noPreload": {
-    "message": "No `preload` directive found"
-  },
-  "core/audits/has-hsts.js | noSubdomain": {
-    "message": "No `includeSubDomains` directive found"
-  },
-  "core/audits/has-hsts.js | title": {
-    "message": "Use a strong HSTS policy"
-  },
   "core/audits/image-aspect-ratio.js | columnActual": {
     "message": "Aspect Ratio (Actual)"
   },
@@ -1706,15 +1676,6 @@
   "core/gather/timespan-runner.js | warningNavigationDetected": {
     "message": "A page navigation was detected during the run. Using timespan mode to audit page navigations is not recommended. Use navigation mode to audit page navigations for better third-party attribution and main thread detection."
   },
-  "core/lib/bf-cache-strings.js | HTTPMethodNotGET": {
-    "message": "Only pages loaded via a GET request are eligible for back/forward cache."
-  },
-  "core/lib/bf-cache-strings.js | HTTPStatusNotOK": {
-    "message": "Only pages with a status code of 2XX can be cached."
-  },
-  "core/lib/bf-cache-strings.js | JavaScriptExecution": {
-    "message": "Chrome detected an attempt to execute JavaScript while in the cache."
-  },
   "core/lib/bf-cache-strings.js | appBanner": {
     "message": "Pages that requested an AppBanner are not currently eligible for back/forward cache."
   },
@@ -1814,12 +1775,12 @@
   "core/lib/bf-cache-strings.js | embedderExtensionMessagingForOpenPort": {
     "message": "Extensions with long-lived connection should close the connection before entering back/forward cache."
   },
-  "core/lib/bf-cache-strings.js | embedderExtensionSentMessageToCachedFrame": {
-    "message": "Extensions with long-lived connection attempted to send messages to frames in back/forward cache."
-  },
   "core/lib/bf-cache-strings.js | embedderExtensions": {
     "message": "Back/forward cache is disabled due to extensions."
   },
+  "core/lib/bf-cache-strings.js | embedderExtensionSentMessageToCachedFrame": {
+    "message": "Extensions with long-lived connection attempted to send messages to frames in back/forward cache."
+  },
   "core/lib/bf-cache-strings.js | embedderModalDialog": {
     "message": "Modal dialog such as form resubmission or http password dialog was shown for the page upon navigating away."
   },
@@ -1859,6 +1820,12 @@
   "core/lib/bf-cache-strings.js | haveInnerContents": {
     "message": "Pages that use portals are not currently eligible for back/forward cache."
   },
+  "core/lib/bf-cache-strings.js | HTTPMethodNotGET": {
+    "message": "Only pages loaded via a GET request are eligible for back/forward cache."
+  },
+  "core/lib/bf-cache-strings.js | HTTPStatusNotOK": {
+    "message": "Only pages with a status code of 2XX can be cached."
+  },
   "core/lib/bf-cache-strings.js | idleManager": {
     "message": "Pages that use IdleManager are not currently eligible for back/forward cache."
   },
@@ -1880,6 +1847,9 @@
   "core/lib/bf-cache-strings.js | internalError": {
     "message": "Internal error."
   },
+  "core/lib/bf-cache-strings.js | JavaScriptExecution": {
+    "message": "Chrome detected an attempt to execute JavaScript while in the cache."
+  },
   "core/lib/bf-cache-strings.js | keepaliveRequest": {
     "message": "Back/forward cache is disabled due to a keepalive request."
   },
@@ -2093,12 +2063,12 @@
   "core/lib/csp-evaluator.js | plainWildcards": {
     "message": "Avoid using plain wildcards ({keyword}) in this directive. Plain wildcards allow scripts to be sourced from an unsafe domain."
   },
-  "core/lib/csp-evaluator.js | reportToOnly": {
-    "message": "The reporting destination is only configured via the report-to directive. This directive is only supported in Chromium-based browsers so it is recommended to also use a `report-uri` directive."
-  },
   "core/lib/csp-evaluator.js | reportingDestinationMissing": {
     "message": "No CSP configures a reporting destination. This makes it difficult to maintain the CSP over time and monitor for any breakages."
   },
+  "core/lib/csp-evaluator.js | reportToOnly": {
+    "message": "The reporting destination is only configured via the report-to directive. This directive is only supported in Chromium-based browsers so it is recommended to also use a `report-uri` directive."
+  },
   "core/lib/csp-evaluator.js | strictDynamic": {
     "message": "Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with `'strict-dynamic'` if necessary."
   },
@@ -2126,9 +2096,6 @@
   "core/lib/deprecations-strings.js | AuthorizationCoveredByWildcard": {
     "message": "Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers` handling."
   },
-  "core/lib/deprecations-strings.js | CSSSelectorInternalMediaControlsOverlayCastButton": {
-    "message": "The `disableRemotePlayback` attribute should be used in order to disable the default Cast integration instead of using `-internal-media-controls-overlay-cast-button` selector."
-  },
   "core/lib/deprecations-strings.js | CanRequestURLHTTPContainingNewline": {
     "message": "Resource requests whose URLs contained both removed whitespace `(n|r|t)` characters and less-than characters (`<`) are blocked. Please remove newlines and encode less-than characters from places like element attribute values in order to load these resources."
   },
@@ -2153,8 +2120,8 @@
   "core/lib/deprecations-strings.js | CrossOriginWindowConfirm": {
     "message": "Triggering window.confirm from cross origin iframes has been deprecated and will be removed in the future."
   },
-  "core/lib/deprecations-strings.js | DOMMutationEvents": {
-    "message": "DOM Mutation Events, including `DOMSubtreeModified`, `DOMNodeInserted`, `DOMNodeRemoved`, `DOMNodeRemovedFromDocument`, `DOMNodeInsertedIntoDocument`, and `DOMCharacterDataModified` are deprecated (https://w3c.github.io/uievents/#legacy-event-types) and will be removed. Please use `MutationObserver` instead."
+  "core/lib/deprecations-strings.js | CSSSelectorInternalMediaControlsOverlayCastButton": {
+    "message": "The `disableRemotePlayback` attribute should be used in order to disable the default Cast integration instead of using `-internal-media-controls-overlay-cast-button` selector."
   },
   "core/lib/deprecations-strings.js | DataUrlInSvgUse": {
     "message": "Support for data: URLs in SVG <use> element is deprecated and it will be removed in the future."
@@ -2162,6 +2129,9 @@
   "core/lib/deprecations-strings.js | DocumentDomainSettingWithoutOriginAgentClusterHeader": {
     "message": "Relaxing the same-origin policy by setting `document.domain` is deprecated, and will be disabled by default. To continue using this feature, please opt-out of origin-keyed agent clusters by sending an `Origin-Agent-Cluster: ?0` header along with the HTTP response for the document and frames. See https://developer.chrome.com/blog/immutable-document-domain/ for more details."
   },
+  "core/lib/deprecations-strings.js | DOMMutationEvents": {
+    "message": "DOM Mutation Events, including `DOMSubtreeModified`, `DOMNodeInserted`, `DOMNodeRemoved`, `DOMNodeRemovedFromDocument`, `DOMNodeInsertedIntoDocument`, and `DOMCharacterDataModified` are deprecated (https://w3c.github.io/uievents/#legacy-event-types) and will be removed. Please use `MutationObserver` instead."
+  },
   "core/lib/deprecations-strings.js | ExpectCTHeader": {
     "message": "The `Expect-CT` header is deprecated and will be removed. Chrome requires Certificate Transparency for all publicly trusted certificates issued after April 30, 2018."
   },
@@ -2195,12 +2165,12 @@
   "core/lib/deprecations-strings.js | MediaSourceDurationTruncatingBuffered": {
     "message": "Setting `MediaSource.duration` below the highest presentation timestamp of any buffered coded frames is deprecated due to specification change. Support for implicit removal of truncated buffered media will be removed in the future. You should instead perform explicit `remove(newDuration, oldDuration)` on all `sourceBuffers`, where `newDuration < oldDuration`."
   },
-  "core/lib/deprecations-strings.js | NoSysexWebMIDIWithoutPermission": {
-    "message": "Web MIDI will ask a permission to use even if the sysex is not specified in the `MIDIOptions`."
-  },
   "core/lib/deprecations-strings.js | NonStandardDeclarativeShadowDOM": {
     "message": "The older, non-standardized `shadowroot` attribute is deprecated, and will *no longer function* in M119. Please use the new, standardized `shadowrootmode` attribute instead."
   },
+  "core/lib/deprecations-strings.js | NoSysexWebMIDIWithoutPermission": {
+    "message": "Web MIDI will ask a permission to use even if the sysex is not specified in the `MIDIOptions`."
+  },
   "core/lib/deprecations-strings.js | NotificationInsecureOrigin": {
     "message": "The Notification API may no longer be used from insecure origins. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gle/chrome-insecure-origins for more details."
   },
@@ -2237,24 +2207,30 @@
   "core/lib/deprecations-strings.js | PrefixedVideoDisplayingFullscreen": {
     "message": "HTMLVideoElement.webkitDisplayingFullscreen is deprecated. Please use Document.fullscreenElement instead."
   },
-  "core/lib/deprecations-strings.js | PrefixedVideoEnterFullScreen": {
-    "message": "HTMLVideoElement.webkitEnterFullScreen() is deprecated. Please use Element.requestFullscreen() instead."
-  },
   "core/lib/deprecations-strings.js | PrefixedVideoEnterFullscreen": {
     "message": "HTMLVideoElement.webkitEnterFullscreen() is deprecated. Please use Element.requestFullscreen() instead."
   },
-  "core/lib/deprecations-strings.js | PrefixedVideoExitFullScreen": {
-    "message": "HTMLVideoElement.webkitExitFullScreen() is deprecated. Please use Document.exitFullscreen() instead."
+  "core/lib/deprecations-strings.js | PrefixedVideoEnterFullScreen": {
+    "message": "HTMLVideoElement.webkitEnterFullScreen() is deprecated. Please use Element.requestFullscreen() instead."
   },
   "core/lib/deprecations-strings.js | PrefixedVideoExitFullscreen": {
     "message": "HTMLVideoElement.webkitExitFullscreen() is deprecated. Please use Document.exitFullscreen() instead."
   },
+  "core/lib/deprecations-strings.js | PrefixedVideoExitFullScreen": {
+    "message": "HTMLVideoElement.webkitExitFullScreen() is deprecated. Please use Document.exitFullscreen() instead."
+  },
   "core/lib/deprecations-strings.js | PrefixedVideoSupportsFullscreen": {
     "message": "HTMLVideoElement.webkitSupportsFullscreen is deprecated. Please use Document.fullscreenEnabled instead."
   },
   "core/lib/deprecations-strings.js | PrivacySandboxExtensionsAPI": {
     "message": "We're deprecating the API `chrome.privacy.websites.privacySandboxEnabled`, though it will remain active for backward compatibility until release M113. Instead, please use `chrome.privacy.websites.topicsEnabled`, `chrome.privacy.websites.fledgeEnabled` and `chrome.privacy.websites.adMeasurementEnabled`. See https://developer.chrome.com/docs/extensions/reference/privacy/#property-websites-privacySandboxEnabled."
   },
+  "core/lib/deprecations-strings.js | RangeExpand": {
+    "message": "Range.expand() is deprecated. Please use Selection.modify() instead."
+  },
+  "core/lib/deprecations-strings.js | RequestedSubresourceWithEmbeddedCredentials": {
+    "message": "Subresource requests whose URLs contain embedded credentials (e.g. `https://user:pass@host/`) are blocked."
+  },
   "core/lib/deprecations-strings.js | RTCConstraintEnableDtlsSrtpFalse": {
     "message": "The constraint `DtlsSrtpKeyAgreement` is removed. You have specified a `false` value for this constraint, which is interpreted as an attempt to use the removed `SDES key negotiation` method. This functionality is removed; use a service that supports `DTLS key negotiation` instead."
   },
@@ -2264,12 +2240,6 @@
   "core/lib/deprecations-strings.js | RTCPeerConnectionGetStatsLegacyNonCompliant": {
     "message": "The callback-based getStats() is deprecated and will be removed. Use the spec-compliant getStats() instead."
   },
-  "core/lib/deprecations-strings.js | RangeExpand": {
-    "message": "Range.expand() is deprecated. Please use Selection.modify() instead."
-  },
-  "core/lib/deprecations-strings.js | RequestedSubresourceWithEmbeddedCredentials": {
-    "message": "Subresource requests whose URLs contain embedded credentials (e.g. `https://user:pass@host/`) are blocked."
-  },
   "core/lib/deprecations-strings.js | RtcpMuxPolicyNegotiate": {
     "message": "The `rtcpMuxPolicy` option is deprecated and will be removed."
   },
@@ -2411,12 +2381,12 @@
   "core/lib/i18n/i18n.js | ms": {
     "message": "{timeInMs, number, milliseconds} ms"
   },
-  "core/lib/i18n/i18n.js | otherResourceType": {
-    "message": "Other"
-  },
   "core/lib/i18n/i18n.js | otherResourcesLabel": {
     "message": "Other resources"
   },
+  "core/lib/i18n/i18n.js | otherResourceType": {
+    "message": "Other"
+  },
   "core/lib/i18n/i18n.js | scriptResourceType": {
     "message": "Script"
   },
@@ -2651,72 +2621,6 @@
   "flow-report/src/i18n/ui-strings.js | title": {
     "message": "Lighthouse User Flow Report"
   },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | description": {
-    "message": "Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://web.dev/articles/optimize-cls), such as elements being added, removed, or their fonts changing as the page loads."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/CLSCulprits.js | title": {
-    "message": "Layout shift culprits"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | description": {
-    "message": "Your first network request is the most important.  Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/DocumentLatency.js | title": {
-    "message": "Document request latency"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | description": {
-    "message": "Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/FontDisplay.js | title": {
-    "message": "Font display"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ImageDelivery.js | description": {
-    "message": "Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/lighthouse/performance/uses-optimized-images/)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ImageDelivery.js | title": {
-    "message": "Improve image delivery"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | description": {
-    "message": "Start investigating with the longest phase. [Delays can be minimized](https://web.dev/articles/optimize-inp#optimize_interactions). To reduce processing duration, [optimize the main-thread costs](https://web.dev/articles/optimize-long-tasks), often JS."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/InteractionToNextPaint.js | title": {
-    "message": "INP by phase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | description": {
-    "message": "Optimize LCP by making the LCP image [discoverable](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) from the HTML immediately, and [avoiding lazy-loading](https://web.dev/articles/lcp-lazy-loading)"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPDiscovery.js | title": {
-    "message": "LCP request discovery"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | description": {
-    "message": "Each [phase has specific improvement strategies](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/LCPPhases.js | title": {
-    "message": "LCP by phase"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | description": {
-    "message": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources/) can move these network requests out of the critical path."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/RenderBlocking.js | title": {
-    "message": "Render blocking requests"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | description": {
-    "message": "If Recalculate Style costs remain high, selector optimization can reduce them. [Optimize the selectors](https://developer.chrome.com/docs/devtools/performance/selector-stats) with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/SlowCSSSelector.js | title": {
-    "message": "CSS Selector costs"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | description": {
-    "message": "Third party code can significantly impact load performance. [Reduce and defer loading of third party code](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/) to prioritize your page's content."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/ThirdParties.js | title": {
-    "message": "Third parties"
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | description": {
-    "message": "The page's viewport is not mobile-optimized, so tap interactions may be [delayed by up to 300 ms](https://developer.chrome.com/blog/300ms-tap-delay-gone-away/)."
-  },
-  "node_modules/@paulirish/trace_engine/models/trace/insights/Viewport.js | title": {
-    "message": "Viewport not optimized for mobile"
-  },
   "node_modules/lighthouse-stack-packs/packs/amp.js | efficient-animated-content": {
     "message": "For animated content, use [`amp-anim`](https://amp.dev/documentation/components/amp-anim/) to minimize CPU usage when the content is offscreen."
   },
@@ -3224,12 +3128,12 @@
   "report/renderer/report-utils.js | dropdownSaveJSON": {
     "message": "Save as JSON"
   },
-  "report/renderer/report-utils.js | dropdownViewUnthrottledTrace": {
-    "message": "View Unthrottled Trace"
-  },
   "report/renderer/report-utils.js | dropdownViewer": {
     "message": "Open in Viewer"
   },
+  "report/renderer/report-utils.js | dropdownViewUnthrottledTrace": {
+    "message": "View Unthrottled Trace"
+  },
   "report/renderer/report-utils.js | errorLabel": {
     "message": "Error!"
   },