Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

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:43.076 source:map[type:text value:[unattributed]]]]

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-DIV

nodeLabel: Skip to search form Skip to main content Skip to account menu Sign In Create Fr…

path: 1,HTML,2,BODY,3,DIV,0,DIV

selector: body > div#app > div.app-page

snippet: <div class="app-page HACK__is-desktop home-page__search_emphasis">

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

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.

URL	Transfer Size	Duration
cdn.semanticscholar.org/bc669961c407e17a/css/main.css	82.1 KiB	381 ms
/css?family=Roboto+Slab:400,500,600,700\|Roboto:300,400,50...	2.5 KiB	269 ms
fast.appcues.com/87350.js	6.2 KiB	202 ms

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.

Request	Cache TTL	Transfer Size
js.hs-analytics.net/analytics/1776798900000/5910970.js	300.0 s	42.3 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.2 KiB
js.hs-banner.com/v2/5910970/banner.js	300.0 s	24.1 KiB
fast.appcues.com/87350.js	120.0 s	6.2 KiB
js.hsadspixel.net/pixels.js	600.0 s	3.9 KiB
js.hs-scripts.com/5910970.js	90.0 s	1.1 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: 388 ms

URL	Time Spent
semanticscholar.org/	388 ms
www.semanticscholar.org/	0.0 ms

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.

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: 80 ms 79.5 KiB

URL	Transfer Size	Est Savings
cdn.semanticscholar.org/bc669961c407e17a/css/main.css	81.7 KiB	79.5 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: 60 ms 1.1 MiB

URL	Transfer Size	Est Savings
cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js	707.6 KiB	396.1 KiB
c09bc9c04079.edge.sdk.awswaf.com/c09bc9c04079/4996efde3854/challenge.js	501.0 KiB	256.6 KiB
www.googletagmanager.com/gtag/js?id=AW-936736651&cx=c&gtm=4e64h1	141.6 KiB	103.1 KiB
/generic/main/7.20.2/appcues.main.6a6a274575024b516c91cfd...	100.5 KiB	72.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-592W6WL	155.2 KiB	70.9 KiB
accounts.google.com/gsi/client	95.6 KiB	68.4 KiB
www.googletagmanager.com/gtag/js?id=G-H7P4ZT52H5	177.0 KiB	64.5 KiB
www.googletagmanager.com/gtag/js?id=AW-936736651	141.6 KiB	53.8 KiB

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 reason	Failure type
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support
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
Back/forward cache is disabled because WebSocket has been used.	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

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,461 KiB

●User Timing marks and measures 12 user timings

●JavaScript execution time 1.1 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 4 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 170 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 170 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

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
Search `form#search-form > div.flex-row-vcenter > div.flex-row-vcenter > button.form-submit`
Blog (opens in a new tab) `div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row`
Ai2 Careers (opens in a new tab) `div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row`
API Documentation (opens in a new tab) `div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row`
Publications (opens in a new tab) `div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row`
Research Careers (opens in a new tab) `div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row`
Resources (opens in a new tab) `div.container > div.about-us__link-group > div.about-us__link-list > a.flex-row`
Terms of Service (opens in a new tab) `div.container > div > div.footer__row > a.tos-link`
Privacy Policy (opens in a new tab) `div.container > div > div.footer__row > a.pp-link`
The Allen Institute for AI (opens in a new tab) `footer.footer > section.page-section > div.container > a.footer-ai2-logo`

○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.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[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

○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.

○Skip links are focusable.

○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.

○`<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.

○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.

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 / Warning	Source
Unload event listeners are deprecated and will be removed.	cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js line 264, col 169460
AttributionReporting	www.googletagmanager.com/gtag/js?id=AW-936736651 line 584, col 244

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.

Source	Description
accounts.google.com/gsi/client line 85, col 88	`[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.`
cdn.semanticscholar.org/bc669961c407e17a/js/BrowserEntry.tsx.js line 120, col 876168	`ERROR s2-client: attempted to use Heap before the global was set`
www.semanticscholar.org/	`Not signed in with the identity provider.`

●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

●No issues in the `Issues` panel in Chrome Devtools

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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 destination	Link Text
www.semanticscholar.org/product/semantic-reader	Learn More
www.semanticscholar.org/about	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`