Skip to content
https://www.julialang.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.

98

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
www.julialang.org/assets/infra/waves.webp600.0 s823.0 KiB
www.julialang.org/assets/infra/world_map.webp600.0 s368.0 KiB
i.ytimg.com/vi/QSRw7QofNwg/maxresdefault.jpg7200.0 s138.5 KiB
cdn.jsdelivr.net/gh/cormullion/juliamono-webfonts/JuliaMono-Bold.woff2604800.0 s998.0 KiB
cdn.jsdelivr.net/gh/cormullion/juliamono-webfonts/JuliaMono-Regular.woff2604800.0 s997.1 KiB
i.ytimg.com/vi/wPFPT-Ech2c/maxresdefault.jpg7200.0 s100.4 KiB
www.julialang.org/libs/bootstrap/bootstrap.min.css600.0 s31.3 KiB
www.julialang.org/libs/bootstrap/bootstrap.bundle.min.js600.0 s23.8 KiB
www.julialang.org/libs/highlight/highlight.min.js600.0 s17.4 KiB
www.julialang.org/assets/infra/backsplash-min-0.5.svg600.0 s14.4 KiB
www.julialang.org/assets/infra/zed.png600.0 s13.8 KiB
www.julialang.org/assets/infra/linkedin.png600.0 s13.8 KiB
www.julialang.org/assets/infra/vscode.png600.0 s13.6 KiB
www.julialang.org/assets/infra/vim.png600.0 s12.6 KiB
www.julialang.org/assets/infra/emacs.png600.0 s11.4 KiB
www.julialang.org/css/app.css600.0 s8.1 KiB
www.julialang.org/libs/buttons.js600.0 s6.8 KiB
www.julialang.org/assets/infra/slack.png600.0 s5.1 KiB
www.julialang.org/assets/infra/logo.svg600.0 s2.5 KiB
www.julialang.org/assets/infra/juliacon_logo.svg600.0 s2.1 KiB
www.julialang.org/css/franklin.css600.0 s1.7 KiB
www.julialang.org/assets/infra/jupyter.svg600.0 s1.6 KiB
www.julialang.org/libs/detectdark.js600.0 s1.2 KiB
www.julialang.org/assets/infra/flexibleJulia.svg600.0 s1.1 KiB
www.julialang.org/assets/infra/zulip.svg600.0 s1.0 KiB
www.julialang.org/libs/carousel.js600.0 s1008 B
www.julialang.org/libs/youtube-player.js600.0 s877 B
www.julialang.org/assets/infra/github.svg600.0 s701 B
www.julialang.org/css/juliamono.css600.0 s681 B
www.julialang.org/assets/infra/discourse.svg600.0 s638 B
www.julialang.org/assets/infra/pluto_jl.svg600.0 s627 B
www.julialang.org/libs/highlight/github.min.css600.0 s604 B
www.julialang.org/assets/infra/youtube.svg600.0 s515 B
static.doubleclick.net/instream/ad_status.js900.0 s495 B
www.julialang.org/assets/infra/twitter.svg600.0 s419 B

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
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff240 ms

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
Visualization of waves in 3D, as a heatmap, and on the x y axis div.row > div.col-lg-12 > div.container > img.pb-2
www.julialang.org/assets/infra/waves.webp822.2 KiB804.8 KiB
body > div#juliacon-videos > picture.juliacon-world-map > img body > div#juliacon-videos > picture.juliacon-world-map > img
www.julialang.org/assets/infra/world_map.webp367.5 KiB306.6 KiB
LinkedIn Logo div.row > div.col-lg-3 > a.ide-tile > img
www.julialang.org/assets/infra/linkedin.png13.6 KiB13.4 KiB
Zed Logo div.row > div.col-lg-3 > a.ide-tile > img
www.julialang.org/assets/infra/zed.png13.6 KiB12.5 KiB
VSCode Logo div.row > div.col-lg-3 > a.ide-tile > img
www.julialang.org/assets/infra/vscode.png13.3 KiB12.1 KiB
Vim Logo div.row > div.col-lg-3 > a.ide-tile > img
www.julialang.org/assets/infra/vim.png12.2 KiB11.1 KiB
Emacs Logo div.row > div.col-lg-3 > a.ide-tile > img
www.julialang.org/assets/infra/emacs.png11.1 KiB9.9 KiB
Slack Logo div.row > div.col-lg-3 > a.ide-tile > img
www.julialang.org/assets/infra/slack.png4.9 KiB4.2 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
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.

URLTransfer SizeDuration
www.julialang.org/libs/detectdark.js1.2 KiB
www.julialang.org/css/franklin.css1.7 KiB
www.julialang.org/css/app.css8.1 KiB
www.julialang.org/libs/bootstrap/bootstrap.min.css31.3 KiB96 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: 0.0 ms 28.8 KiB
URLTransfer SizeEst Savings
www.julialang.org/libs/bootstrap/bootstrap.min.css31.1 KiB28.8 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.

URLTransfer Size
cdn.jsdelivr.net/gh/cormullion/juliamono-webfonts/JuliaMono-Bold.woff2998.0 KiB
cdn.jsdelivr.net/gh/cormullion/juliamono-webfonts/JuliaMono-Regular.woff2997.1 KiB
www.julialang.org/assets/infra/waves.webp823.0 KiB
www.youtube.com/s/player/57fefa84/player_embed_es6.vflset/en_US/base.js433.2 KiB
www.julialang.org/assets/infra/world_map.webp368.0 KiB
/s/_/ytembeds/_/js/k=ytembeds.base.en_US.I-saIP3mOa8.2021...329.1 KiB
i.ytimg.com/vi/QSRw7QofNwg/maxresdefault.jpg138.5 KiB
i.ytimg.com/vi/wPFPT-Ech2c/maxresdefault.jpg100.4 KiB
/embed/?list=PLP8iPy9hna6SZOq4EH_nE_BFulBAKXkf1&listType=...73.9 KiB
www.youtube.com/s/player/57fefa84/www-player.css57.0 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
JuliaCon div#top-alert > div.alert > p.text-center > img.juliacon-logo
www.julialang.org/assets/infra/juliacon_logo.svg
Visualization of waves in 3D, as a heatmap, and on the x y axis div.row > div.col-lg-12 > div.container > img.pb-2
www.julialang.org/assets/infra/waves.webp

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Forced reflow
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Time to Interactive 1.2 s
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused JavaScript
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.5 s
●Avoid long main-thread tasks 1 long task found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 120 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 0 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
91

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
JuliaCon Global 2026 div.alert > p.text-center > span.alert-text > a
juliacon.org/2026 div.alert > p.text-center > span.alert-text > a
Watch JuliaCon 2025 ↓ div.alert > p.text-center > span.alert-text > a.watch-videos-link

These are opportunities to improve the legibility of your content.

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
Fast div.container > div.row > div.col-lg-4 > h3
Data Visualization and Plotting div.row > div.col-lg-12 > div.container > h4

These are opportunities to improve keyboard navigation in your application.

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
Go to slide 1 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 2 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 3 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 4 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 5 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 6 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 7 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 8 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 9 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 10 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 11 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 12 body > div.container > div.carousel-dots > button.carousel-dot
Go to slide 13 body > div.container > div.carousel-dots > button.carousel-dot
Governance div.row > ul > li > a
Publications div.row > ul > li > a
Stewards div.row > ul > li > a
Diversity div.row > ul > li > a
JuliaCon div.row > ul > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●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
●`[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.
●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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●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 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
○`<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.
○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.
96

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
kit.fontawesome.com/f030d443fe.js
Failed to load resource: the server responded with a status of 403 ()
●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 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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○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