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
/beacon.min.js/vce701823e78c4301a35b7e07294d8730179208881...	86400.0 s	10.2 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.182361] map[node:map[boundingRect:map[bottom:1026 height:387 left:16 right:396 top:639 width:380] lhId:page-2-DIV nodeLabel:four-pillars · example EXAMPLE Heavenly stems · visible Earthly branches · root… path:1,HTML,1,BODY,4,DIV,1,MAIN,0,DIV,0,SECTION,0,DIV,1,DIV selector:div > section.hero-band > div.mx-auto > div.mx-auto snippet:<div class="mx-auto w-full min-w-0 max-w-[460px]"> type:node] score:0.144598 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://bazicalculator.pro/_next/static/media/1755441e3a2fa970-s.p.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:15411 height:15346 left:0 right:412 top:65 width:412] lhId:page-7-MAIN nodeLabel:FOUR PILLARS · FREE · NO SIGN-UP Free BaZi Calculator Calculate your Four Pill… path:1,HTML,1,BODY,4,DIV,1,MAIN selector:body.size-full > div.flex > main.flex-1 snippet:<main class="flex-1"> type:node] score:0.037323] map[node:map[boundingRect:map[bottom:48 height:32 left:364 right:396 top:16 width:32] lhId:page-8-DIV nodeLabel:Toggle Mobile Menu path:1,HTML,1,BODY,4,DIV,0,SECTION,0,DIV,1,DIV,1,DIV selector:section.sticky > div.container > div.flex > div.flex snippet:<div class="flex items-center justify-end gap-4"> type:node] score:0.00044]]

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:71.684 source:map[type:text value:[unattributed]]]]

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
Four Pillars chart displaying Geng Wu, Xin Si, Gui Wei, and Bing Chen with the … `div.mt-10 > div.mx-auto > button.group > img.aspect-video`	bazicalculator.pro/images/promo-poster.webp	36.7 KiB	35.3 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

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.

URL	Transfer Size	Duration
bazicalculator.pro/_next/static/css/696270d9df93ab1d.css	2.2 KiB	190 ms
bazicalculator.pro/_next/static/css/61027c5e8ceda214.css	29.5 KiB	812 ms

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

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.

Element	Layout shift score
four-pillars · example EXAMPLE Heavenly stems · visible Earthly branches · root… `div > section.hero-band > div.mx-auto > div.mx-auto`	0.145
FOUR PILLARS · FREE · NO SIGN-UP Free BaZi Calculator Calculate your Four Pill… `body.size-full > div.flex > main.flex-1`	0.037
Toggle Mobile Menu `section.sticky > div.container > div.flex > div.flex`	0.000

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: 160 ms 21.0 KiB

URL	Transfer Size	Est Savings
bazicalculator.pro/_next/static/chunks/fae1a7c7-071b2102016d171c.js	62.6 KiB	21.0 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.

URL	Total CPU Time	Script Evaluation	Script Parse
bazicalculator.pro/	2.7 s	53 ms	58 ms
bazicalculator.pro/_next/static/chunks/9448-2278cfb833bb224e.js	725 ms	652 ms	25 ms
Unattributable	468 ms	15 ms	0.0 ms
bazicalculator.pro/_next/static/chunks/webpack-cceb4ab57a5ecd29.js	453 ms	428 ms	1.1 ms
bazicalculator.pro/_next/static/chunks/fae1a7c7-071b2102016d171c.js	147 ms	95 ms	30 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.

Category	Time Spent
Style & Layout	2.1 s
Script Evaluation	1.3 s
Other	621 ms
Rendering	232 ms
Script Parsing & Compilation	205 ms
Parse HTML & CSS	201 ms
Garbage Collection	45 ms

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 742 KiB

●Avoid long main-thread tasks 12 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 30 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 30 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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
Calculate my chart `div.mx-auto > div > div.mt-7 > a.btn-teal`
EXAMPLE `div.mx-auto > div.window > div.window-bar > b.window-badge`
02 / YOU GET `div > div.showcase > div.showcase-col > p.showcase-num`
03 / THREE STEPS `div > div.showcase > div.showcase-col > p.showcase-num`
City not listed? Enter time zone and coordinates manually `section#birth-form > form.flex > div.relative > button.mt-1`
Calculate My Chart `div.no-print > section#birth-form > form.flex > button.inline-flex`
15S CHART PREVIEW `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
OVERVIEW `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
WHAT `div.grid-rule > div.p-6 > div.flex > span.font-mono`
WHY `div.grid-rule > div.p-6 > div.flex > span.font-mono`
HOW `div.grid-rule > div.p-6 > div.flex > span.font-mono`
INSIDE THE CHART `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
01 `div.grid > ol.steps > li > span.step-num`
02 `div.grid > ol.steps > li > span.step-num`
03 `div.grid > ol.steps > li > span.step-num`
04 `div.grid > ol.steps > li > span.step-num`
EXAMPLE `div.no-print > section#example > div.mx-auto > p.eyebrow`
● Metal `tr > td.rounded-xl > div.flex > span.inline-flex`
● Metal `tr > td.rounded-xl > div.flex > span.inline-flex`
▲ Wood `tbody > tr > th.w-24 > span.inline-flex`
■ Earth `tbody > tr > th.w-24 > span.inline-flex`
METHOD `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
MORE TOOLS `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
USE CASES `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
ARTICLES `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
Install App `div.no-print > div.fixed > div.group > button.inline-flex`
Calculate my chart `footer.no-print > div.container > div.flex > a.btn-teal`
BaZi and the I Ching are traditional cultural systems. Results here are for stu… `div.container > div.grid > div.col-span-full > p.mt-4`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
methodology `section#how-it-works > div.mt-5 > p.leading-7 > a.text-primary`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Install App `div.no-print > div.fixed > div.group > button.inline-flex`

○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

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

●Select elements have associated label elements.

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

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

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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

○`<object>` elements have alternate text

○Skip links are focusable.

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

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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

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