Skip to content
https://sbs.army

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

90

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
usforces.army/api/media/file/Magyar.svg?2026-05-04T07:43:08.572Z1209600.0 s7.5 KiB
usforces.army/api/media/file/K2_logo.svg?2026-01-15T16:04:19.348Z1209600.0 s6.5 KiB
/api/media/file/%D0%A0%D0%B0%D1%80%D0%BE%D0%B3.svg?2025-1...1209600.0 s6.4 KiB
usforces.army/api/media/file/59shhhh-02%25201.svg?2026-01-15T16:08:17.778Z1209600.0 s4.1 KiB
usforces.army/api/media/file/1-center-logo_u.svg?2026-01-02T08:11:09.817Z1209600.0 s4.0 KiB
/api/media/file/Component%201%20(1).svg?2025-10-30T14:58:...1209600.0 s3.6 KiB
usforces.army/api/media/file/nemesis_icon_2.svg?2025-12-20T09:54:57.768Z1209600.0 s3.2 KiB
usforces.army/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js172791.0 s936 B
usforces.army/api/media/file/hawks_icon.svg?2025-12-20T09:58:27.181Z1209600.0 s2.6 KiB
usforces.army/api/media/file/9_icon.svg?2025-12-20T10:05:51.348Z1209600.0 s1.4 KiB
usforces.army/api/media/file/Achilles.svg?2025-10-30T14:53:23.586Z1209600.0 s1.2 KiB
usforces.army/api/media/file/Reyd-1.svg?2025-12-19T11:36:22.063Z1209600.0 s770 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Бойові посади div.select-none > div > picture > img.group-hover:scale-105
/_next/image?url=%2Fapi%2Fmedia%2Ffile%2Fboyovi2.webp%3F2...128.2 KiB84.4 KiB
Тилові посади div.select-none > div > picture > img.group-hover:scale-105
/_next/image?url=%2Fapi%2Fmedia%2Ffile%2Ftylovi3.webp%3F2...120.8 KiB77.0 KiB
Обирай з 15 000 вакансій у Силах безпілотних систем section.relative > div.absolute > picture.absolute > img.absolute
/_next/image?url=%2Fapi%2Fmedia%2Ffile%2Fmain_hero_m_upd2...219.8 KiB13.6 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
usforces.army/_next/static/css/df808db80ea6530c.css16.7 KiB
usforces.army/_next/static/css/34daaa51324022bb.css427 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 867 ms
URLTime Spent
sbs.army/403 ms
usforces.army/238 ms
sbs.army/225 ms
usforces.army/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 10 ms 10.0 KiB
URLTransfer SizeEst Savings
usforces.army/_next/static/css/df808db80ea6530c.css15.5 KiB10.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 251.7 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-NT6JCV4W3J&cx=c&gtm=4e67e1h2182.5 KiB69.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-TMXZ3Q66153.5 KiB68.6 KiB
www.googletagmanager.com/gtag/js?id=AW-17476733107&cx=c&gtm=4e67e1h2151.1 KiB57.8 KiB
usforces.army/_next/static/chunks/5587-061ef630adcec5e9.js104.0 KiB34.9 KiB
usforces.army/_next/static/chunks/4053-10668a376397d5b8.js37.9 KiB20.6 KiB

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

●Max Potential First Input Delay 120 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,759 KiB
●JavaScript execution time 0.7 s
●Minimizes main-thread work 1.3 s
●Avoid long main-thread tasks 4 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 180 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 210 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
93

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Тилові посади tr.group/row > td.[&:has([role=checkbox])]:pr-0 > div.flex > span.text-label
Бойові посади tr.group/row > td.[&:has([role=checkbox])]:pr-0 > div.flex > span.text-label
Бойові посади tr.group/row > td.[&:has([role=checkbox])]:pr-0 > div.flex > span.text-label
Тилові посади tr.group/row > td.[&:has([role=checkbox])]:pr-0 > div.flex > span.text-label
Бойові посади tr.group/row > td.[&:has([role=checkbox])]:pr-0 > div.flex > span.text-label
Бойові посади tr.group/row > td.[&:has([role=checkbox])]:pr-0 > div.flex > span.text-label
Тилові посади tr.group/row > td.[&:has([role=checkbox])]:pr-0 > div.flex > span.text-label
Крок 1 div.relative > div.flex > div.flex > span.text-label
Крок 2 div.relative > div.flex > div.flex > span.text-label
Крок 3 div.relative > div.flex > div.flex > span.text-label
Крок 4 div.relative > div.flex > div.flex > span.text-label
Крок 5 div.relative > div.flex > div.flex > span.text-label
Крок 6 div.relative > div.flex > div.flex > span.text-label

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Новини ul.group > li.relative > button#radix-_R_4l99fivb_-trigger-radix-_R_4sl99fivb_ > a.group
Вакансії ul.group > li.relative > button#radix-_R_4l99fivb_-trigger-radix-_R_6sl99fivb_ > a.group
Підрозділи ul.group > li.relative > button#radix-_R_4l99fivb_-trigger-radix-_R_8sl99fivb_ > a.group

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Підрозділ Посада Тип Зарплата (грн) 414-та окрема бригада безпілотних систе… div > div.hidden > div.relative > table.w-full
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Elements with visible text labels have matching accessible names.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
www.googletagmanager.com/gtm.js?id=GTM-TMXZ3Q66 line 204, col 390
Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=1191224071.1784147395&gtm=45He67e1h2v9189935182za200zd9189935182xea' violates the following Content Security Policy directive: "connect-src 'self' https://usforces.army https://www.googletagmanager.com https://analytics.google.com https://www.google-analytics.com https://stats.g.doubleclick.net https://www.google.com https://www.google.com.ua". The action has been blocked.
www.googletagmanager.com/gtm.js?id=GTM-TMXZ3Q66 line 204, col 390
Fetch API cannot load https://ad.doubleclick.net/ccm/s/collect?auid=1191224071.1784147395&gtm=45He67e1h2v9189935182za200zd9189935182xea. Refused to connect because it violates the document's Content Security Policy.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback