Skip to content
Audit Complete

Results for https://ucoz.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 20:27 UTC
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

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Reasonable footprint with room for optimization.

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.

How the composite score is calculated

How you compare

Bootstrap · 621 peers
You 72
·
Avg 73
At average
0 50 100
Better than 28% of Bootstrap sites See full Bootstrap benchmark →
Font Awesome · 391 peers
You 72
·
Avg 73
At average
0 50 100
Better than 28% of Font Awesome sites See full Font Awesome benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

11 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fucoz.com)](https://beavercheck.com/results/2a651642-4ba0-4868-8152-b17a868cc6f3)
<a href="https://beavercheck.com/results/2a651642-4ba0-4868-8152-b17a868cc6f3"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fucoz.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fucoz.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

1 critical 7 warning

8 barrier(s) likely increasing bounce by ~27%.

Speed (2)

Page takes 11.6s to load

+12% bounce

Users abandon at ~3s — you're 9.1s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 373ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (3)

11 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

AED 1,125 investment → AED 11,162/month returns + AED 5,000,000 risk avoided

Payback period: < 1 month First-year ROI: +11806%

Investment

AED 1,125

4h · 5 findings

Monthly returns

AED 11,162 /mo

~AED 133,948 / year

  • Conversions recovered AED 11,161
  • Bandwidth savings AED 1.25

Regulatory risk avoided

AED 5,000,000

if kept compliant

  • UAE PDPL AED 5,000,000

Payback period

0 12mo 24mo

AED 375 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

د.إ1,125

4.5 developer hours at د.إ250/hr

Based on UAE rates (د.إ250/hr)

Quick wins
د.إ375 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
د.إ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

AED 416,668 / month at risk

~AED 5,000,015 / year if left unfixed

Compliance Risk

AED 5,000,000

UAE PDPL
  • No privacy policy link detected
    UAE PDPL: AED 10,000 – AED 5,000,000
  • Trackers detected but no cookie policy found
    UAE PDPL: AED 10,000 – AED 5,000,000
  • Trackers detected but no privacy policy found
    UAE PDPL: AED 10,000 – AED 5,000,000

Bandwidth Waste

AED 1.25 /mo

4226.1 MB/mo × 0.296 AED/GB

  • Optimize transfer: save ~423 KB per page load
    Saves AED 1.25/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

54
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
78
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.
100
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.

4.47 s

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

11.56 s

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

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

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

11.56 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.ucoz.com/ucoz/v3/images/for-bot-en-1@2x.webp0.0 ms450.6 KiB
www.ucoz.com/ucoz/v3/js/jquery.min.js0.0 ms93.8 KiB
mc.yandex.ru/metrika/tag.js3600.0 s85.4 KiB
www.ucoz.com/ucoz/v3/images/ukit_image.webp0.0 ms31.9 KiB
www.ucoz.com/ucoz/v3/js/jquery.fullPage.js0.0 ms31.5 KiB
www.ucoz.com/ucoz/v3/js/bootstrap-select.min.js0.0 ms29.4 KiB
www.ucoz.com/ucoz/v3/js/bootstrap.min.js0.0 ms27.2 KiB
www.ucoz.com/ucoz/v3/js/owl.carousel.min.js0.0 ms22.8 KiB
www.ucoz.com/ucoz/v3/css/style.css0.0 ms17.5 KiB
www.ucoz.com/ucoz/v3/css/style.css?v=10.0 ms17.5 KiB
www.ucoz.com/ucoz/v3/css/bootstrap.min.css0.0 ms16.6 KiB
cdn.mouseflow.com/projects/14db124b-35ec-4c89-a819-e8f0d680ec8c.js86400.0 s18.4 KiB
www.ucoz.com/ucoz/v3/js/lazysizes.min.js0.0 ms6.7 KiB
www.ucoz.com/ucoz/v3/js/sidemenu.js0.0 ms6.4 KiB
www.ucoz.com/ucoz/v3/css/style_new.css0.0 ms5.8 KiB
www.ucoz.com/ucoz/v3/css/font-awesome.min.css0.0 ms5.5 KiB
www.ucoz.com/ucoz/v3/css/style2.css0.0 ms5.3 KiB
www.ucoz.com/ucoz/v3/css/style_v5.css?v=30.0 ms5.3 KiB
www.ucoz.com/ucoz/v3/js/jquery.slimscroll.min.js0.0 ms4.6 KiB
www.ucoz.com/ucoz/v3/css/bootstrap-theme.min.css0.0 ms2.3 KiB
www.ucoz.com/ucoz/v3/js/mainPage.js0.0 ms1.9 KiB
www.ucoz.com/ucoz/v3/css/bootstrap-select.min.css0.0 ms1.6 KiB
www.ucoz.com/ucoz/v3/js/ftlight.js0.0 ms1.4 KiB
www.ucoz.com/ucoz/v3/css/owl.transitions.css0.0 ms898 B
www.ucoz.com/ucoz/v3/css/owl.carousel.css0.0 ms721 B
www.ucoz.com/ucoz/v3/images/logo-ukit.png1728000.0 s4.2 KiB
mc.yandex.com/metrika/advert.gif?t=gdpr(14)ti(4)3600.0 s375 B
www.ucoz.com/ucoz/v3/img/logo-ucoz.svg1728000.0 s2.0 KiB
/sync_cookie_image_decide?cid=18794098&scid=533734e9-cd8e...0.0 ms185 B
www.ucoz.com/ucoz/v3/img/arrow.svg1728000.0 s976 B
/sync_cookie_image_decide_secondary?cid=18794098&scid=9e2...0.0 ms79 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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:28.116 source:map[column:6379 line:2 type:source-location url:https://www.ucoz.com/ucoz/v3/js/lazysizes.min.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:28.116 source:map[column:2806 line:1 type:source-location url:https://www.ucoz.com/ucoz/v3/js/lazysizes.min.js urlProvider:network]] map[reflowTime:0.353 source:map[column:31201 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:4.218 source:map[column:56773 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.104 source:map[column:60858 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.322 source:map[column:58723 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.152 source:map[column:59090 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.358 source:map[column:59266 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.21 source:map[column:59342 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.232 source:map[column:44 line:183 type:source-location url:https://www.ucoz.com/ucoz/v3/js/sidemenu.js urlProvider:network]] map[reflowTime:0.211 source:map[column:23344 line:2 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.fullPage.js urlProvider:network]] map[reflowTime:0.293 source:map[column:94297 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.364 source:map[column:62406 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.087 source:map[column:60872 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.341 source:map[column:87549 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]]]

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.

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 841 ms
URLTime Spent
ucoz.com/841 ms
www.ucoz.com/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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 180 ms 32.5 KiB
URLTransfer SizeEst Savings
www.ucoz.com/ucoz/v3/css/style.css?v=117.2 KiB16.5 KiB
www.ucoz.com/ucoz/v3/css/bootstrap.min.css16.3 KiB16.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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.ucoz.com/5.1 s19 ms5.0 ms
mc.yandex.ru/metrika/tag.js1.8 s1.6 s26 ms
Unattributable605 ms18 ms0.0 ms
www.ucoz.com/ucoz/v3/js/jquery.min.js443 ms274 ms7.5 ms
www.googletagmanager.com/gtag/js?id=G-VDG4M9XEXC&cx=c&gtm=4e64k0254 ms195 ms58 ms
www.googletagmanager.com/gtm.js?id=GTM-59QRNH145 ms114 ms28 ms
www.ucoz.com/ucoz/v3/js/lazysizes.min.js142 ms18 ms0.6 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Other3.2 s
Script Evaluation2.3 s
Style & Layout1.9 s
Rendering986 ms
Script Parsing & Compilation141 ms
Parse HTML & CSS73 ms
Garbage Collection57 ms

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
uKit group div.footer-bar > div.row > div.column-logo > img.lazyloaded
www.ucoz.com/ucoz/v3/images/logo-ukit.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
Improve image delivery
LCP breakdown
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,376 KiB
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 7 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 80 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
LCP request discovery
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.

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
body > button.menu-btn-v5 body > button.menu-btn-v5

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.choice-container > header.choice-header > div.choice-actions > a.choice-btn div.choice-container > header.choice-header > div.choice-actions > a.choice-btn

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
Website Builder for Business. Start from Scratch or Choose a Template div.card-wrapper > div.card > div.card-body > p
LLC Ucoz Media div.row > div.column-logo > div.copy-subtitle > p
Copyright © 2005-2026 div.row > div.column-logo > div.copy-subtitle > p

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-hidden="true"]` is not present on the document `<body>`
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-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
`[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 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
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
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.
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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: net::ERR_TIMED_OUT
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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
robots.txt is valid
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

94
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
72
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.

976 ms

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

1.40 s

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

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

976 ms

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

2.52 s

Detailed Report

Audit breakdown by category with detailed findings.

94

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.ucoz.com/ucoz/v3/images/for-me-en-3.webp0.0 ms180.6 KiB
www.ucoz.com/ucoz/v3/images/for-bot-en-1.webp0.0 ms156.5 KiB
www.ucoz.com/ucoz/v3/images/for-me-en-1.webp0.0 ms103.6 KiB
www.ucoz.com/ucoz/v3/js/jquery.min.js0.0 ms93.8 KiB
www.ucoz.com/ucoz/v3/img/ukit_background.svg1728000.0 s855.1 KiB
www.ucoz.com/ucoz/v3/images/for-me-en-2.webp0.0 ms80.6 KiB
www.ucoz.com/ucoz/v3/fonts/fontawesome-webfont.woff2?v=4.3.00.0 ms75.6 KiB
mc.yandex.ru/metrika/tag.js3600.0 s85.4 KiB
www.ucoz.com/ucoz/v3/images/ukit_image.webp0.0 ms31.9 KiB
www.ucoz.com/ucoz/v3/js/jquery.fullPage.js0.0 ms31.5 KiB
www.ucoz.com/ucoz/v3/js/bootstrap-select.min.js0.0 ms29.4 KiB
www.ucoz.com/ucoz/v3/js/bootstrap.min.js0.0 ms27.2 KiB
www.ucoz.com/ucoz/v3/js/owl.carousel.min.js0.0 ms22.8 KiB
www.ucoz.com/ucoz/v3/css/style.css0.0 ms17.5 KiB
www.ucoz.com/ucoz/v3/css/style.css?v=10.0 ms17.5 KiB
www.ucoz.com/ucoz/v3/css/bootstrap.min.css0.0 ms16.6 KiB
www.ucoz.com/ucoz/v3/images/iphone-min.png1728000.0 s100.1 KiB
cdn.mouseflow.com/projects/14db124b-35ec-4c89-a819-e8f0d680ec8c.js86400.0 s18.3 KiB
www.ucoz.com/ucoz/v3/js/lazysizes.min.js0.0 ms6.7 KiB
www.ucoz.com/ucoz/v3/js/sidemenu.js0.0 ms6.4 KiB
www.ucoz.com/ucoz/v3/images/divlybackgr.jpg1728000.0 s62.0 KiB
www.ucoz.com/ucoz/v3/css/style_new.css0.0 ms5.8 KiB
www.ucoz.com/ucoz/v3/css/font-awesome.min.css0.0 ms5.5 KiB
www.ucoz.com/ucoz/v3/css/style2.css0.0 ms5.3 KiB
www.ucoz.com/ucoz/v3/css/style_v5.css?v=30.0 ms5.3 KiB
www.ucoz.com/ucoz/v3/js/jquery.slimscroll.min.js0.0 ms4.6 KiB
www.ucoz.com/ucoz/v3/css/bootstrap-theme.min.css0.0 ms2.3 KiB
www.ucoz.com/ucoz/v3/js/mainPage.js0.0 ms1.9 KiB
www.ucoz.com/ucoz/v3/css/bootstrap-select.min.css0.0 ms1.6 KiB
www.ucoz.com/ucoz/v3/js/ftlight.js0.0 ms1.4 KiB
www.ucoz.com/ucoz/v3/css/owl.transitions.css0.0 ms898 B
www.ucoz.com/ucoz/v3/css/owl.carousel.css0.0 ms721 B
www.ucoz.com/ucoz/v3/images/laptop-clear.png1728000.0 s7.1 KiB
www.ucoz.com/ucoz/v3/images/laptop-plate-transp.png1728000.0 s3.7 KiB
www.ucoz.com/ucoz/v3/images/ucoz-header.svg1728000.0 s2.6 KiB
www.ucoz.com/ucoz/v3/img/logo-ucoz.svg1728000.0 s2.0 KiB
www.ucoz.com/ucoz/v3/img/business_features.svg1728000.0 s1.1 KiB
mc.yandex.com/metrika/advert.gif?t=gdpr(14)ti(4)3600.0 s139 B
www.ucoz.com/ucoz/v3/images/pad-bg.svg1728000.0 s995 B
www.ucoz.com/ucoz/v3/img/arrow.svg1728000.0 s976 B
www.ucoz.com/ucoz/v3/img/ukit_back_effect2.svg1728000.0 s917 B
www.ucoz.com/ucoz/v3/img/ukit_back_effect1.svg1728000.0 s906 B
www.ucoz.com/ucoz/v3/img/code_features.svg1728000.0 s903 B
/sync_cookie_image_decide_secondary?cid=18794098&scid=a9d...0.0 ms79 B
/sync_cookie_image_decide?cid=18794098&scid=d73f0dbc-302d...0.0 ms67 B
www.ucoz.com/ucoz/v3/img/play_icon.svg1728000.0 s646 B
www.ucoz.com/ucoz/v3/images/i_downarrows.png1728000.0 s577 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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:31.024 source:map[column:30177 line:1 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.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.83 source:map[column:31201 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:8.207 source:map[column:56773 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.859 source:map[column:60858 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.263 source:map[column:58723 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.114 source:map[column:59090 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.254 source:map[column:59266 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.206 source:map[column:59342 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.254 source:map[column:44 line:183 type:source-location url:https://www.ucoz.com/ucoz/v3/js/sidemenu.js urlProvider:network]] map[reflowTime:1.605 source:map[column:95195 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.135 source:map[column:23344 line:2 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.fullPage.js urlProvider:network]] map[reflowTime:0.638 source:map[column:94297 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:0.346 source:map[column:60872 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.js urlProvider:network]] map[reflowTime:2.313 source:map[column:87549 line:0 type:source-location url:https://www.ucoz.com/ucoz/v3/js/jquery.min.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
tg-bot-example div.owl-wrapper > div.owl-item > div.active > img
www.ucoz.com/ucoz/v3/images/for-bot-en-1.webp156.2 KiB127.5 KiB

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.ucoz.com/http/1.1
www.ucoz.com/ucoz/v3/css/bootstrap.min.csshttp/1.1
www.ucoz.com/ucoz/v3/css/style.csshttp/1.1
www.ucoz.com/ucoz/v3/css/style2.csshttp/1.1
www.ucoz.com/ucoz/v3/css/font-awesome.min.csshttp/1.1
www.ucoz.com/ucoz/v3/css/style.css?v=1http/1.1
www.ucoz.com/ucoz/v3/css/style_new.csshttp/1.1
www.ucoz.com/ucoz/v3/css/style_v5.css?v=3http/1.1
www.ucoz.com/ucoz/v3/css/owl.carousel.csshttp/1.1
www.ucoz.com/ucoz/v3/css/owl.transitions.csshttp/1.1
www.ucoz.com/ucoz/v3/css/bootstrap-theme.min.csshttp/1.1
www.ucoz.com/ucoz/v3/css/bootstrap-select.min.csshttp/1.1
www.ucoz.com/ucoz/v3/images/ukit_image.webphttp/1.1
www.ucoz.com/ucoz/v3/images/for-bot-en-1.webphttp/1.1
www.ucoz.com/ucoz/v3/js/jquery.min.jshttp/1.1
www.ucoz.com/ucoz/v3/js/jquery.slimscroll.min.jshttp/1.1
www.ucoz.com/ucoz/v3/js/jquery.fullPage.jshttp/1.1
www.ucoz.com/ucoz/v3/js/lazysizes.min.jshttp/1.1
www.ucoz.com/ucoz/v3/js/sidemenu.jshttp/1.1
www.ucoz.com/ucoz/v3/js/mainPage.jshttp/1.1
www.ucoz.com/ucoz/v3/js/bootstrap.min.jshttp/1.1
www.ucoz.com/ucoz/v3/js/bootstrap-select.min.jshttp/1.1
www.ucoz.com/ucoz/v3/js/ftlight.jshttp/1.1
www.ucoz.com/ucoz/v3/js/owl.carousel.min.jshttp/1.1
www.ucoz.com/ucoz/v3/images/payments.svg?v=9#mastercardhttp/1.1
www.ucoz.com/ucoz/v3/img/logo-ucoz.svghttp/1.1
www.ucoz.com/ucoz/v3/img/arrow.svghttp/1.1
www.ucoz.com/ucoz/v3/images/pad-bg.svghttp/1.1
www.ucoz.com/ucoz/v3/images/i_downarrows.pnghttp/1.1
www.ucoz.com/ucoz/v3/img/ukit_background.svghttp/1.1
www.ucoz.com/ucoz/v3/img/ukit_back_effect1.svghttp/1.1
www.ucoz.com/ucoz/v3/img/ukit_back_effect2.svghttp/1.1
www.ucoz.com/ucoz/v3/img/play_icon.svghttp/1.1
www.ucoz.com/ucoz/v3/img/code_features.svghttp/1.1
www.ucoz.com/ucoz/v3/img/business_features.svghttp/1.1
www.ucoz.com/ucoz/v3/images/laptop-clear.pnghttp/1.1
www.ucoz.com/ucoz/v3/images/laptop-plate-transp.pnghttp/1.1
www.ucoz.com/ucoz/v3/images/iphone-min.pnghttp/1.1
www.ucoz.com/ucoz/v3/images/divlybackgr.jpghttp/1.1
www.ucoz.com/ucoz/v3/fonts/fontawesome-webfont.woff2?v=4.3.0http/1.1
www.ucoz.com/ucoz/v3/images/ucoz-header.svghttp/1.1
www.ucoz.com/ucoz/v3/images/for-me-en-1.webphttp/1.1
www.ucoz.com/ucoz/v3/images/for-me-en-2.webphttp/1.1
www.ucoz.com/ucoz/v3/images/for-me-en-3.webphttp/1.1
www.ucoz.com/favicon1.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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 290 ms
URLTime Spent
ucoz.com/290 ms
www.ucoz.com/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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 60 ms 30.3 KiB
URLTransfer SizeEst Savings
www.ucoz.com/ucoz/v3/css/bootstrap.min.css16.3 KiB15.9 KiB
www.ucoz.com/ucoz/v3/css/style.css?v=117.2 KiB14.5 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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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
UCOZ div.top-part > div.box > p.lead > img.lazyloaded
www.ucoz.com/ucoz/v3/images/ucoz-header.svg
uCalc div.side-left > div#image-ucalc > a > img.lazyload
uKit group div.footer-bar > div.row > div.column-logo > img.lazyload

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Optimize viewport for mobile
Max Potential First Input Delay 60 ms
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,589 KiB
User Timing marks and measures 7 user timings
JavaScript execution time 0.5 s
Minimizes main-thread work 1.0 s
Avoid long main-thread tasks 1 long task found
Avoid non-composited animations 6 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 70 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 80 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
72

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
body > button.menu-btn-v5 body > button.menu-btn-v5

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.owl-wrapper > div.owl-item > div.item > a div.owl-wrapper > div.owl-item > div.item > a
div.owl-wrapper > div.owl-item > div.item > a div.owl-wrapper > div.owl-item > div.item > a
div.owl-wrapper > div.owl-item > div.item > a div.owl-wrapper > div.owl-item > div.item > a
div.business-container > div.info-container > div.social-list > a div.business-container > div.info-container > div.social-list > a
div.business-container > div.info-container > div.social-list > a div.business-container > div.info-container > div.social-list > a
div.owl-wrapper > div.owl-item > div.active > a div.owl-wrapper > div.owl-item > div.active > a
div.owl-wrapper > div.owl-item > div.item > a div.owl-wrapper > div.owl-item > div.item > a
div.owl-wrapper > div.owl-item > div.item > a div.owl-wrapper > div.owl-item > div.item > a
div.owl-wrapper > div.owl-item > div.item > a div.owl-wrapper > div.owl-item > div.item > a
div.owl-wrapper > div.owl-item > div.item > a div.owl-wrapper > div.owl-item > div.item > a

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
Website Builder for Business. Start from Scratch or Choose a Template div.card-wrapper > div.card > div.card-body > p
Landing Page div.card > div.card-body > ul.features-list > li
Fast Setup div.card > div.card-body > ul.features-list > li
Online Store div.card > div.card-body > ul.features-list > li
Business Card Site div.card > div.card-body > ul.features-list > li

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Make a Choice div#fp-nav > ul.white > li > a.active
uCoz div#fp-nav > ul.white > li > a
uKit div#fp-nav > ul.white > li > a
uShop div#fp-nav > ul.white > li > a
uCalc div#fp-nav > ul.white > li > a
Web Bots div#fp-nav > ul.white > li > a
Divly div#fp-nav > ul.white > li > a
About Us div#fp-nav > ul.white > li > a

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
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Identical links have the same purpose.
`[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 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
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
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.
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.
92

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
tg-bot-example div.owl-wrapper > div.owl-item > div.active > img
www.ucoz.com/ucoz/v3/images/for-bot-en-1.webp290 x 581 (0.50)290 x 608 (0.48)

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
Failed to load resource: net::ERR_TIMED_OUT
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
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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
robots.txt is valid
Document has a valid `rel=canonical`

Send Feedback