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
logseq.com/full-bg-text_mobile.8b57c51e.png	0.0 ms	528.7 KiB
logseq.com/index.4a951e2d.js	0.0 ms	391.7 KiB
logseq.com/benefit-0.94936967.png	0.0 ms	357.8 KiB
logseq.com/promise-0-0.9e77bf1b.png	0.0 ms	324.1 KiB
logseq.com/header_bg.165283d7.png	0.0 ms	249.7 KiB
logseq.com/light_spots_bg.5eb1ded0.png	0.0 ms	239.6 KiB
logseq.com/app-window-placeholder-bg-no-logo.c1b98589.png	0.0 ms	148.6 KiB
logseq.com/avatar.d3fd2d4e.png	0.0 ms	106.5 KiB
logseq.com/full-bg-a.8ea8e509.png	0.0 ms	19.7 KiB
logseq.com/index.5f582d11.css	0.0 ms	18.0 KiB
logseq.com/cover.b8c6a4fc.png	0.0 ms	14.4 KiB
logseq.com/footer-gradients-bg.b772b439.png	0.0 ms	10.6 KiB
logseq.com/product_hunt_logo.55e01c43.png	0.0 ms	8.6 KiB
logseq.com/logo-with-border.a30e7bd0.png	0.0 ms	3.9 KiB
logseq.com/icon_relations.49fb7c0d.png	0.0 ms	2.9 KiB
logseq.com/icon_intel.abf50ae6.png	0.0 ms	2.3 KiB
logseq.com/full-bg-c-gradient.6c959506.png	0.0 ms	1.8 KiB
logseq.com/index.5cad6fbd.js	0.0 ms	1.5 KiB
assets.lemonsqueezy.com/lemon.js	14400.0 s	1.8 KiB
logseq.com/icon_m1.7f7f8bc5.png	0.0 ms	774 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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:59.652 source:map[column:141384 line:1 type:source-location url:https://logseq.com/index.4a951e2d.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:56.352 source:map[column:1304 line:3131 type:source-location url:https://logseq.com/index.4a951e2d.js urlProvider:network]] map[reflowTime:2.852 source:map[column:1903 line:3180 type:source-location url:https://logseq.com/index.4a951e2d.js urlProvider:network]] map[reflowTime:0.448 source:map[column:1104 line:5508 type:source-location url:https://logseq.com/index.4a951e2d.js urlProvider:network]]]

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
image `div.app-page > div.page-inner-full-wrap > div.page-inner > img.w-full`	logseq.com/full-bg-text_mobile.8b57c51e.png	527.8 KiB	472.4 KiB
image `div#Relationships > div.card > div.l > img`	logseq.com/benefit-0.94936967.png	357.1 KiB	314.6 KiB
image `div.bd > div.bd-info > div.flex > img.animate-in`	logseq.com/promise-0-0.9e77bf1b.png	323.4 KiB	279.7 KiB
Image `div.glass-card > div.glass-card-inner > div.avatar > span.avatar-img`	logseq.com/avatar.d3fd2d4e.png	106.1 KiB	90.7 KiB
div.bd > div.wrap > div.c > div.app-window-holder `div.bd > div.wrap > div.c > div.app-window-holder`	logseq.com/app-window-placeholder-bg-no-logo.c1b98589.png	148.1 KiB	34.1 KiB
div.app-head-showcase > div.inner > div.item-wrap > div.image-2 `div.app-head-showcase > div.inner > div.item-wrap > div.image-2`	logseq.com/header_bg.165283d7.png	249.1 KiB	23.3 KiB
Image `div.glass-card > div.glass-card-inner > div.avatar > span.avatar-img`	logseq.com/cover.b8c6a4fc.png	14.0 KiB	12.2 KiB
image `button.flex > div.l > i.pr-1.5 > img.w-10`	logseq.com/product_hunt_logo.55e01c43.png	8.2 KiB	7.5 KiB
A safe space for your thoughts. Designed to store your interests, questions, id… `main.app-container > div.app-page > div.page-inner-full-wrap > div.page-inner`	logseq.com/footer-gradients-bg.b772b439.png	10.3 KiB	6.0 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: div.app-head-showcase > div.inner > div.item-wrap > div.image-2

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

selector: div.app-head-showcase > div.inner > div.item-wrap > div.image-2

snippet: <div class="image-2 z-10 thinker absolute">

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
logseq.com/index.5f582d11.css	18.0 KiB	363 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: 845 ms

URL	Time Spent
www.logseq.com/	845 ms
logseq.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

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: 360 ms 69.0 KiB

URL	Transfer Size	Est Savings
logseq.com/index.4a951e2d.js	391.3 KiB	69.0 KiB

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: 400 ms 12.4 KiB

URL	Transfer Size	Est Savings
logseq.com/index.5f582d11.css	17.7 KiB	12.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.

Estimated savings: 910 ms 156.1 KiB

URL	Transfer Size	Est Savings
logseq.com/index.4a951e2d.js	389.6 KiB	156.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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	2.3 s
Script Evaluation	1.0 s
Style & Layout	636 ms
Rendering	418 ms
Garbage Collection	24 ms
Parse HTML & CSS	7.5 ms
Script Parsing & Compilation	5.8 ms

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
image `div#Relationships > div.card > div.l > img`	logseq.com/benefit-0.94936967.png
image `div.bd > div.bd-info > div.flex > img.animate-in`	logseq.com/promise-0-0.9e77bf1b.png
image `div.app-page > div.page-inner-full-wrap > div.page-inner > img.w-full`	logseq.com/full-bg-text_mobile.8b57c51e.png
image `button.flex > div.l > i.pr-1.5 > img.w-10`	logseq.com/product_hunt_logo.55e01c43.png
Logseq `div.flex > div.flex > a.app-logo-link > img`	logseq.com/logo-with-border.a30e7bd0.png

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

●Avoids enormous network payloads Total size was 2,502 KiB

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 9 long tasks found

●Avoid non-composited animations 6 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 680 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid large layout shifts

100

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.

○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

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

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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

○Identical links have the same purpose.

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

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.

Source Description

Source	Description
logseq.com/index.4a951e2d.js line 779, col 499	[ERROR] 36:49.84 AuthError - Error: Amplify has not been configured correctly. The configuration object is missing required auth properties. This error is typically caused by one of the following scenarios: 1. Did you run `amplify push` after adding auth via `amplify add auth`? See https://aws-amplify.github.io/docs/js/authentication#amplify-project-setup for more information 2. This could also be caused by multiple conflicting versions of amplify packages, see (https://docs.amplify.aws/lib/troubleshooting/upgrading/q/platform/js) for help upgrading Amplify packages.
logseq.com/index.4a951e2d.js line 779, col 499	[ERROR] 36:49.85 AuthError - Error: Amplify has not been configured correctly. The configuration object is missing required auth properties. This error is typically caused by one of the following scenarios: 1. Did you run `amplify push` after adding auth via `amplify add auth`? See https://aws-amplify.github.io/docs/js/authentication#amplify-project-setup for more information 2. This could also be caused by multiple conflicting versions of amplify packages, see (https://docs.amplify.aws/lib/troubleshooting/upgrading/q/platform/js) for help upgrading Amplify packages.

logseq.com/index.4a951e2d.js line 779, col 499

[ERROR] 36:49.84 AuthError - 
            Error: Amplify has not been configured correctly. 
            The configuration object is missing required auth properties.
            This error is typically caused by one of the following scenarios:

            1. Did you run `amplify push` after adding auth via `amplify add auth`?
                See https://aws-amplify.github.io/docs/js/authentication#amplify-project-setup for more information

            2. This could also be caused by multiple conflicting versions of amplify packages, see (https://docs.amplify.aws/lib/troubleshooting/upgrading/q/platform/js) for help upgrading Amplify packages.

logseq.com/index.4a951e2d.js line 779, col 499

[ERROR] 36:49.85 AuthError - 
            Error: Amplify has not been configured correctly. 
            The configuration object is missing required auth properties.
            This error is typically caused by one of the following scenarios:

            1. Did you run `amplify push` after adding auth via `amplify add auth`?
                See https://aws-amplify.github.io/docs/js/authentication#amplify-project-setup for more information

            2. This could also be caused by multiple conflicting versions of amplify packages, see (https://docs.amplify.aws/lib/troubleshooting/upgrading/q/platform/js) for help upgrading Amplify packages.

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

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.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	<!doctype html><html lang="en"><head><script type="module" src="https://logseq.com/index.5cad6fbd.js"></script><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=5.0, minimum-scale=1.0"><meta http-equiv="X-UA-Compatible" content="ie=edge"><title>Logseq: A privacy-first, open-source knowledge base</title><link href="https://asset.logseq.com/static/img/logo.png" rel="icon shortcut" type="image/png"><link href="https://asset.logseq.com/static/img/logo.png" rel="icon shortcut" sizes="192x192"><link href="https://asset.logseq.com/static/img/logo.png" rel="apple-touch-icon"><meta content="Logseq" name="apple-mobile-web-app-title"><meta content="yes" name="apple-mobile-web-app-capable"><meta content="yes" name="apple-touch-fullscreen"><meta content="black-translucent" name="apple-mobile-web-app-status-bar-style"><meta content="yes" name="mobile-web-app-capable"><meta content="summary_large_image" name="twitter:card"><meta content="A privacy-first, open-source platform for knowledge management and collaboration." name="twitter:description"><meta content="@logseq" name="twitter:site"><meta content="A privacy-first, open-source knowledge base" name="twitter:title"><meta content="https://asset.logseq.com/static/img/social-banner-230118.png" name="twitter:image:src"><meta content="A privacy-first, open-source platform for knowledge management and collaboration." name="twitter:image:alt"><meta content="A privacy-first, open-source knowledge base" property="og:title"><meta content="site" property="og:type"><meta content="https://logseq.com" property="og:url"><meta content="https://asset.logseq.com/static/img/social-banner-230118.png" property="og:image"><meta content="A privacy-first, open-source platform for knowledge management and collaboration." property="og:description"><meta content="logseq" property="og:site_name"><meta description="A privacy-first, open-source platform for knowledge management and collaboration."><link rel="stylesheet" href="https://logseq.com/index.5f582d11.css"></head><body> <div id="root"></div> <script src="https://assets.lemonsqueezy.com/lemon.js" defer></script> <script src="https://logseq.com/index.4a951e2d.js" type="module" defer></script> </body></html>	`Unknown directive`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`