Lighthouse Mobile
· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.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.
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
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| goodschina.ru/assets/index-BpDzux6U.css | 0 B |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| goodschina.ru/ | 1.0 s |
| goodschina.ru/ | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-2QRKGJB32X | 142.8 KiB | 60.8 KiB |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
form.p-8 > div > div.relative > button.absolute form.p-8 > div > div.relative > 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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Проблемы со входом? ВКонтакте · Telegram div.min-h-screen > div.w-full > div.bg-slate-50 > p.text-xs |
ВКонтакте div.w-full > div.bg-slate-50 > p.text-xs > a.hover:text-slate-600 |
Telegram div.w-full > div.bg-slate-50 > p.text-xs > a.hover:text-slate-600 |
These are opportunities to improve the legibility of your content.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
form.p-8 > div > div.relative > button.absolute form.p-8 > div > div.relative > button.absolute |
These items highlight common accessibility best practices.
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Line # | Content | Error |
|---|---|---|
| 1 | <!DOCTYPE html> | Syntax not understood |
| 2 | <html lang="en"> | Syntax not understood |
| 4 | <head> | Syntax not understood |
| 5 | <meta charset="UTF-8" /> | Syntax not understood |
| 6 | <meta name="viewport" content="width=device-width, initial-scale=1.0" /> | Syntax not understood |
| 7 | <title>GOODS CHINA</title> | Syntax not understood |
| 8 | <link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32" /> | Syntax not understood |
| 9 | <link rel="preconnect" href="https://knizgpullfdgeeueculf.supabase.co" crossorigin /> | Unknown directive |
| 10 | <script> | Syntax not understood |
| 11 | // Фикс F5 Chrome: патчим navigator.locks ДО загрузки любых модулей. | Unknown directive |
| 12 | // Supabase GoTrueClient вызывает navigator.locks.request синхронно в конструкторе — | Syntax not understood |
| 13 | // патч в index.tsx всегда опаздывает, здесь — нет. | Syntax not understood |
| 14 | if (navigator.locks) { | Syntax not understood |
| 15 | try { | Syntax not understood |
| 16 | Object.defineProperty(navigator, 'locks', { | Syntax not understood |
| 17 | value: { | Unknown directive |
| 18 | request: function(name, optOrFn, fn) { | Unknown directive |
| 19 | var cb = typeof fn === 'function' ? fn : optOrFn; | Unknown directive |
| 20 | return Promise.resolve().then(function() { return cb({ name: name, mode: 'exclusive' }); }); | Unknown directive |
| 21 | } | Syntax not understood |
| 22 | }, | Syntax not understood |
| 23 | configurable: true, | Unknown directive |
| 24 | writable: true | Unknown directive |
| 25 | }); | Syntax not understood |
| 26 | } catch(e) {} | Syntax not understood |
| 27 | } | Syntax not understood |
| 28 | </script> | Syntax not understood |
| 29 | <script> | Syntax not understood |
| 30 | // Миграция ключа сессии: всегда используем ключ для прокси (sb-goodschina) | Unknown directive |
| 31 | (function() { | Syntax not understood |
| 32 | var proxyKey = 'sb-goodschina-auth-token'; | Syntax not understood |
| 33 | var directKey = 'sb-knizgpullfdgeeueculf-auth-token'; | Syntax not understood |
| 34 | // Если есть ключ от прямого URL — переносим в ключ прокси | Syntax not understood |
| 35 | var data = localStorage.getItem(directKey); | Syntax not understood |
| 36 | if (data && !localStorage.getItem(proxyKey)) { | Syntax not understood |
| 37 | localStorage.setItem(proxyKey, data); | Syntax not understood |
| 38 | localStorage.removeItem(directKey); | Syntax not understood |
| 39 | } | Syntax not understood |
| 40 | })(); | Syntax not understood |
| 41 | </script> | Syntax not understood |
| 42 | <script> | Syntax not understood |
| 43 | (function() { | Syntax not understood |
| 44 | var VERSION = "1.0.5"; | Syntax not understood |
| 45 | if (localStorage.getItem('app_version') !== VERSION) { | Syntax not understood |
| 46 | var keys = Object.keys(localStorage); | Syntax not understood |
| 47 | for (var i = 0; i < keys.length; i++) { | Syntax not understood |
| 48 | if (keys[i] !== 'app_version') localStorage.removeItem(keys[i]); | Syntax not understood |
| 49 | } | Syntax not understood |
| 50 | localStorage.setItem('app_version', VERSION); | Syntax not understood |
| 51 | window.location.reload(); | Syntax not understood |
| 52 | } | Syntax not understood |
| 53 | })(); | Syntax not understood |
| 54 | </script> | Syntax not understood |
| 55 | <!-- Google tag (gtag.js) --> | Syntax not understood |
| 56 | <script async src="https://www.googletagmanager.com/gtag/js?id=G-2QRKGJB32X"></script> | Unknown directive |
| 57 | <script> | Syntax not understood |
| 58 | window.dataLayer = window.dataLayer || []; | Syntax not understood |
| 59 | function gtag(){dataLayer.push(arguments);} | Syntax not understood |
| 60 | gtag('js', new Date()); | Syntax not understood |
| 61 | gtag('config', 'G-2QRKGJB32X'); | Syntax not understood |
| 62 | </script> | Syntax not understood |
| 63 | <script type="module" crossorigin src="/assets/index-gKVK3eix.js"></script> | Syntax not understood |
| 64 | <link rel="stylesheet" crossorigin href="/assets/index-BpDzux6U.css"> | Syntax not understood |
| 65 | </head> | Syntax not understood |
| 67 | <body> | Syntax not understood |
| 68 | <div id="root"></div> | Syntax not understood |
| 69 | </body> | Syntax not understood |
| 71 | </html> | Syntax not understood |
To appear in search results, crawlers need access to your app.