Skip to content
https://genome.gov

Lighthouse Mobile

· 0 checks — Mobile 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.

41

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.

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:122.024 source:map[column:13 line:255 type:source-location url:https://www.genome.gov/sites/default/files/js/js_xi0FtGdjW2Z6VR7E4ps29cMkIygxI-vuQpt3k_8ypz4.js?scope=footer&delta=0&language=en&theme=nhgri&include=eJxljkEOgzAMBD8UmidZBkwwcmwUJ1B4fZEKl_a2O1qtBt2pAutCQ7USF3-tzWcYTCtphZ5EbAeeoEelEvBvXimvMPEbFLcwFDwPSik-ISSzJASoKEflweMvCJzXYhuNkJtUBie5viNnDzqnwnG6VHAnt0wPaSLdiok6Fx4vqy9OYj3KXRTVEopQOW5yttJ3kzUdsbLpB2MdYl8 urlProvider:network]]]

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: section#face > div#slider > div.slide > div.slide-bg
path: 1,HTML,1,BODY,2,DIV,0,DIV,2,MAIN,2,DIV,1,DIV,0,ARTICLE,0,DIV,0,SECTION,1,DIV,0,DIV,0,DIV
selector: section#face > div#slider > div.slide > div.slide-bg
snippet: <div class="slide-bg slide-bg-0" fetchpriority="high" data-lazy="">

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
HGP mosaic div.wrapper > div.tab > div.box > div.img
/sites/default/files/media/images/2023-08/hgp_specialty_f...104.8 KiB80.8 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: 777 ms
URLTime Spent
genome.gov/777 ms
www.genome.gov/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

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.

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: 630 ms 75.4 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_S9fxr0VKT9XswDa4m5Lk9YATdxRc...81.4 KiB75.4 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.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.3 s
Style & Layout692 ms
Other608 ms
Script Parsing & Compilation542 ms
Parse HTML & CSS136 ms
Rendering58 ms
Garbage Collection49 ms

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 38.1 KiB
URLTransfer SizeEst Savings
code.jquery.com/ui/1.12.1/jquery-ui.js105.6 KiB38.1 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
NHGRI Logo div.eye > a > div.logo > img#nhgri-logo
www.genome.gov/themes/custom/nhgri/assets/global/logo-light-nhgri.webp

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
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 14 user timings
Avoid long main-thread tasks 18 long tasks found
Avoid non-composited animations 1 animated element found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 70 ms
INP breakdown
Avoid large layout shifts
92

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.

ARIA

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ABOUT GENOMICS div.menu-container > ul.menu-items > a.title-link > div.menu-title
RESEARCH FUNDING div.menu-container > ul.menu-items > a.title-link > div.menu-title
RESEARCH AT NHGRI div.menu-container > ul.menu-items > a.title-link > div.menu-title
ABOUT HEALTH div.menu-container > ul.menu-items > a.title-link > div.menu-title
CAREERS & TRAINING div.menu-container > ul.menu-items > a.title-link > div.menu-title
NEWS & EVENTS div.menu-container > ul.menu-items > a.title-link > div.menu-title
ABOUT NHGRI div.menu-container > ul.menu-items > a.title-link > div.menu-title

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

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
INTRODUCTION TO GENOMICS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
EDUCATIONAL RESOURCES div#about-genome > div.menu-container > ul.menu-items > li.menu-item
POLICY ISSUES IN GENOMICS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
THE HUMAN GENOME PROJECT div#about-genome > div.menu-container > ul.menu-items > li.menu-item
HISTORY OF GENOMICS PROGRAM div#about-genome > div.menu-container > ul.menu-items > li.menu-item
FUNDING OPPORTUNITIES div#about-genome > div.menu-container > ul.menu-items > li.menu-item
FUNDED PROGRAMS & PROJECTS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
DIVISION AND PROGRAM DIRECTORS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
SCIENTIFIC PROGRAM ANALYSTS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
CONTACTS BY RESEARCH AREA div#about-genome > div.menu-container > ul.menu-items > li.menu-item
NEWS & EVENTS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
RESEARCH AREAS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
RESEARCH INVESTIGATORS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
STAFF CLINICIANS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
RESEARCH PROJECTS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
CLINICAL RESEARCH div#about-genome > div.menu-container > ul.menu-items > li.menu-item
DATA TOOLS & RESOURCES div#about-genome > div.menu-container > ul.menu-items > li.menu-item
NEWS & EVENTS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
GENOMICS & MEDICINE div#about-genome > div.menu-container > ul.menu-items > li.menu-item
FAMILY HEALTH HISTORY div#about-genome > div.menu-container > ul.menu-items > li.menu-item
FOR PATIENTS & FAMILIES div#about-genome > div.menu-container > ul.menu-items > li.menu-item
FOR HEALTH PROFESSIONALS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
JOBS AT NHGRI div#about-genome > div.menu-container > ul.menu-items > li.menu-item
TRAINING AT NHGRI div#about-genome > div.menu-container > ul.menu-items > li.menu-item
FUNDING FOR RESEARCH TRAINING div#about-genome > div.menu-container > ul.menu-items > li.menu-item
PROFESSIONAL DEVELOPMENT PROGRAMS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
NHGRI CULTURE div#about-genome > div.menu-container > ul.menu-items > li.menu-item
NEWS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
EVENTS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
SOCIAL MEDIA div#about-genome > div.menu-container > ul.menu-items > li.menu-item
BROADCAST MEDIA div#about-genome > div.menu-container > ul.menu-items > li.menu-item
IMAGE GALLERY div#about-genome > div.menu-container > ul.menu-items > li.menu-item
VIDEOS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
PRESS RESOURCES div#about-genome > div.menu-container > ul.menu-items > li.menu-item
ORGANIZATION div#about-genome > div.menu-container > ul.menu-items > li.menu-item
MISSION AND VISION div#about-genome > div.menu-container > ul.menu-items > li.menu-item
POLICIES AND GUIDANCE div#about-genome > div.menu-container > ul.menu-items > li.menu-item
BUDGET div#about-genome > div.menu-container > ul.menu-items > li.menu-item
INSTITUTE ADVISORS div#about-genome > div.menu-container > ul.menu-items > li.menu-item
STRATEGIC VISION div#about-genome > div.menu-container > ul.menu-items > li.menu-item
PARTNER WITH NHGRI div#about-genome > div.menu-container > ul.menu-items > li.menu-item
STAFF SEARCH div#about-genome > div.menu-container > ul.menu-items > li.menu-item
CONTACT US div#about-genome > div.menu-container > ul.menu-items > li.menu-item

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

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>`
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
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.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
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>`).
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
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`[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 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.
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.
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.
100

Best Practices

General

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 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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
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