Skip to content
https://lacia.life

Lighthouse Desktop

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

83

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.

RequestCache TTLTransfer Size
lacia.life/uploads/anime/585820.webp86400.0 s390.9 KiB
lacia.life/uploads/anime/633836.webp86400.0 s372.0 KiB
lacia.life/uploads/anime/528828.webp86400.0 s238.8 KiB
lacia.life/uploads/anime/638151.webp86400.0 s148.0 KiB
lacia.life/uploads/anime/515594.webp86400.0 s129.9 KiB
lacia.life/uploads/anime/412144.webp86400.0 s103.2 KiB
lacia.life/uploads/2026/09/96018188-b9ad-492c-bd70-50c65f47f4c1.webp86400.0 s75.3 KiB
lacia.life/uploads/2026/09/cb50ad27-6c6d-4174-9380-31546c49d36e.webp86400.0 s37.9 KiB
/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba178836298...86400.0 s10.1 KiB

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

URLResource SizeEst Savings
body > div.mx-auto > aside.dvh-cap-img-96 > img.pointer-events-none body > div.mx-auto > aside.dvh-cap-img-96 > img.pointer-events-none
lacia.life/assets/misaki.webp437.0 KiB429.6 KiB
Clevatess II-魔兽之王与虚假的勇者传承- article.group > div.relative > button.block > img.h-full
lacia.life/uploads/anime/585820.webp390.0 KiB388.2 KiB
Re：从零开始的异世界生活 第四季 夺还篇 article.group > div.relative > button.block > img.h-full
lacia.life/uploads/anime/633836.webp371.2 KiB368.9 KiB
main.min-w-0 > div.pb-4 > section.relative > img.pointer-events-none main.min-w-0 > div.pb-4 > section.relative > img.pointer-events-none
lacia.life/assets/hero.webp269.5 KiB262.2 KiB
骸骨骑士大人异世界冒险中 第二季 article.group > div.relative > button.block > img.h-full
lacia.life/uploads/anime/528828.webp238.1 KiB236.4 KiB
地狱模式～喜欢挑战特殊成就的玩家在废设定的异世界成为无双～第二季 article.group > div.relative > button.block > img.h-full
lacia.life/uploads/anime/638151.webp147.2 KiB145.2 KiB
关于我转生变成史莱姆这档事 第四季 article.group > div.relative > button.block > img.h-full
lacia.life/uploads/anime/515594.webp129.1 KiB127.3 KiB
恋爱游戏世界对路人角色很不友好 第二季 article.group > div.relative > button.block > img.h-full
lacia.life/uploads/anime/412144.webp102.5 KiB100.2 KiB
div > a.@container > div.relative > img.relative div > a.@container > div.relative > img.relative
lacia.life/uploads/2026/09/96018188-b9ad-492c-bd70-50c65f47f4c1.webp74.6 KiB74.2 KiB
div > a.@container > div.relative > img.relative div > a.@container > div.relative > img.relative
lacia.life/uploads/2026/09/cb50ad27-6c6d-4174-9380-31546c49d36e.webp37.1 KiB36.7 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.

URLTransfer SizeDuration
lacia.life/assets/styles-wA1aSLJA.css17.2 KiB67 ms

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

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: 50 ms 29.7 KiB
URLTransfer SizeEst Savings
lacia.life/assets/index-V4LMfLtM.js76.4 KiB29.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
body > div.mx-auto > aside.dvh-cap-img-96 > img.pointer-events-none body > div.mx-auto > aside.dvh-cap-img-96 > img.pointer-events-none
lacia.life/assets/misaki.webp

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 30 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 2,475 KiB
●JavaScript execution time 0.1 s
●Minimizes main-thread work 0.4 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 20 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 360 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
95

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
主页 div.col-start-1 > header.site-nav > nav.site-nav-links > a.site-nav-link
CHK div.relative > h1.flex > span.whitespace-nowrap > span.text-[#7DBBE2]
Chugoku 中国 div.relative > button.mt-8 > span.mt-[12px] > span.relative
Chugoku button.mt-8 > span.mt-[12px] > span.relative > span.absolute
Hikikomori ひきこもり div.relative > button.mt-8 > span.mt-[12px] > span.relative
Hikikomori button.mt-8 > span.mt-[12px] > span.relative > span.absolute
Kyokai 協会 div.relative > button.mt-8 > span.mt-[12px] > span.relative
Kyokai button.mt-8 > span.mt-[12px] > span.relative > span.absolute

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
Chugoku 中国 Hikikomori ひきこもり Kyokai 協会 div.pb-4 > section.relative > div.relative > button.mt-8
○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>`
●`[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
●`[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
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○`[role]` values are valid
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
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
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○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`

Send Feedback