Skip to content
https://collegeboard.org

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.

67

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.

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
kiwi.collegeboard.org/embed.js0.0 ms211.9 KiB
/2blxFu2OYUH5/-opIpNMIkZ/wg/YrzaLGQGX4fNNz/ITk8VCBifQU/Dx...21600.0 s197.5 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/main.min.js3600.0 s149.3 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/main.min.css3600.0 s99.2 KiB
athena.collegeboard.org/2.2.4/cbw-widgets.min.js3600.0 s80.7 KiB
atlas.collegeboard.org/apricot/prod/4.6.1/fonts/org-icons.woff3600.0 s67.5 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/fonts/Roboto-Medium.woff23600.0 s65.7 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/fonts/Roboto-Black.woff23600.0 s65.0 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/fonts/Roboto-Bold.woff23600.0 s64.9 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/fonts/Roboto-Regular.woff23600.0 s64.8 KiB
atlas.collegeboard.org/apricot/prod/4.8.0/fonts/Roboto-Regular.woff23600.0 s64.8 KiB
atlas.collegeboard.org/apricot/prod/4.8.0/fonts/Roboto-Light.woff23600.0 s64.4 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/fonts/Roboto-Light.woff23600.0 s64.4 KiB
cdn.cookielaw.org/scripttemplates/202509.1.0/otBannerSdk.js86400.0 s121.6 KiB
/modules/site/cb_org_homepage/assets/CB_BigFuture_College...853881.0 s423.4 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/fonts/cb-icons-logo-4_11_5.woff3600.0 s39.2 KiB
atlas.collegeboard.org/apricot/prod/4.8.0/fonts/cbw-icons-logo_4_8_0.woff3600.0 s35.7 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/fonts/cb-icons-a-4_11_5.woff3600.0 s32.8 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/dx_profile.css3600.0 s31.2 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/dx_profile.js3600.0 s17.3 KiB
/logos/65a38c3f-4f1f-4acc-9e16-9a9cd7f86053/0197c2b3-d022...86400.0 s19.5 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/assets/apple-touch-icon.png3600.0 s8.0 KiB
/media/js/js_iVjiK8VqT9Zh3SDpA36V2PzUlkitrd3JUa6lhq4UXhc....1450946.0 s63.5 KiB
atlas.collegeboard.org/apricot/prod/4.8.0/fonts/cbw-icons.woff3600.0 s5.9 KiB
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/hostedL...0.0 ms4.6 KiB
atlas.collegeboard.org/apricot/prod/4.8.0/widgets.css3600.0 s5.1 KiB
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RCbb140...0.0 ms4.1 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/illustrations.css3600.0 s4.8 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
atlas.collegeboard.org/apricot/prod/4.6.1/fonts/cb-bf-icons-logo.woff3600.0 s3.4 KiB
www.collegeboard.org/core/assets/vendor/jquery/jquery.min.js?v=4.0.01450567.0 s27.3 KiB
atlas.collegeboard.org/apricot/prod/4.6.1/org.css3600.0 s2.1 KiB
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RCb3bb6...0.0 ms1.5 KiB
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RCf980b...0.0 ms1.2 KiB
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RC0811f...0.0 ms1.2 KiB
/media/js/js_GyLA1v6kTpmuPtuwS9SeESY4KmpiVMng5x_wcK_T2Cg....1450568.0 s11.3 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.5 KiB
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RC07242...0.0 ms982 B
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RC647ee...0.0 ms964 B
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RC78be3...0.0 ms942 B
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RC83814...0.0 ms922 B
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RCc9fd1...0.0 ms921 B
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RC9aacf...0.0 ms855 B
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RC2b787...0.0 ms840 B
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RC0cf24...0.0 ms770 B
/cb-global/f740f8a20d94/74f95571d83d/05b39968bd52/RCabc58...0.0 ms745 B
atlas.collegeboard.org/apricot/prod/4.11.5/athena.min.css3600.0 s662 B
/media/js/js_SOOmDLnx9nLdCrFq6bt-TnICjHSzGhKnHF_YRyJpmJU....1450567.0 s4.9 KiB
/media/css/css_84Q_Bvqp4kph3ke5zhznAWIhaQw6X0dG2K2KvGrQnm...1450568.0 s4.5 KiB
/media/css/css_9BjPb83R99UzOkU40D-xAijyvHpTotg1pk45f4ON3K...1450567.0 s2.9 KiB
/media/css/css_4YpRBZVGMebHc-u5mlNjCM-Y4gM8gBsbqyNDc7VPJR...1450567.0 s2.8 KiB
/media/js/js_7xVIs9b28Jc2EyjmlhfX5taWtTRC8U5mCyz4wBIuaEA....1450567.0 s2.5 KiB
/media/js/js_Hvvgl5psum_HkH4genORwaU5Ll6_xojmu8VvXOgXpKI....1450568.0 s640 B

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:35.695 source:map[type:text value:[unattributed]]]]

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

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.

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
Find the right college for you div#block-cborghomepage > div.cb-org > div.block > div#college-search-block
/modules/site/cb_org_homepage/assets/CB_BigFuture_College...422.9 KiB305.7 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: 672 ms
URLTime Spent
collegeboard.org/672 ms
www.collegeboard.org/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: 110 ms 152.3 KiB
URLTransfer SizeEst Savings
atlas.collegeboard.org/apricot/prod/4.11.5/main.min.css98.8 KiB98.8 KiB
atlas.collegeboard.org/apricot/prod/4.11.5/dx_profile.css30.8 KiB30.4 KiB
27.0 KiB23.1 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.

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
The page has an unload handler in the main frame.Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.9 KiB
URLTransfer SizeEst Savings
atlas.collegeboard.org/apricot/prod/4.11.5/dx_profile.css31.2 KiB4.7 KiB
27.0 KiB2.2 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.2 KiB
URLTransfer SizeEst Savings
atlas.collegeboard.org/apricot/prod/4.11.5/dx_profile.js16.9 KiB6.2 KiB

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

●Max Potential First Input Delay 90 ms
●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 2,530 KiB
●JavaScript execution time 0.5 s
●Minimizes main-thread work 1.1 s
●Avoid long main-thread tasks 4 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 150 ms
●Server Backend Latencies 100 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
●Avoid large layout shifts 11 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Statement div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 are distinguishable without relying on color.
●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
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
73

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

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
Creating a worker from 'blob:https://www.collegeboard.org/ee0d3194-7997-4389-a8c6-54b4bb52a493' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' *.collegeboard.org cdnjs.cloudflare.com sdk.amazonaws.com cdn.cookielaw.org www.googletagmanager.com googleads.g.doubleclick.net www.googleadservices.com connect.facebook.net www.youtube.com *.salesforceliveagent.com service.force.com ajax.cloudflare.com js-agent.newrelic.com bam.nr-data.net d10lpsik1i8c69.cloudfront.net s3.amazonaws.com/cdn.aimtell.com/ www.google.com static.lightning.force.com *.my.salesforce.com *.my.salesforce-sites.com apform.secure.force.com www.pagespeed-mod.com cdn.ckeditor.com cdnjs.cloudflare.com/ajax/libs/cropper/4.0.0/cropper.min.js assets.calendly.com platform.twitter.com *.appcues.com cb-zscaler-pages.s3.amazonaws.com www.buzzsprout.com cdn.jsdelivr.net/npm/js-cookie@3.0.5/dist/js.cookie.min.js collegeboard--full.sandbox.my.site.com collegeboard.my.site.com cdn.aimtell.com client.rum.us-east-1.amazonaws.com/1.0.2/cwr.js cdn.jsdelivr.net/npm/@fingerprintjs/fingerprintjs@3.3.2/dist/fp.js pagead2.googlesyndication.com blue.mbsy.co https://athena.collegeboard.org/2.2.4/cbw-widgets.min.js https://atlas.collegeboard.org/apricot/prod/4.11.5/dx_profile.js https://atlas.collegeboard.org/apricot/prod/4.11.5/main.min.js https://bigfuture.collegeboard.org/widgets/v2/CollegeSearchAndSaveTypeahead.js https://cdn.jsdelivr.net/npm/html2canvas@1.3.2/dist/html2canvas.min.js https://cdn.jsdelivr.net/npm/js-cookie@3.0.5/dist/js.cookie.min.js https://cdnjs.cloudflare.com/ajax/libs/cropper/4.0.0/cropper.min.js https://cdnjs.cloudflare.com/ajax/libs/mathjax/3.2.2/es5/tex-mml-chtml.js https://github.com/mattfarina/farbtastic/blob/master/src/farbtastic.js". Note that 'worker-src' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.

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.

●Uses HTTPS
●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
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
83

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
privacy.collegeboard.org/cookie-notice?kiwi-ccbMore information

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Manage Cookies div.cbw-footer-wrapper > ul.cbw-col-xs-12 > li > a#ot-sdk-btn

To appear in search results, crawlers need access to your app.

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

Send Feedback