Skip to content
https://watsnaydouch.site

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

54

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.

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
វត្តស្នាយដួច div.my-auto > div.text-center > div.inline-block > img.w-16
watsnaydouch.site/logo.png999.4 KiB998.7 KiB
App Icon div.relative > div.p-6 > div.w-14 > img.w-full
watsnaydouch.site/icon.png444.1 KiB443.6 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
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.

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: 2.6 s 520.4 KiB
URLTransfer SizeEst Savings
watsnaydouch.site/assets/index-CPYssjIP.js1.9 MiB520.4 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Max Potential First Input Delay 120 ms
Use efficient cache lifetimes
Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
JavaScript execution time 0.4 s
Minimizes main-thread work 1.5 s
Avoid long main-thread tasks 6 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 180 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 210 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
83

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.fixed > div.relative > div.p-6 > button.absolute div.fixed > div.relative > div.p-6 > button.absolute

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ទាក់ទង Admin តាម Telegram div.my-auto > div.mt-5 > a.text-[13px] > span.text-[#2AABEE]
ប្រព័ន្ធគ្រប់គ្រងផ្ទៃក្នុង វត្តស្នាយដួច · សម្រាប់តែអ្នកទទួលសិទ្ធិប្រើប្រាស់ div.w-full > div.w-full > div.col-span-1 > div.pt-4

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
Form elements have associated labels
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
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.
`[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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
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.
100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
92

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.

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 #ContentError
1<!doctype html>Syntax not understood
2<html lang="en">Syntax not understood
3 <head>Syntax not understood
4<script>Syntax not understood
5 window.addEventListener('error', function(event) {Syntax not understood
6 const errorDiv = document.createElement('div');Syntax not understood
7 errorDiv.style.position = 'fixed';Syntax not understood
8 errorDiv.style.top = '0';Syntax not understood
9 errorDiv.style.left = '0';Syntax not understood
10 errorDiv.style.zIndex = '999999';Syntax not understood
11 errorDiv.style.background = 'red';Syntax not understood
12 errorDiv.style.color = 'white';Syntax not understood
13 errorDiv.style.padding = '20px';Syntax not understood
14 errorDiv.style.width = '100%';Syntax not understood
15 errorDiv.style.whiteSpace = 'pre-wrap';Syntax not understood
16 errorDiv.innerText = "GLOBAL ERROR: " + event.error?.stack;Unknown directive
17 document.body.appendChild(errorDiv);Syntax not understood
18 });Syntax not understood
19</script>Syntax not understood
21 <meta charset="UTF-8" />Syntax not understood
22 <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, viewport-fit=cover" />Syntax not understood
23 <title>វត្តស្នាយដួច</title>Syntax not understood
24 <meta name="theme-color" content="#028090" />Syntax not understood
25 <link rel="icon" type="image/x-icon" href="./favicon.ico" />Syntax not understood
26 <link rel="icon" type="image/png" sizes="32x32" href="./favicon-32x32.png" />Syntax not understood
27 <link rel="icon" type="image/png" sizes="16x16" href="./favicon-16x16.png" />Syntax not understood
28 <link rel="icon" type="image/svg+xml" href="./icon.svg" />Syntax not understood
29 <link rel="shortcut icon" href="./favicon.ico" />Syntax not understood
30 <link rel="apple-touch-icon" href="./icon.png" />Syntax not understood
31 <meta name="apple-mobile-web-app-capable" content="yes" />Syntax not understood
32 <meta name="mobile-web-app-capable" content="yes" />Syntax not understood
33 <meta name="apple-mobile-web-app-status-bar-style" content="default" />Syntax not understood
34 <link rel="preconnect" href="https://fonts.googleapis.com">Unknown directive
35 <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>Unknown directive
36 <link rel="preload" href="./fonts/KhmerOS_muollight.ttf" as="font" type="font/ttf" crossorigin="anonymous">Syntax not understood
37 <link href="https://fonts.googleapis.com/css2?family=Battambang:wght@400;700&family=Koulen&family=Moul&family=Rajdhani:wght@300;400;500;600;700&display=swap" rel="stylesheet" crossorigin="anonymous">Unknown directive
38 <meta name="description" content="Temple donation records, expenses, and activities management." />Syntax not understood
39 <meta property="og:title" content="វត្តស្នាយដួច" />Unknown directive
40 <meta property="og:description" content="Temple donation records, expenses, and activities management." />Unknown directive
41 <meta property="og:type" content="website" />Unknown directive
42 <meta name="twitter:card" content="summary_large_image" />Unknown directive
44 <style>Syntax not understood
45 body {Syntax not understood
46 margin: 0;Unknown directive
47 padding: 0;Unknown directive
48 background-color: #FAFAFA;Unknown directive
49 }Syntax not understood
51 display: flex;Unknown directive
52 flex-direction: column;Unknown directive
53 align-items: center;Unknown directive
54 justify-content: center;Unknown directive
55 height: 100vh;Unknown directive
56 width: 100vw;Unknown directive
57 font-family: system-ui, -apple-system, sans-serif;Unknown directive
58 background-color: #FAFAFA;Unknown directive
59 }Syntax not understood
60 @media (prefers-color-scheme: dark) {Unknown directive
61 body { background-color: #0F172A; }Unknown directive
63 .spinner {Syntax not understood
64 border: 3px solid rgba(45, 212, 191, 0.2) !important;Unknown directive
65 border-top-color: #2DD4BF !important;Unknown directive
66 }Syntax not understood
67 }Syntax not understood
68 .spinner {Syntax not understood
69 width: 40px;Unknown directive
70 height: 40px;Unknown directive
71 border: 3px solid rgba(2, 128, 144, 0.2);Unknown directive
72 border-top-color: #028090;Unknown directive
73 border-radius: 50%;Unknown directive
74 animation: spin 1s linear infinite;Unknown directive
75 margin-bottom: 16px;Unknown directive
76 }Syntax not understood
77 @keyframes spin {Syntax not understood
78 to { transform: rotate(360deg); }Unknown directive
79 }Syntax not understood
80 .loading-text {Syntax not understood
81 font-size: 14px;Unknown directive
82 font-weight: 600;Unknown directive
83 color: #A1A1AA;Unknown directive
84 animation: pulse 2s cubic-bezier(0.4, 0, 0.6, 1) infinite;Unknown directive
85 }Syntax not understood
86 @keyframes pulse {Syntax not understood
87 0%, 100% { opacity: 1; }Unknown directive
88 50% { opacity: .5; }Unknown directive
89 }Syntax not understood
90 </style>Syntax not understood
91 <script type="module" crossorigin src="./assets/index-CPYssjIP.js"></script>Syntax not understood
92 <link rel="stylesheet" crossorigin href="./assets/index-BDDfduw9.css">Syntax not understood
93 <link rel="manifest" href="./manifest.webmanifest"><script id="vite-plugin-pwa:register-sw" src="./registerSW.js"></script></head>Unknown directive
94 <body>Syntax not understood
95 <div id="root">Syntax not understood
96 <div id="initial-loader">Syntax not understood
97 <div class="spinner"></div>Syntax not understood
98 <div class="loading-text">កំពុងដំណើរការ...</div>Syntax not understood
99 </div>Syntax not understood
100 </div>Syntax not understood
101 </body>Syntax not understood
102</html>Syntax not understood

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
Document has a meta description
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