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

82

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.virtualbox.org/graphics/dark-triangles.png1616.0 s461.0 KiB
www.virtualbox.org/graphics/patterned-background.png1616.0 s453.1 KiB
www.virtualbox.org/graphics/vbox-new-logo.png1251.0 s62.2 KiB
www.virtualbox.org/chrome/common/js/jquery.js1250.0 s30.7 KiB
www.virtualbox.org/graphics/community.png1734.0 s21.4 KiB
www.virtualbox.org/graphics/training.png1734.0 s18.2 KiB
www.virtualbox.org/graphics/vboxlogodown.png273.0 s12.3 KiB
www.virtualbox.org/graphics/user-manual.png1734.0 s8.8 KiB
www.virtualbox.org/graphics/user.png309.0 s7.6 KiB
www.virtualbox.org/chrome/common/css/trac.css305.0 s7.3 KiB
www.virtualbox.org/chrome/common/js/jquery-migrate.js1250.0 s5.1 KiB
www.virtualbox.org/chrome/site/style.css682.0 s4.2 KiB
www.virtualbox.org/chrome/common/js/trac.js1250.0 s3.2 KiB
www.virtualbox.org/chrome/common/js/babel.js1786.0 s2.5 KiB
www.virtualbox.org/chrome/common/css/wiki.css1250.0 s2.3 KiB
www.virtualbox.org/chrome/common/trac_logo_mini.png1251.0 s2.0 KiB
www.virtualbox.org/chrome/common/js/search.js1087.0 s1.6 KiB
www.virtualbox.org/chrome/common/js/folding.js1250.0 s1.4 KiB
www.virtualbox.org/chrome/common/js/wiki.js1250.0 s1.3 KiB
www.virtualbox.org/graphics/oracle-logo-new.svg1251.0 s1.1 KiB
www.virtualbox.org/chrome/common/css/code.css1251.0 s1.1 KiB

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.16852] map[node:map[boundingRect:map[bottom:1311 height:1223 left:0 right:1350 top:88 width:1350] lhId:page-6-DIV nodeLabel:Powerful open source virtualization For personal and enterprise use VirtualBo… path:1,HTML,1,BODY,4,DIV,3,DIV,3,DIV,0,DIV,0,DIV selector:div#main > div#content > div.wikipage > div#wikipage snippet:<div id="wikipage" class="trac-content borderless"> type:node] score:0.16852]]

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.

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
Oracle VirtualBox div#ctxtnav > li > a#logo > img
www.virtualbox.org/graphics/vbox-new-logo.png61.9 KiB61.4 KiB
Community icon div.flexboxes_vertical > div#dark_background > a.dark > img
www.virtualbox.org/graphics/community.png21.1 KiB21.0 KiB
Training icon div.flexboxes_vertical > div#dark_background > a.dark > img
www.virtualbox.org/graphics/training.png17.9 KiB17.8 KiB
Documentation icon div.flexboxes_vertical > div#dark_background > a.dark > img
www.virtualbox.org/graphics/user-manual.png8.4 KiB8.4 KiB
User profile icon ul > li.first > a#profile > img
www.virtualbox.org/graphics/user.png7.3 KiB7.2 KiB

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-5-DIV
nodeLabel: Powerful open source virtualization For personal and enterprise use VirtualBo…
path: 1,HTML,1,BODY,4,DIV,3,DIV,3,DIV
selector: body > div#center > div#main > div#content
snippet: <div id="content" class="wiki">

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.

URLTransfer Size
www.virtualbox.org/chrome/common/js/folding.js1.4 KiB
www.virtualbox.org/chrome/common/js/jquery.js30.7 KiB
www.virtualbox.org/chrome/common/js/wiki.js1.3 KiB
www.virtualbox.org/chrome/common/js/jquery-migrate.js5.1 KiB
www.virtualbox.org/chrome/common/js/search.js1.6 KiB
www.virtualbox.org/chrome/common/js/trac.js3.2 KiB
www.virtualbox.org/chrome/common/css/code.css1.1 KiB
www.virtualbox.org/chrome/common/js/babel.js2.5 KiB
www.virtualbox.org/chrome/common/css/wiki.css2.3 KiB
www.virtualbox.org/chrome/site/style.css4.2 KiB
www.virtualbox.org/chrome/common/css/trac.css7.3 KiB

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

Diagnostics

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
Community icon div.flexboxes_vertical > div#dark_background > a.dark > img
www.virtualbox.org/graphics/community.png
Documentation icon div.flexboxes_vertical > div#dark_background > a.dark > img
www.virtualbox.org/graphics/user-manual.png
Training icon div.flexboxes_vertical > div#dark_background > a.dark > img
www.virtualbox.org/graphics/training.png
Oracle VirtualBox div#ctxtnav > li > a#logo > img
www.virtualbox.org/graphics/vbox-new-logo.png
User profile icon ul > li.first > a#profile > img
www.virtualbox.org/graphics/user.png

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

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: 746 ms
URLTime Spent
virtualbox.org/746 ms
www.virtualbox.org/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Powerful open source virtualization For personal and enterprise use VirtualBo… div#main > div#content > div.wikipage > div#wikipage
0.169
●Time to Interactive 1.9 s
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 1,117 KiB
●Minimizes main-thread work 0.1 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 160 ms
●Server Backend Latencies 50 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 290 ms
○INP breakdown
○User Timing marks and measures
○JavaScript execution time
○Avoid long main-thread tasks
○Avoid non-composited animations
68

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
ul > form > div > input#vboxsearch ul > form > div > input#vboxsearch

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul > form > div > input#vboxsearch ul > form > div > input#vboxsearch

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home Download Documentation Community div#center > div#main > div#ctxtnav > ul

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Oracle VirtualBox div#center > div#main > div#ctxtnav > li
Get Started div#opener > div.flexboxes > div.light > li
Community div.flexboxes_vertical > div#dark_background > a.dark > li
Documentation div.flexboxes_vertical > div#dark_background > a.dark > li
Training div.flexboxes_vertical > div#dark_background > a.dark > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●`[accesskey]` values are unique
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<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
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

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.

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.virtualbox.org/wiki/NewsRead 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
●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