Skip to content
http://www.elkot.info

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.

95

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
www.elkot.info/images/default3_08.png0.0 ms86.6 KiB
www.google-analytics.com/ga.js7200.0 s17.4 KiB
www.elkot.info/elkot.css0.0 ms5.3 KiB
www.elkot.info/images/default2_02.png0.0 ms3.1 KiB
www.elkot.info/images/default2_14.png0.0 ms545 B
www.elkot.info/images/default2_23.png0.0 ms470 B
www.elkot.info/images/default2_03.png0.0 ms461 B
www.elkot.info/images/default2_01.png0.0 ms450 B
www.elkot.info/images/default2_18.png0.0 ms448 B
www.elkot.info/images/default2_07.png0.0 ms446 B
www.elkot.info/images/default2_17.png0.0 ms435 B
www.elkot.info/images/default2_10.png0.0 ms431 B
www.elkot.info/images/default2_16.png0.0 ms430 B
www.elkot.info/images/default2_04.png0.0 ms418 B
www.elkot.info/images/default2_19.png0.0 ms417 B
www.elkot.info/images/default2_06.png0.0 ms415 B
www.elkot.info/images/default2_15.png0.0 ms413 B
www.elkot.info/images/default2_13.png0.0 ms412 B
www.elkot.info/images/default2_22.png0.0 ms408 B
www.elkot.info/images/default2_21.png0.0 ms408 B
www.elkot.info/images/default2_11.png0.0 ms405 B
www.elkot.info/images/default2_12.png0.0 ms405 B
www.elkot.info/images/default2_20.png0.0 ms404 B
www.elkot.info/images/spacer.gif0.0 ms319 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.

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-0-IMG
nodeLabel: tbody > tr > td > img
path: 1,HTML,1,BODY,2,TABLE,0,TBODY,3,TR,2,TD,0,IMG
selector: tbody > tr > td > img
snippet: <img src="images/default3_08.png" width="622" height="391" alt="">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.elkot.info/http/1.1
www.elkot.info/elkot.csshttp/1.1
www.elkot.info/images/default2_01.pnghttp/1.1
www.elkot.info/images/default2_02.pnghttp/1.1
www.elkot.info/images/default2_03.pnghttp/1.1
www.elkot.info/images/spacer.gifhttp/1.1
www.elkot.info/images/default2_04.pnghttp/1.1
www.elkot.info/images/default2_06.pnghttp/1.1
www.elkot.info/images/default2_07.pnghttp/1.1
www.elkot.info/images/default3_08.pnghttp/1.1
www.elkot.info/images/default2_10.pnghttp/1.1
www.elkot.info/images/default2_11.pnghttp/1.1
www.elkot.info/images/default2_12.pnghttp/1.1
www.elkot.info/images/default2_13.pnghttp/1.1
www.elkot.info/images/default2_15.pnghttp/1.1
www.elkot.info/images/default2_16.pnghttp/1.1
www.elkot.info/images/default2_17.pnghttp/1.1
www.elkot.info/images/default2_18.pnghttp/1.1
www.elkot.info/images/default2_19.pnghttp/1.1
www.elkot.info/images/default2_20.pnghttp/1.1
www.elkot.info/images/default2_21.pnghttp/1.1
www.elkot.info/images/default2_22.pnghttp/1.1
www.elkot.info/images/default2_14.pnghttp/1.1
www.elkot.info/images/default2_23.pnghttp/1.1
www.elkot.info/favicon.icohttp/1.1

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
www.elkot.info/elkot.css5.3 KiB206 ms

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
tbody > tr > td > img tbody > tr > td > img
www.elkot.info/images/default3_08.png86.3 KiB46.7 KiB

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

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages containing plugins are not currently eligible for back/forward cache.Pending browser support

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 476 ms
URLTime Spent
www.elkot.info/326 ms
www.elkot.info/150 ms
www.elkot.info/0.0 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Optimize viewport for mobile
●Time to Interactive 1.3 s
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 134 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.1 s
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 170 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 170 ms
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
○Avoid large layout shifts
78

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
New Designs! li > a > blink > font

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●Document has a `<title>` element
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●The page contains a heading, skip link, or landmark region
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○`<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
○Heading elements appear in a sequentially-descending order
○`<html>` element has a valid value for its `[lang]` attribute
○`<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">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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.
70

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.elkot.info/Allowed
www.elkot.info/elkot.cssAllowed
www.elkot.info/images/default2_01.pngAllowed
www.elkot.info/images/default2_02.pngAllowed
www.elkot.info/images/default2_03.pngAllowed
www.elkot.info/images/spacer.gifAllowed
www.elkot.info/images/default2_04.pngAllowed
www.elkot.info/images/default2_06.pngAllowed
www.elkot.info/images/default2_07.pngAllowed
www.elkot.info/images/default3_08.pngAllowed
www.elkot.info/images/default2_10.pngAllowed
www.elkot.info/images/default2_11.pngAllowed
www.elkot.info/images/default2_12.pngAllowed
www.elkot.info/images/default2_13.pngAllowed
www.elkot.info/images/default2_15.pngAllowed
www.elkot.info/images/default2_16.pngAllowed
www.elkot.info/images/default2_17.pngAllowed
www.elkot.info/images/default2_18.pngAllowed
www.elkot.info/images/default2_19.pngAllowed
www.elkot.info/images/default2_20.pngAllowed
www.elkot.info/images/default2_21.pngAllowed
www.elkot.info/images/default2_22.pngAllowed
www.elkot.info/images/default2_14.pngAllowed
www.elkot.info/images/default2_23.pngAllowed
www.elkot.info/favicon.icoAllowed

Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

SourceDescription
www.elkot.info/favicon.ico
Failed to load resource: the server responded with a status of 404 (Not Found)
●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
●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
○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
2Disallow: createUser.aspx/Pattern should either be empty, start with "/" or "*"

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