Skip to content
https://wolframalpha.com

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.

47

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.

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.

URLEst Savings
/_next/static/media/source-sans-pro-v9-latin-regular.090a...405 ms
www.wolframalpha.com/_next/static/media/roboto-latin-italic-400.fac7cf37.woff2400 ms
www.wolframalpha.com/_next/static/media/Lexia_W_Lt.19c4cb27.woff400 ms
/_next/static/media/source-sans-pro-v9-latin-600.96f36c1a...400 ms
www.wolframalpha.com/_next/static/media/roboto-latin-400.7e0ffa28.woff2400 ms
www.wolframalpha.com/_next/static/media/Lexia_W_LtIt.763dc789.woff155 ms

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:897.609 label:Time to first byte subpart:timeToFirstByte] map[duration:2096.228 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-P
nodeLabel: This website uses cookies to optimize your experience with our services on the …
path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,5,SECTION,0,P
selector: div > div.sc-469ea5b3-0 > section.sc-925ffb52-0 > p.sc-4020a3e-1
snippet: <p class="sc-4020a3e-1 iEouda">

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

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: 750 ms
URLTime Spent
wolframalpha.com/750 ms
www.wolframalpha.com/0.0 ms

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.

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 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: 1.2 s 260.6 KiB
URLTransfer SizeEst Savings
www.wolframalpha.com/_next/static/chunks/pages/_app-5e36c1fbb0d9113d.js193.6 KiB77.5 KiB
www.wolframalpha.com/_next/static/chunks/4869-e9da3fb3526a80a2.js123.0 KiB70.0 KiB
www.wolframalpha.com/_next/static/chunks/9afd5809-45a13b3d11fec1dd.js83.8 KiB50.3 KiB
www.wolframalpha.com/_next/static/chunks/275-c6462c43c8fa56a7.js64.5 KiB42.7 KiB
www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js58.5 KiB20.1 KiB

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.

URLTotal CPU TimeScript EvaluationScript Parse
www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js1.0 s851 ms48 ms
www.wolframalpha.com/763 ms9.0 ms4.5 ms
www.wolframalpha.com/_next/static/chunks/pages/index-af52cfcd888931b0.js645 ms638 ms5.7 ms
www.wolframalpha.com/_next/static/chunks/pages/_app-5e36c1fbb0d9113d.js522 ms386 ms107 ms
Unattributable354 ms10 ms0.0 ms
www.wolframalpha.com/_next/static/chunks/main-9c7afc91105fe70f.js186 ms139 ms46 ms
www.wolframalpha.com/_next/static/chunks/4869-e9da3fb3526a80a2.js76 ms1.9 ms73 ms
www.wolframalpha.com/_next/static/chunks/9afd5809-45a13b3d11fec1dd.js72 ms1.7 ms70 ms

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 Evaluation2.1 s
Other579 ms
Style & Layout479 ms
Script Parsing & Compilation408 ms
Rendering109 ms
Parse HTML & CSS53 ms
Garbage Collection40 ms

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 reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages with WebSocket cannot enter back/forward cache.Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because WebSocket has been used.Not actionable

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

●Use efficient cache lifetimes
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Improve image delivery
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 769 KiB
●User Timing marks and measures 4 user timings
●Avoid long main-thread tasks 9 long tasks found
●Avoid non-composited animations 3 animated elements found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 150 ms
●Server Backend Latencies 240 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 170 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
86

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
div.sc-32afdb9f-0 > div.sc-a16b5657-2 > nav.sc-a16b5657-1 > button._RLFy div.sc-32afdb9f-0 > div.sc-a16b5657-2 > nav.sc-a16b5657-1 > button._RLFy

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
footer.sc-a94ac160-0 > ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy footer.sc-a94ac160-0 > ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy

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
Mathematics section.sc-48f4de15-0 > h2.sc-2eae87b5-0 > a._RLFy > span.sc-48f4de15-1
Step-by-Step Solutions ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
Elementary Math ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
Algebra ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
More Topics » section.sc-48f4de15-0 > ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy
Science & Technology section.sc-48f4de15-0 > h2.sc-2eae87b5-0 > a._RLFy > span.sc-48f4de15-1
Units & Measures ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
Physics ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
Chemistry ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
More Topics » section.sc-48f4de15-0 > ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy
Society & Culture section.sc-48f4de15-0 > h2.sc-2eae87b5-0 > a._RLFy > span.sc-48f4de15-1
People ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
Arts & Media ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
Dates & Times ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
More Topics » section.sc-48f4de15-0 > ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy
Everyday Life section.sc-48f4de15-0 > h2.sc-2eae87b5-0 > a._RLFy > span.sc-48f4de15-1
Personal Health ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
Personal Finance ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
Surprises ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy > span.sc-8848da46-0
More Topics » section.sc-48f4de15-0 > ul.sc-48f4de15-2 > li.sc-2eae87b5-0 > a._RLFy
Pro ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
Mobile Apps ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
Products ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
Business ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
API ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
LLM ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
About ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
Contact ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
©2026 Wolfram footer.sc-a94ac160-0 > ul.sc-57bc466-0 > li.sc-f328ba4c-0 > span.sc-105e6ee4-0
©2026 ul.sc-57bc466-0 > li.sc-f328ba4c-0 > span.sc-105e6ee4-0 > span.sc-105e6ee4-1
Terms ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
Privacy ul.sc-57bc466-0 > li.sc-f328ba4c-0 > a._RLFy > span.sc-8848da46-0
Accept & Close div > div.sc-469ea5b3-0 > section.sc-925ffb52-0 > button._RLFy

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-*]` 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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●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
○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 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
○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.
○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
www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js
Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at rD (https://www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js:1:45909) at oK (https://www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js:1:96473) at uS (https://www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js:1:127042) at https://www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js:1:126887 at uw (https://www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js:1:126895) at uc (https://www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js:1:122270) at uZ (https://www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js:1:145408) at MessagePort.N (https://www.wolframalpha.com/_next/static/chunks/framework-7e404342b933869f.js:1:9027)

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.

URL
www.wolframalpha.com/_next/static/chunks/pages/_app-5e36c1fbb0d9113d.js
●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○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