Lighthouse Mobile

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

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
knightlab.northwestern.edu/assets/people/amyjo-brown.jpg	0.0 ms	502.6 KiB
/assets/posts/jr3-workshop-recap/hero-purpose-of-journali...	0.0 ms	349.5 KiB
knightlab.northwestern.edu/assets/front-page-image.jpg	0.0 ms	239.3 KiB
knightlab.northwestern.edu/assets/devicelab_wide.jpg	0.0 ms	186.5 KiB
knightlab.northwestern.edu/assets/posts/storymap-frontpage.jpeg	0.0 ms	155.9 KiB
knightlab.northwestern.edu/assets/research.jpg	0.0 ms	151.4 KiB
knightlab.northwestern.edu/assets/students.jpg	0.0 ms	127.1 KiB
knightlab.northwestern.edu/assets/class.jpg	0.0 ms	125.6 KiB
knightlab.northwestern.edu/assets/devicelab_phones.jpg	0.0 ms	103.8 KiB
knightlab.northwestern.edu/assets/local_news_bg.jpg	0.0 ms	100.2 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/screenshot-juxtapose.jpg	14400.0 s	145.6 KiB
knightlab.northwestern.edu/assets/about-the-lab.jpg	0.0 ms	95.1 KiB
studio.knightlab.com/assets/projects/live-streaming-twitter-spaces.png	14400.0 s	126.7 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/screenshot-soundcite.png	14400.0 s	125.5 KiB
knightlab.northwestern.edu/assets/open_lab_students.jpg	0.0 ms	82.4 KiB
knightlab.northwestern.edu/assets/studio_people_03.jpg	0.0 ms	55.4 KiB
media.knightlab.com/scenevr/screenshot-scenevr.jpg	14400.0 s	78.0 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/screenshot-storymap.png	14400.0 s	77.8 KiB
/projects/5433/7ae_vdef_emp_6b6c.woff2?a39a9c83c035d53f6a...	600.0 s	57.5 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/screenshot-timeline.png	14400.0 s	67.6 KiB
storyline.knightlab.com/screenshot-storyline.png	14400.0 s	60.9 KiB
/projects/5433/691_vdef_emp_6b77.woff2?a39a9c83c035d53f6a...	600.0 s	36.2 KiB
studio.knightlab.com/assets/projects/high-school-journalism.png	14400.0 s	48.1 KiB
studio.knightlab.com/assets/projects/gif-story.png	14400.0 s	30.3 KiB
knightlab.northwestern.edu/assets/logo-knightlab-stacked-dark.png	0.0 ms	14.7 KiB
cdn.knightlab.com/libs/orangeline/latest/css/orangeline.min.css	14400.0 s	20.7 KiB
cdn.knightlab.com/libs/orangeline/latest/js/orangeline.js	14400.0 s	17.8 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/fonts/icons.ttf?at2s0a	14400.0 s	15.8 KiB
/libs/orangeline/latest/assets/logo-knightlab-stacked-dar...	14400.0 s	15.5 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/fonts/ApresRERegular/font.woff2	14400.0 s	14.6 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/logo-mccormick-dark.png	14400.0 s	9.0 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/logo-medill-dark.png	14400.0 s	5.2 KiB
cloud.typenetwork.com/projects/5433/fontface.css	600.0 s	2.9 KiB
knightlab.northwestern.edu/assets/style.css	0.0 ms	639 B

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.

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.

URL	Est Savings
cdn.knightlab.com/libs/orangeline/latest/assets/fonts/icons.ttf?at2s0a	260 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.

	URL	Resource Size	Est Savings
div.card > a > header.header-image > div.header-image-background `div.card > a > header.header-image > div.header-image-background`	cdn.knightlab.com/libs/orangeline/latest/assets/screenshot-juxtapose.jpg	145.0 KiB	86.4 KiB
div.card > a > header.header-image > div.header-image-background `div.card > a > header.header-image > div.header-image-background`	studio.knightlab.com/assets/projects/live-streaming-twitter-spaces.png	126.1 KiB	56.9 KiB
body > header.header-image > div.header-image-background `body > header.header-image > div.header-image-background`	knightlab.northwestern.edu/assets/front-page-image.jpg	238.9 KiB	46.3 KiB
div.card > a > header.header-image > div.header-image-background `div.card > a > header.header-image > div.header-image-background`	/assets/posts/jr3-workshop-recap/hero-purpose-of-journali...	349.0 KiB	40.3 KiB
div.card > a > header.header-image > div.header-image-background `div.card > a > header.header-image > div.header-image-background`	media.knightlab.com/scenevr/screenshot-scenevr.jpg	77.4 KiB	29.9 KiB
body > article#page-body > section#community > div.section-image-background `body > article#page-body > section#community > div.section-image-background`	knightlab.northwestern.edu/assets/students.jpg	126.9 KiB	21.4 KiB
body > article#page-body > section#studio > div.section-image-background `body > article#page-body > section#studio > div.section-image-background`	knightlab.northwestern.edu/assets/class.jpg	125.3 KiB	16.8 KiB
body > header.header-image > div.header-image-content > img.logo `body > header.header-image > div.header-image-content > img.logo`	knightlab.northwestern.edu/assets/logo-knightlab-stacked-dark.png	14.5 KiB	6.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-2-DIV

nodeLabel: body > header.header-image > div.header-image-background

path: 1,HTML,1,BODY,1,HEADER,0,DIV

selector: body > header.header-image > div.header-image-background

snippet: <div class="header-image-background bw" style="background-image: url(/assets/front-page-image.jpg);">

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.

URL	Transfer Size	Duration
knightlab.northwestern.edu/assets/style.css	639 B
cdn.knightlab.com/libs/orangeline/latest/css/orangeline.min.css	20.7 KiB	986 ms
cloud.typenetwork.com/projects/5433/fontface.css	2.9 KiB	751 ms

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: 1.0 s

URL	Time Spent
knightlab.com/	1.0 s
knightlab.northwestern.edu/	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

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: 250 ms 16.2 KiB

URL	Transfer Size	Est Savings
cdn.knightlab.com/libs/orangeline/latest/css/orangeline.min.css	20.0 KiB	16.2 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: 490 ms 63.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-8F4WPDMPL5	146.1 KiB	63.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
knightlab.northwestern.edu/assets/people/amyjo-brown.jpg	502.6 KiB
/assets/posts/jr3-workshop-recap/hero-purpose-of-journali...	349.5 KiB
knightlab.northwestern.edu/assets/front-page-image.jpg	239.3 KiB
knightlab.northwestern.edu/assets/devicelab_wide.jpg	186.5 KiB
knightlab.northwestern.edu/assets/posts/storymap-frontpage.jpeg	155.9 KiB
knightlab.northwestern.edu/assets/research.jpg	151.4 KiB
www.googletagmanager.com/gtag/js?id=G-8F4WPDMPL5	146.4 KiB
cdn.knightlab.com/libs/orangeline/latest/assets/screenshot-juxtapose.jpg	145.6 KiB
knightlab.northwestern.edu/assets/students.jpg	127.1 KiB
studio.knightlab.com/assets/projects/live-streaming-twitter-spaces.png	126.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
body > header.header-image > div.header-image-content > img.logo `body > header.header-image > div.header-image-content > img.logo`	knightlab.northwestern.edu/assets/logo-knightlab-stacked-dark.png
div.grid > div.column-2 > a > img `div.grid > div.column-2 > a > img`	/libs/orangeline/latest/assets/logo-knightlab-stacked-dar...
div.grid-size-2 > div.grid-item > a > img `div.grid-size-2 > div.grid-item > a > img`	cdn.knightlab.com/libs/orangeline/latest/assets/logo-mccormick-dark.png
div.grid-size-2 > div.grid-item > a > img `div.grid-size-2 > div.grid-item > a > img`	cdn.knightlab.com/libs/orangeline/latest/assets/logo-medill-dark.png

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 3 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > nav#navbar-product-top > div.nav-mobile-menu > button.button-plain `body > nav#navbar-product-top > div.nav-mobile-menu > button.button-plain`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > header.header-image > div.header-image-content > img.logo `body > header.header-image > div.header-image-content > img.logo`
div.grid > div.column-2 > a > img `div.grid > div.column-2 > a > img`
div.grid-size-2 > div.grid-item > a > img `div.grid-size-2 > div.grid-item > a > img`
div.grid-size-2 > div.grid-item > a > img `div.grid-size-2 > div.grid-item > a > img`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.column-10 > div.cards > div.card > a `div.column-10 > div.cards > div.card > a`
div.column-10 > div.cards > div.card > a `div.column-10 > div.cards > div.card > a`
div.column-10 > div.cards > div.card > a `div.column-10 > div.cards > div.card > a`
div.container > div.grid > div.column-2 > a `div.container > div.grid > div.column-2 > a`

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.

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
Latest updates about our work, observations and experimentation in the Knight L… `div.container > div.grid > div.column-10 > p.dek`
LAB `div.card > article > p.dateline > a`
PROJECTS `div.card > article > p.dateline > a`
JUL 21, 2025 `div.card > article > p.dateline > time`
LAB `div.card > article > p.dateline > a`
PROJECTS `div.card > article > p.dateline > a`
OCT 6, 2023 `div.card > article > p.dateline > time`
by JOE GERMUSKA `div.cards > div.card > article > p.byline`
PEOPLE `div.card > article > p.dateline > a`
JAN 31, 2023 `div.card > article > p.dateline > time`
We build easy-to-use tools that can help you tell better stories. `div.container > div.grid > div.column-10 > p.lead`
Easy-to-make frame comparisons. `div.card > a > article > p.product-tagline`
Easy-to-make VR stories. `div.card > a > article > p.product-tagline`
Seamless inline audio. `div.card > a > article > p.product-tagline`
Tell the story behind the numbers. `div.card > a > article > p.product-tagline`
Maps that tell stories. `div.card > a > article > p.product-tagline`
Easy-to-make, beautiful timelines. `div.card > a > article > p.product-tagline`
Living documents and how-to guides developed by the Knight Lab community. `div.container > div.grid > div.column-10 > p.lead`
Live streaming is complicated but we can help. `div.card > a > article > p.product-tagline`
(847) 467-4971 `div.grid > div.grid-item > address > span.tel`
1845 SHERIDAN ROAD `div.grid-item > address > span.address > span.street-address`
FISK #109 & #111 `div.grid-item > address > span.address > span.room-num`
EVANSTON, `address > span.address > div.address-group > span`
IL `address > span.address > div.address-group > span`
60208 `address > span.address > div.address-group > span`
© COPYRIGHT 2017-2023 NORTHWESTERN UNIVERSITY `div.container > div.grid > div.grid-item > span.copyright`

These are opportunities to improve the legibility of your content.

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

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

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

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > header.header-image > div.header-image-content > img.logo `body > header.header-image > div.header-image-content > img.logo`
div.grid > div.column-2 > a > img `div.grid > div.column-2 > a > img`
div.grid-size-2 > div.grid-item > a > img `div.grid-size-2 > div.grid-item > a > img`
div.grid-size-2 > div.grid-item > a > img `div.grid-size-2 > div.grid-item > a > img`

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 have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid