Skip to content
https://comptia.org

Lighthouse Mobile

· 0 checks — Mobile 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.

71

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.

Consider setting 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
www.comptia.org/fonts/Inter-VariableFont.ttf135 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: SecAI+ Certification product logo
path: 1,HTML,1,BODY,4,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,2,DIV,0,IMG
selector: div.ImagePlusTextBlock > div.image-text-block > div.flex > img.w-full
snippet: <img alt="SecAI+ Certification product logo" loading="lazy" width="522" height="462" decoding="async" data-nimg="1" class="w-full h-auto block object-cover aspect-image rounded-corner-8 xl:max-w-[2…" style="color:transparent" srcset="/_next/image/?url=https%3A%2F%2Fimages3.cmp.optimizely.com%2F53a053aec5841…" src="/_next/image/?url=https%3A%2F%2Fimages3.cmp.optimizely.com%2F53a053aec5841…">

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
www.comptia.org/fonts/Inter-VariableFont.ttf14400.0 s448.4 KiB
cdn.optimizely.com/js/26330300728.js120.0 s109.9 KiB

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
home hero block 2 div.ImagePlusTextBlock > div.image-text-block > div.flex > img.w-full
/_next/image/?url=https%3A%2F%2Fimages2.cmp.optimizely.co...106.7 KiB37.1 KiB
SecAI+ Certification product logo div.ImagePlusTextBlock > div.image-text-block > div.flex > img.w-full
/_next/image/?url=https%3A%2F%2Fimages3.cmp.optimizely.co...25.2 KiB17.9 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 SizeDuration
www.comptia.org/_next/static/css/9c18201ed62bdfea.css31.8 KiB300 ms
www.comptia.org/_next/static/css/68bb102d71d167cc.css4.6 KiB

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: 1.6 s
URLTime Spent
comptia.org/796 ms
www.comptia.org/817 ms
www.comptia.org/en-eu0.0 ms
www.comptia.org/en-eu/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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 160 ms 26.2 KiB
URLTransfer SizeEst Savings
www.comptia.org/_next/static/css/9c18201ed62bdfea.css28.4 KiB26.2 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: 320 ms 296.2 KiB
URLTransfer SizeEst Savings
www.comptia.org/metrics/?id=G-Z1ZV6990VN&cx=c&gtm=4e64k0185.5 KiB73.1 KiB
www.comptia.org/metrics/?id=AW-761327116&cx=c&gtm=4e64k0150.8 KiB70.0 KiB
www.comptia.org/metrics/?id=GTM-M647LGC7181.4 KiB67.8 KiB
cdn.optimizely.com/js/26330300728.js109.3 KiB44.0 KiB
www.comptia.org/_next/static/chunks/481-6ed8db471396a010.js44.1 KiB41.3 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.comptia.org/_next/static/chunks/117-8f652c678b855060.js489 ms437 ms18 ms
Unattributable369 ms11 ms0.0 ms
www.comptia.org/metrics/?id=GTM-M647LGC7312 ms255 ms46 ms
www.comptia.org/en-eu/243 ms8.9 ms10 ms
cdn.optimizely.com/js/26330300728.js225 ms185 ms28 ms
www.comptia.org/metrics/?id=G-Z1ZV6990VN&cx=c&gtm=4e64k0220 ms147 ms42 ms
www.comptia.org/_next/static/chunks/3-f9ec505e18393b17.js182 ms179 ms1.6 ms
www.comptia.org/metrics/?id=AW-761327116&cx=c&gtm=4e64k0128 ms95 ms32 ms
www.comptia.org/_next/static/chunks/236-3b8a593d7f01776b.js62 ms56 ms6.2 ms
www.comptia.org/_next/static/chunks/main-app-2dcde4753ea0d175.js60 ms58 ms2.2 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.5 s
Other394 ms
Script Parsing & Compilation246 ms
Style & Layout142 ms
Garbage Collection69 ms
Parse HTML & CSS61 ms
Rendering32 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,632 KiB
●User Timing marks and measures 6 user timings
●Avoid long main-thread tasks 12 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 70 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 40 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
95

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○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
●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
●Background and foreground colors have a sufficient contrast ratio
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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
○ARIA IDs are unique
○No form fields have multiple labels
○`<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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<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
○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.
○`<td>` elements in a large `<table>` have one or more table headers.
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.comptia.org/metrics/?id=G-Z1ZV6990VN&cx=c&gtm=4e64k0 line 415, col 390
Connecting to 'https://region1.google-analytics.com/g/collect?v=2&tid=G-Z1ZV6990VN&gtm=45g92e64k0v885143331z89205670028za20kzb9205670028zd9205670028&_p=1776896817298&gcs=G100&gcd=13p3pPp2p5l1&npa=1&dma_cps=-&dma=1&gdid=dNzQzZD&ecid=791666645&_eu=EAAAAGA&_uip=%3A%3A&are=1&cid=965562991.1776896818&ec_mode=a&frm=0&gtm_up=1&ir=1&pscdl=denied&rcb=13&sr=412x823&uaa=&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=moto%20g%20power%20(2022)&uamb=1&uap=Android&uapv=11.0&uaw=0&ul=en-us&ur=ES&_s=1&tag_exp=0~115616985~115938466~115938469~117266401~117384406~117512542&sid=1776896817&sct=1&seg=0&dl=https%3A%2F%2Fwww.comptia.org%2Fen-eu%2F&dt=Information%20Technology%20(IT)%20Certifications%20%26%20Tech%20Training%20%7C%20CompTIA%20Europe&_tu=CA&en=page_view&_fv=1&_nsi=1&_ss=1&gap.gtb=2&ep.custom_timestamp=2026-04-22T22%3A26%3A57.406%2B00%3A00&tfd=1717' violates the following Content Security Policy directive: "connect-src 'self' ws: wss: https://*.optimizely.com https://cdn.cookielaw.org https://www.google-analytics.com https://www.googletagmanager.com https://cms.comptia.org https://www.comptia.org https://www.google.com.br https://geolocation.onetrust.com https://privacyportal.onetrust.com https://chatapps-us.netomi.com https://*.chatplus.jp https://ak.sail-horizon.com https://d1igp3oop3iho5.cloudfront.net https://js.zi-scripts.com https://api.sail-personalize.com https://px.ads.linkedin.com https://*.wootric.com https://wootric-eligibility.herokuapp.com https://analytics.tiktok.com https://ws.zoominfo.com https://cdn.segment.com https://api.segment.io https://*.hotjar.io https://*.cmp.optimizely.com https://*.google.com https://*.googlesyndication.com https://sso.comptia.org https://*.contentsquare.net https://*.contentsquare.com https://stats.g.doubleclick.net https://analytics-ipv6.tiktokw.us https://api.sail-track.com https://*.zaius.com https://www.facebook.com https://*.sailthru.cloud https://*.googleadservices.com https://googleads.g.doubleclick.net https://ak.sail-horizon.com https://gtm.comptia.org https://*.in.applicationinsights.azure.com https://js.monitor.azure.com". The action has been blocked.
www.comptia.org/metrics/?id=G-Z1ZV6990VN&cx=c&gtm=4e64k0 line 415, col 390
Fetch API cannot load https://region1.google-analytics.com/g/collect?v=2&tid=G-Z1ZV6990VN&gtm=45g92e64k0v885143331z89205670028za20kzb9205670028zd9205670028&_p=1776896817298&gcs=G100&gcd=13p3pPp2p5l1&npa=1&dma_cps=-&dma=1&gdid=dNzQzZD&ecid=791666645&_eu=EAAAAGA&_uip=%3A%3A&are=1&cid=965562991.1776896818&ec_mode=a&frm=0&gtm_up=1&ir=1&pscdl=denied&rcb=13&sr=412x823&uaa=&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=moto%20g%20power%20(2022)&uamb=1&uap=Android&uapv=11.0&uaw=0&ul=en-us&ur=ES&_s=1&tag_exp=0~115616985~115938466~115938469~117266401~117384406~117512542&sid=1776896817&sct=1&seg=0&dl=https%3A%2F%2Fwww.comptia.org%2Fen-eu%2F&dt=Information%20Technology%20(IT)%20Certifications%20%26%20Tech%20Training%20%7C%20CompTIA%20Europe&_tu=CA&en=page_view&_fv=1&_nsi=1&_ss=1&gap.gtb=2&ep.custom_timestamp=2026-04-22T22%3A26%3A57.406%2B00%3A00&tfd=1717. 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

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.comptia.org/metrics/?id=GTM-M647LGC7
www.comptia.org/metrics/?id=G-Z1ZV6990VN&cx=c&gtm=4e64k0
●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
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
92

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.comptia.org/en-eu/resources/case-studies/case-study-college-of-dupage/Learn more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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 are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback