Skip to content
Audit Complete

Results for https://www.logseq.com

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:37 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

HSTS header is missing

Security › Security Headers
3

No Content-Security-Policy header found

Security › Content Security Policy
4

1 link(s) with no accessible text

Accessibility › Link & Button Quality
5

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility › 404 Error Page
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.logseq.com)](https://beavercheck.com/results/4e49e8f0-fa63-a6d0-69b6-0883959d5a8e)
<a href="https://beavercheck.com/results/4e49e8f0-fa63-a6d0-69b6-0883959d5a8e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.logseq.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.logseq.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

57
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.88 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

6.78 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

416 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.88 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

6.78 s

Detailed Report

Audit breakdown by category with detailed findings.

57

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
logseq.com/full-bg-text_mobile.8b57c51e.png0.0 ms528.7 KiB
logseq.com/index.4a951e2d.js0.0 ms391.7 KiB
logseq.com/benefit-0.94936967.png0.0 ms357.8 KiB
logseq.com/promise-0-0.9e77bf1b.png0.0 ms324.1 KiB
logseq.com/header_bg.165283d7.png0.0 ms249.7 KiB
logseq.com/light_spots_bg.5eb1ded0.png0.0 ms239.6 KiB
logseq.com/app-window-placeholder-bg-no-logo.c1b98589.png0.0 ms148.6 KiB
logseq.com/avatar.d3fd2d4e.png0.0 ms106.5 KiB
logseq.com/full-bg-a.8ea8e509.png0.0 ms19.7 KiB
logseq.com/index.5f582d11.css0.0 ms18.0 KiB
logseq.com/cover.b8c6a4fc.png0.0 ms14.4 KiB
logseq.com/footer-gradients-bg.b772b439.png0.0 ms10.6 KiB
logseq.com/product_hunt_logo.55e01c43.png0.0 ms8.6 KiB
logseq.com/logo-with-border.a30e7bd0.png0.0 ms3.9 KiB
logseq.com/icon_relations.49fb7c0d.png0.0 ms2.9 KiB
logseq.com/icon_intel.abf50ae6.png0.0 ms2.3 KiB
logseq.com/full-bg-c-gradient.6c959506.png0.0 ms1.8 KiB
logseq.com/index.5cad6fbd.js0.0 ms1.5 KiB
assets.lemonsqueezy.com/lemon.js14400.0 s1.8 KiB
logseq.com/icon_m1.7f7f8bc5.png0.0 ms774 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

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

URLResource SizeEst Savings
image div.app-page > div.page-inner-full-wrap > div.page-inner > img.w-full
logseq.com/full-bg-text_mobile.8b57c51e.png527.8 KiB472.4 KiB
image div#Relationships > div.card > div.l > img
logseq.com/benefit-0.94936967.png357.1 KiB314.6 KiB
image div.bd > div.bd-info > div.flex > img.animate-in
logseq.com/promise-0-0.9e77bf1b.png323.4 KiB279.7 KiB
Image div.glass-card > div.glass-card-inner > div.avatar > span.avatar-img
logseq.com/avatar.d3fd2d4e.png106.1 KiB90.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.png148.1 KiB34.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.png249.1 KiB23.3 KiB
Image div.glass-card > div.glass-card-inner > div.avatar > span.avatar-img
logseq.com/cover.b8c6a4fc.png14.0 KiB12.2 KiB
image button.flex > div.l > i.pr-1.5 > img.w-10
logseq.com/product_hunt_logo.55e01c43.png8.2 KiB7.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.png10.3 KiB6.0 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

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.

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.

URLTransfer SizeDuration
logseq.com/index.5f582d11.css18.0 KiB363 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.

Estimated savings: 845 ms
URLTime 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.

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.

TTI

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 360 ms 69.0 KiB
URLTransfer SizeEst Savings
logseq.com/index.4a951e2d.js391.3 KiB69.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.

Estimated savings: 400 ms 12.4 KiB
URLTransfer SizeEst Savings
logseq.com/index.5f582d11.css17.7 KiB12.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.

Estimated savings: 910 ms 156.1 KiB
URLTransfer SizeEst Savings
logseq.com/index.4a951e2d.js389.6 KiB156.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

CategoryTime Spent
Other2.3 s
Script Evaluation1.0 s
Style & Layout636 ms
Rendering418 ms
Garbage Collection24 ms
Parse HTML & CSS7.5 ms
Script Parsing & Compilation5.8 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

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

SourceDescription
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
83

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.

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.

Line #ContentError
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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

91
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
97
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.11 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.70 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

37 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.11 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.70 s

Detailed Report

Audit breakdown by category with detailed findings.

91

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
logseq.com/full-bg-text.c1d5a921.png0.0 ms494.5 KiB
logseq.com/index.4a951e2d.js0.0 ms391.7 KiB
logseq.com/benefit-0.94936967.png0.0 ms357.8 KiB
logseq.com/whiteboard-demo.602e2184.png0.0 ms353.8 KiB
logseq.com/promise-0-0.9e77bf1b.png0.0 ms324.1 KiB
logseq.com/header_bg.165283d7.png0.0 ms249.7 KiB
logseq.com/light_spots_bg.5eb1ded0.png0.0 ms239.6 KiB
logseq.com/sync-indicator-demo.83ba8708.png0.0 ms171.3 KiB
logseq.com/light_spots_full_bg.f8c3aa4c.png0.0 ms152.4 KiB
logseq.com/app-window-placeholder-bg-no-logo.c1b98589.png0.0 ms148.6 KiB
logseq.com/avatar.d3fd2d4e.png0.0 ms106.5 KiB
logseq.com/features_sp.3e1e0ab5.png0.0 ms47.3 KiB
logseq.com/logo-with-shadow.286d4dd7.png0.0 ms36.3 KiB
logseq.com/full-bg-a.8ea8e509.png0.0 ms19.7 KiB
logseq.com/gradient-bg-demo.5c947e0e.png0.0 ms18.3 KiB
logseq.com/index.5f582d11.css0.0 ms18.0 KiB
logseq.com/cover.b8c6a4fc.png0.0 ms14.4 KiB
logseq.com/product_hunt_logo.55e01c43.png0.0 ms8.6 KiB
logseq.com/logo-with-border.a30e7bd0.png0.0 ms3.9 KiB
logseq.com/icon_relations.49fb7c0d.png0.0 ms2.9 KiB
logseq.com/icon_intel.abf50ae6.png0.0 ms2.3 KiB
logseq.com/icon_daily_plan.4d933095.png0.0 ms2.2 KiB
logseq.com/icon_journals.251f455e.png0.0 ms2.1 KiB
logseq.com/icon_data_control.2ae3325d.png0.0 ms1.9 KiB
logseq.com/full-bg-c-gradient.6c959506.png0.0 ms1.8 KiB
logseq.com/index.5cad6fbd.js0.0 ms1.5 KiB
assets.lemonsqueezy.com/lemon.js14400.0 s1.8 KiB
logseq.com/icon_m1.7f7f8bc5.png0.0 ms777 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

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:93.923 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:15.927 source:map[column:1304 line:3131 type:source-location url:https://logseq.com/index.4a951e2d.js urlProvider:network]] map[reflowTime:77.478 source:map[column:1903 line:3180 type:source-location url:https://logseq.com/index.4a951e2d.js urlProvider:network]] map[reflowTime:0.518 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

URLResource SizeEst Savings
image div.app-page > div.page-inner-full-wrap > div.page-inner > img.w-full
logseq.com/full-bg-text.c1d5a921.png493.6 KiB318.8 KiB
image div#Relationships > div.card > div.l > img
logseq.com/benefit-0.94936967.png357.1 KiB304.2 KiB
image div.bd > div.bd-info > div.flex > img.animate-in
logseq.com/promise-0-0.9e77bf1b.png323.4 KiB287.7 KiB
Image div.glass-card > div.glass-card-inner > div.avatar > span.avatar-img
logseq.com/avatar.d3fd2d4e.png106.1 KiB90.7 KiB
div.bd > div.wrap > div.a > div.app-window-holder div.bd > div.wrap > div.a > div.app-window-holder
logseq.com/app-window-placeholder-bg-no-logo.c1b98589.png148.1 KiB34.1 KiB
div.wrap > div.a > div.app-window-holder > ::after div.wrap > div.a > div.app-window-holder > ::after
logseq.com/logo-with-shadow.286d4dd7.png35.9 KiB28.6 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.png249.1 KiB23.3 KiB
Image div.glass-card > div.glass-card-inner > div.avatar > span.avatar-img
logseq.com/cover.b8c6a4fc.png14.0 KiB12.2 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-6-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.

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.

URLTransfer SizeDuration
logseq.com/index.5f582d11.css18.0 KiB157 ms

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

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 80 ms 69.0 KiB
URLTransfer SizeEst Savings
logseq.com/index.4a951e2d.js391.3 KiB69.0 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.

Estimated savings: 160 ms 156.8 KiB
URLTransfer SizeEst Savings
logseq.com/index.4a951e2d.js389.6 KiB156.8 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

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.c1d5a921.png
image button.flex > div.l > i.pr-1.5 > img.w-10
logseq.com/product_hunt_logo.55e01c43.png
button#tab-Relationships > div.py-6 > span.icon > img button#tab-Relationships > div.py-6 > span.icon > img
logseq.com/icon_relations.49fb7c0d.png
button#tab-Daily_Plan > div.py-6 > span.icon > img button#tab-Daily_Plan > div.py-6 > span.icon > img
logseq.com/icon_daily_plan.4d933095.png
button#tab-Journaling > div.py-6 > span.icon > img button#tab-Journaling > div.py-6 > span.icon > img
logseq.com/icon_journals.251f455e.png
button#tab-Data_Control > div.py-6 > span.icon > img button#tab-Data_Control > div.py-6 > span.icon > img
logseq.com/icon_data_control.2ae3325d.png
Logseq div.flex > div.flex > a.app-logo-link > img
logseq.com/logo-with-border.a30e7bd0.png
intel div.flex > div.flex > span.color-icon > img.w-4/5
logseq.com/icon_intel.abf50ae6.png
M1 div.flex > div.flex > span.color-icon > img.w-4/5
logseq.com/icon_m1.7f7f8bc5.png
intel div.flex > div.flex > span.color-icon > img.w-4/5
logseq.com/icon_intel.abf50ae6.png
M1 div.flex > div.flex > span.color-icon > img.w-4/5
logseq.com/icon_m1.7f7f8bc5.png
intel div.flex > div.flex > span.color-icon > img.w-4/5
logseq.com/icon_intel.abf50ae6.png
M1 div.flex > div.flex > span.color-icon > img.w-4/5
logseq.com/icon_m1.7f7f8bc5.png

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 282 ms
URLTime Spent
www.logseq.com/282 ms
logseq.com/0.0 ms
●Time to Interactive 1.7 s
●Max Potential First Input Delay 90 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Reduce unused CSS
●JavaScript execution time 0.3 s
●Minimizes main-thread work 1.0 s
●Avoid long main-thread tasks 2 long tasks found
●Avoid non-composited animations 4 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 60 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
○User Timing marks and measures
○Avoid large layout shifts
97

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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Failing Elements
Queries div.desc-card > h2.hidden > span > a
Search div.desc-card > h2.hidden > span > a
Flashcards div.desc-card > h2.hidden > span > a

These are opportunities to improve the legibility of your content.

○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
●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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●No element has a `[tabindex]` value greater than 0
●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
●Identical links have the same purpose.
○`[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 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
○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.
○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.
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

SourceDescription
logseq.com/index.4a951e2d.js line 779, col 499
[ERROR] 37:06.501 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] 37:06.505 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
83

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.

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.

Line #ContentError
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`

Send Feedback