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.

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.

	URL	Resource Size	Est Savings
IACR ePrint Archive `article.mb-3 > div.row > div.col-auto > img.img-fluid`	iacr.org/img/eprint.png	3.4 MiB	3.4 MiB
Journal of Cryptology `article.mb-3 > div.row > div.col-auto > img.img-fluid`	iacr.org/img/jofc2.png	892.7 KiB	891.2 KiB
eurocrypt `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_eurocrypt.jpg	134.1 KiB	128.7 KiB
tcc `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_tcc.jpg	110.3 KiB	104.9 KiB
asiacrypt `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_asiacrypt.jpg	105.9 KiB	100.5 KiB
ches `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_ches.jpg	105.6 KiB	100.2 KiB
pkc `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_pkc.jpg	83.9 KiB	78.5 KiB
rwc `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_rwc.jpg	82.4 KiB	77.1 KiB
crypto `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_crypto.jpg	65.5 KiB	60.2 KiB
fse `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_fse.jpg	37.2 KiB	34.8 KiB
IACR logo `div.row > div.col-2 > a > img#iacrLogo`	iacr.org/img/logo/iacrlogo_small.png	24.2 KiB	22.8 KiB
Conference Proceedings `article.mb-3 > div.row > div.col-auto > img.img-fluid`	iacr.org/img/lncs2.png	19.8 KiB	18.4 KiB
youtube logo in red (will play video on youtube) `div.youtubeOuter > a > div.youtubeInner > img.youtube-play`	iacr.org/img/icons/youtube-red.png	9.2 KiB	9.0 KiB
youtube logo in black `div.youtubeOuter > a > div.youtubeInner > img.youtube-black`	iacr.org/img/icons/youtube-black.png	7.7 KiB	7.4 KiB

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
iacr.org/libs/css/bootstrap/dist/css/bootstrap.min.css	23.2 KiB	310 ms
iacr.org/libs/js/easy-autocomplete/easy-autocomplete.css	2.0 KiB	350 ms
iacr.org/css/iacr.css	2.6 KiB	350 ms

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

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: 40 ms 21.2 KiB

URL	Transfer Size	Est Savings
iacr.org/libs/css/bootstrap/dist/css/bootstrap.min.css	22.7 KiB	21.2 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
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

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 2.1 KiB

URL	Transfer Size	Est Savings
iacr.org/libs/js/easy-autocomplete/jquery.easy-autocomplete.js	7.3 KiB	2.1 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
iacr.org/img/eprint.png	3.4 MiB
iacr.org/img/jofc2.png	893.6 KiB
iacr.org/conf/generic_eurocrypt.jpg	134.7 KiB
iacr.org/conf/generic_tcc.jpg	110.8 KiB
iacr.org/conf/generic_asiacrypt.jpg	106.4 KiB
iacr.org/conf/generic_ches.jpg	106.2 KiB
iacr.org/conf/generic_pkc.jpg	84.4 KiB
iacr.org/conf/generic_rwc.jpg	82.9 KiB
iacr.org/conf/generic_crypto.jpg	66.1 KiB
iacr.org/conf/generic_fse.jpg	37.7 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
IACR ePrint Archive `article.mb-3 > div.row > div.col-auto > img.img-fluid`	iacr.org/img/eprint.png
Open Access Journals `article.mb-3 > div.row > div.col-auto > img.img-fluid`	iacr.org/img/open_access.svg
eurocrypt `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_eurocrypt.jpg
asiacrypt `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_asiacrypt.jpg
fse `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_fse.jpg
pkc `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_pkc.jpg
ches `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_ches.jpg
tcc `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_tcc.jpg
rwc `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_rwc.jpg
Journal of Cryptology `article.mb-3 > div.row > div.col-auto > img.img-fluid`	iacr.org/img/jofc2.png
crypto `div.row > div.col-12 > a > img.img-fluid`	iacr.org/conf/generic_crypto.jpg
Screenshot of featured video `article.col-12 > div.youtubeOuter > a > img.mb-3`	iacr.org/cryptodb/youtube/Verbauwhede.jpg
Conference Proceedings `article.mb-3 > div.row > div.col-auto > img.img-fluid`	iacr.org/img/lncs2.png
Search Button `li.nav-item > a#searchLink > button.btn > img.searchIcon`	iacr.org/img/icons/search.svg
Announcement icon `article.mb-3 > div.row > div.col-1 > img.newsicon`	iacr.org/img/icons/news/channel_1.svg
PKC icon `article.mb-3 > div.row > div.col-1 > img.newsicon`	iacr.org/img/icons/news/channel_8.svg
ePrint Report icon `article.mb-3 > div.row > div.col-1 > img.newsicon`	iacr.org/img/icons/news/channel_10.svg
ePrint Report icon `article.mb-3 > div.row > div.col-1 > img.newsicon`	iacr.org/img/icons/news/channel_10.svg
ePrint Report icon `article.mb-3 > div.row > div.col-1 > img.newsicon`	iacr.org/img/icons/news/channel_10.svg
ePrint Report icon `article.mb-3 > div.row > div.col-1 > img.newsicon`	iacr.org/img/icons/news/channel_10.svg
ePrint Report icon `article.mb-3 > div.row > div.col-1 > img.newsicon`	iacr.org/img/icons/news/channel_10.svg
ePrint Report icon `article.mb-3 > div.row > div.col-1 > img.newsicon`	iacr.org/img/icons/news/channel_10.svg
Twitter logo `div.col-12 > div.text-center > a.social > img.socialBtn`	iacr.org/img/icons/twitter.svg
YouTube logo `div.col-12 > div.text-center > a.social > img.socialBtn`	iacr.org/img/icons/youtube.svg
new `div.row > div.col > p > img`	iacr.org/images/new_tiny.gif

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

●Time to Interactive 1.5 s

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Reduce unused JavaScript

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.3 s

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 230 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Eurocrypt 2026 `article.col-12 > div.row > div.col > h5.mt-2`

These are opportunities to improve keyboard navigation in your application.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CC BY 3.0 `div.row > div.col-12 > p.attribution > a`
via Wikimedia Commons `div.row > div.col-12 > p.attribution > a`
pxhere.com `div.row > div.col-12 > p.attribution > a`
Compact Lattice Signatures via Iterative Rejection Sampling `section.row > article.col-12 > p > a`

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
Access to Publications `div.col-12 > ul.list-unstyled > li > a`
Journal of Cryptology `div.col-12 > ul.list-unstyled > li > a`
News `div.col-12 > ul.list-unstyled > li > a`
Awards `div.col-12 > ul.list-unstyled > li > a`
Jobs `div.col-12 > ul.list-unstyled > li > a`

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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

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

○Elements with visible text labels have matching accessible names.

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

100

Best Practices

●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

●No browser errors logged to the console

●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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●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`