There were issues affecting this run of Lighthouse:

The page may not be loading as expected because your test URL (https://օք.հայ/) was redirected to https://www.օք.հայ/?m=1. Try testing the second URL directly.

Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.

0–49 50–89 90–100

First Contentful Paint

3.8 s

First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.

Largest Contentful Paint

6.0 s

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

Total Blocking Time

100 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.

Cumulative Layout Shift

0.256

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

Speed Index

3.8 s

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

Avoid large layout shifts 4 layout shifts found

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS

Element	Layout shift score
HOME welcome @manudavidos Hey! You can call me David :) Welcome to my half-blo… <div class="container sp_sidebar">	0.192
HOME welcome @manudavidos Hey! You can call me David :) Welcome to my half-blo… <div class="container sp_sidebar">	0.064
@manudavidos <h2>	0.000
Microsoft Certifi… <span id="badge-name">	0.000

Avoid multiple page redirects Potential savings of 1,570 ms

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP

URL	Time Spent
https://xn--ybbb.xn--y9a3aq	750 ms
https://www.xn--ybbb.xn--y9a3aq	820 ms
/?m=1 (www.xn--ybbb.xn--y9a3aq)	0 ms

Largest Contentful Paint element 5,970 ms

This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP

Element
about Me <img alt="about Me" src="https://blogger.googleusercontent.com/img/a/AVvXsEiuAVoOTTl99SNhvCOrMh8Dtp…" style="border-radius: 50px; height: auto; width: 300px;">

Phase	% of LCP	Timing
TTFB	11%	670 ms
Load Delay	15%	910 ms
Load Time	71%	4,240 ms
Render Delay	2%	150 ms

Properly size images Potential savings of 263 KiB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.FCPLCP

	URL	Resource Size	Potential Savings
googleusercontent.com		296.6 KiB	262.6 KiB
about Me <img alt="about Me" src="https://blogger.googleusercontent.com/img/a/AVvXsEiuAVoOTTl99SNhvCOrMh8Dtp…" style="border-radius: 50px; height: auto; width: 300px;">	…a/AVvXsEiuA… (blogger.googleusercontent.com)	289.5 KiB	258.3 KiB
manudavidos@օք.հայ:$ <img alt="manudavidos@օք.հայ:$" height="134px; " id="Header1_headerimg" src="https://blogger.googleusercontent.com/img/a/AVvXsEgUorRicUOzNYW5nSlouevXIN…" width="892px; ">	…a/AVvXsEgUo…=s892 (blogger.googleusercontent.com)	7.1 KiB	4.3 KiB

Serve images in next-gen formats Potential savings of 145 KiB

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.FCPLCP

	URL	Resource Size	Potential Savings
googleusercontent.com		289.5 KiB	136.7 KiB
about Me <img alt="about Me" src="https://blogger.googleusercontent.com/img/a/AVvXsEiuAVoOTTl99SNhvCOrMh8Dtp…" style="border-radius: 50px; height: auto; width: 300px;">	…a/AVvXsEiuA… (blogger.googleusercontent.com)	289.5 KiB	136.7 KiB
credly.com		28.9 KiB	8.5 KiB
	…c3ab66f8-…/CERT-Expe….png (images.credly.com)	28.9 KiB	8.5 KiB

Preconnect to required origins Potential savings of 330 ms

Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP

URL	Potential Savings
Bootstrap CDN cdn	330 ms
https://maxcdn.bootstrapcdn.com	330 ms
Google Analytics analytics	210 ms
https://www.google-analytics.com	210 ms

Eliminate render-blocking resources Potential savings of 300 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.FCPLCP

URL	Transfer Size	Potential Savings
Bootstrap CDN cdn	7.0 KiB	800 ms
…css/font-awesome.min.css (maxcdn.bootstrapcdn.com)	7.0 KiB	800 ms
jQuery CDN cdn	6.0 KiB	990 ms
/jquery-migrate-1.2.1.js (code.jquery.com)	6.0 KiB	990 ms
Google CDN cdn	33.4 KiB	1,250 ms
…1.11.0/jquery.min.js (ajax.googleapis.com)	33.4 KiB	1,250 ms
Google Fonts cdn	2.8 KiB	910 ms
/css?family=Bad+Script%7CRaleway:400,500,600,700,300%7CLora:400 (fonts.googleapis.com)	1.8 KiB	760 ms
/css?family=Montserrat%3A400&subset=latin&ver=143… (fonts.googleapis.com)	1.0 KiB	150 ms
Blogger hosting	6.9 KiB	760 ms
…widgets/55013136-widget_css_bundle.css (www.blogger.com)	6.9 KiB	760 ms

Reduce unused JavaScript Potential savings of 87 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.FCPLCP

URL	Transfer Size	Potential Savings
Google Tag Manager tag-manager	120.1 KiB	49.1 KiB
/gtag/js?id=G-9WL5L35ECD (www.googletagmanager.com)	120.1 KiB	49.1 KiB
Blogger hosting	50.5 KiB	38.3 KiB
…widgets/280…-widgets.js (www.blogger.com)	50.5 KiB	38.3 KiB

Image elements do not have explicit width and height

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

	URL
googleusercontent.com
about Me <img alt="about Me" src="https://blogger.googleusercontent.com/img/a/AVvXsEiuAVoOTTl99SNhvCOrMh8Dtp…" style="border-radius: 50px; height: auto; width: 300px;">	…a/AVvXsEiuA… (blogger.googleusercontent.com)

Minify JavaScript Potential savings of 2 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.FCPLCP

URL	Transfer Size	Potential Savings
jQuery CDN cdn	5.7 KiB	2.1 KiB
/jquery-migrate-1.2.1.js (code.jquery.com)	5.7 KiB	2.1 KiB

Serve static assets with an efficient cache policy 2 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

URL	Cache TTL	Transfer Size
googleusercontent.com		297 KiB
…a/AVvXsEiuA… (blogger.googleusercontent.com)	1d	290 KiB
…a/AVvXsEgUo…=s892 (blogger.googleusercontent.com)	1d	7 KiB

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.

URL	Potential Savings
Google Fonts cdn	990 ms
…v19/wlpogwHKF….woff2 (fonts.gstatic.com)	350 ms
…v24/S6uyw4BMU….woff2 (fonts.gstatic.com)	320 ms
…v24/S6u8w4BMU….woff2 (fonts.gstatic.com)	320 ms
Bootstrap CDN cdn	70 ms
…fonts/fontawesome-webfont.woff2?v=4.6.3 (maxcdn.bootstrapcdn.com)	70 ms

Avoid document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().

Source
/?m=1:3295:3497 (www.xn--ybbb.xn--y9a3aq)

Minimize third-party usage Third-party code blocked the main thread for 190 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT

Third-Party	Transfer Size	Main-Thread Blocking Time
Google Tag Manager tag-manager	121 KiB	165 ms
/gtag/js?id=G-9WL5L35ECD (www.googletagmanager.com)	121 KiB	165 ms
Google CDN cdn	33 KiB	22 ms
…1.11.0/jquery.min.js (ajax.googleapis.com)	33 KiB	22 ms
credly.com	57 KiB	4 ms
/embedded_badge/5cac4c04-e5e5-4fce-a1e6-f186b466db8a (www.credly.com)	2 KiB	4 ms
…c3ab66f8-…/CERT-Expe….png (images.credly.com)	29 KiB	0 ms
…embed/credly-logo-gray-19b614a….svg (cdn.credly.com)	20 KiB	0 ms
…utilities/clamp-f504f8b….js (cdn.credly.com)	2 KiB	0 ms
/assets/embed-b4eebb4….css (cdn.credly.com)	1 KiB	0 ms
…utilities/embed.js (cdn.credly.com)	1 KiB	0 ms
/stats/interaction (stats.credly.com)	0 KiB	0 ms
/embedded_badge/809f7ebb-2b31-492a-be42-4f25c51ce296 (www.credly.com)	0 KiB	0 ms
Blogger hosting	58 KiB	1 ms
…widgets/280…-widgets.js (www.blogger.com)	51 KiB	1 ms
…widgets/55013136-widget_css_bundle.css (www.blogger.com)	7 KiB	0 ms
/dyn-css/authorization.css?targetBlogID=… (www.blogger.com)	1 KiB	0 ms
googleusercontent.com	297 KiB	0 ms
…a/AVvXsEiuA… (blogger.googleusercontent.com)	290 KiB	0 ms
…a/AVvXsEgUo…=s892 (blogger.googleusercontent.com)	7 KiB	0 ms
Bootstrap CDN cdn	78 KiB	0 ms
…fonts/fontawesome-webfont.woff2?v=4.6.3 (maxcdn.bootstrapcdn.com)	71 KiB	0 ms
…css/font-awesome.min.css (maxcdn.bootstrapcdn.com)	7 KiB	0 ms
Google Fonts cdn	49 KiB	0 ms
…v19/wlpogwHKF….woff2 (fonts.gstatic.com)	17 KiB	0 ms
…v24/S6u8w4BMU….woff2 (fonts.gstatic.com)	15 KiB	0 ms
…v24/S6uyw4BMU….woff2 (fonts.gstatic.com)	14 KiB	0 ms
/css?family=Bad+Script%7CRaleway:400,500,600,700,300%7CLora:400 (fonts.googleapis.com)	2 KiB	0 ms
/css?family=Montserrat%3A400&subset=latin&ver=143… (fonts.googleapis.com)	1 KiB	0 ms
/css?family=… (fonts.googleapis.com)	1 KiB	0 ms
JSDelivr CDN cdn	10 KiB	0 ms
…1.5.5/slick.min.js (cdn.jsdelivr.net)	10 KiB	0 ms
jQuery CDN cdn	6 KiB	0 ms
/jquery-migrate-1.2.1.js (code.jquery.com)	6 KiB	0 ms
Google Analytics analytics	0 KiB	0 ms
/g/collect?v=… (www.google-analytics.com)	0 KiB	0 ms

Avoid long main-thread tasks 6 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT

URL	Start Time	Duration
Google Tag Manager tag-manager		340 ms
/gtag/js?id=G-9WL5L35ECD (www.googletagmanager.com)	6,339 ms	172 ms
/gtag/js?id=G-9WL5L35ECD (www.googletagmanager.com)	6,246 ms	93 ms
/gtag/js?id=G-9WL5L35ECD (www.googletagmanager.com)	6,540 ms	75 ms
Unattributable		95 ms
/?m=1 (www.xn--ybbb.xn--y9a3aq)	1,722 ms	95 ms
credly.com		54 ms
/embedded_badge/5cac4c04-e5e5-4fce-a1e6-f186b466db8a (www.credly.com)	3,775 ms	54 ms
Blogger hosting		53 ms
…widgets/280…-widgets.js (www.blogger.com)	5,057 ms	53 ms

Avoid chaining critical requests 12 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.

Maximum critical path latency: 923.045 ms

Initial Navigation

https://xn--ybbb.xn--y9a3aq

https://www.xn--ybbb.xn--y9a3aq

/?m=1

(www.xn--ybbb.xn--y9a3aq)

…widgets/55013136-widget_css_bundle.css

(www.blogger.com)

- 28.313 ms, 6.86 KiB

…css/font-awesome.min.css

(maxcdn.bootstrapcdn.com)

…fonts/fontawesome-webfont.woff2?v=4.6.3

(maxcdn.bootstrapcdn.com)

- 66.836 ms, 70.83 KiB

/css?family=Bad+Script%7CRaleway:400,500,600,700,300%7CLora:400

(fonts.googleapis.com)

- 30.834 ms, 1.80 KiB

/css?family=Montserrat%3A400&subset=latin&ver=143…

(fonts.googleapis.com)

- 25.027 ms, 0.96 KiB

/css?family=…

(fonts.googleapis.com)

…v19/wlpogwHKF….woff2

(fonts.gstatic.com)

- 354.923 ms, 17.11 KiB

…v24/S6uyw4BMU….woff2

(fonts.gstatic.com)

- 320.693 ms, 13.78 KiB

…v24/S6u8w4BMU….woff2

(fonts.gstatic.com)

- 318.281 ms, 15.00 KiB

/dyn-css/authorization.css?targetBlogID=…

(www.blogger.com)

- 15.038 ms, 0.08 KiB

…1.11.0/jquery.min.js

(ajax.googleapis.com)

- 318.613 ms, 33.39 KiB

/jquery-migrate-1.2.1.js

(code.jquery.com)

…posts/summary?max-results=…

(www.xn--ybbb.xn--y9a3aq)

- 72.241 ms, 0.93 KiB

…1.5.5/slick.min.js

(cdn.jsdelivr.net)

- 345.405 ms, 9.83 KiB

…widgets/280…-widgets.js

(www.blogger.com)

- 9.248 ms, 50.67 KiB

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

Show Hide

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.FCPLCP

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.FCPLCP

Reduce unused CSS

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

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.FCPLCP

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.FCPLCP

Initial server response time was short Root document took 70 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.FCPLCP

URL	Time Spent
/?m=1 (www.xn--ybbb.xn--y9a3aq)	70 ms

Use HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.LCPFCP

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsFCPLCP

Remove duplicate modules in JavaScript bundles

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. FCPLCP

Avoid serving legacy JavaScript to modern browsers

Polyfills and transforms enable legacy 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 legacy browsers. Learn why most sites can deploy ES6+ code without transpilingFCPLCP

Preload Largest Contentful Paint image

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP

Avoids enormous network payloads Total size was 740 KiB

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

URL	Transfer Size
googleusercontent.com	290.1 KiB
…a/AVvXsEiuA… (blogger.googleusercontent.com)	290.1 KiB
Google Tag Manager tag-manager	120.7 KiB
/gtag/js?id=G-9WL5L35ECD (www.googletagmanager.com)	120.7 KiB
Bootstrap CDN cdn	70.8 KiB
…fonts/fontawesome-webfont.woff2?v=4.6.3 (maxcdn.bootstrapcdn.com)	70.8 KiB
Blogger hosting	50.7 KiB
…widgets/280…-widgets.js (www.blogger.com)	50.7 KiB
credly.com	49.7 KiB
…c3ab66f8-…/CERT-Expe….png (images.credly.com)	29.4 KiB
…embed/credly-logo-gray-19b614a….svg (cdn.credly.com)	20.3 KiB
Google CDN cdn	33.4 KiB
…1.11.0/jquery.min.js (ajax.googleapis.com)	33.4 KiB
Google Fonts cdn	32.1 KiB
…v19/wlpogwHKF….woff2 (fonts.gstatic.com)	17.1 KiB
…v24/S6u8w4BMU….woff2 (fonts.gstatic.com)	15.0 KiB
Unattributable	28.3 KiB
/?m=1 (www.xn--ybbb.xn--y9a3aq)	28.3 KiB

Avoids an excessive DOM size 100 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT

Statistic	Element	Value
Total DOM Elements		100
Maximum DOM Depth	manudavidos@օք.հայ:$ <img alt="manudavidos@օք.հայ:$" height="134px; " id="Header1_headerimg" src="https://blogger.googleusercontent.com/img/a/AVvXsEgUorRicUOzNYW5nSlouevXIN…" width="892px; ">	10
Maximum Child Elements	body <body style="">	16

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.

JavaScript execution time 0.6 s

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

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	689 ms	65 ms	26 ms
/?m=1 (www.xn--ybbb.xn--y9a3aq)	424 ms	60 ms	26 ms
Unattributable	265 ms	5 ms	0 ms
Google Tag Manager tag-manager	347 ms	301 ms	22 ms
/gtag/js?id=G-9WL5L35ECD (www.googletagmanager.com)	347 ms	301 ms	22 ms
Google CDN cdn	174 ms	115 ms	5 ms
…1.11.0/jquery.min.js (ajax.googleapis.com)	174 ms	115 ms	5 ms
credly.com	123 ms	13 ms	3 ms
/embedded_badge/5cac4c04-e5e5-4fce-a1e6-f186b466db8a (www.credly.com)	123 ms	13 ms	3 ms

Minimizes main-thread work 1.4 s

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 workTBT

Category	Time Spent
Script Evaluation	545 ms
Other	496 ms
Style & Layout	215 ms
Parse HTML & CSS	100 ms
Script Parsing & Compilation	71 ms
Rendering	20 ms

Lazy load third-party resources with facades

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT

Largest Contentful Paint image was not lazily loaded

Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP

Element
about Me <img alt="about Me" src="https://blogger.googleusercontent.com/img/a/AVvXsEiuAVoOTTl99SNhvCOrMh8Dtp…" style="border-radius: 50px; height: auto; width: 300px;">

Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS

Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.

Page didn't prevent back/forward cache restoration

Warnings: Back/forward cache cannot be tested in old Headless Chrome (`--chrome-flags="--headless=old"`). To see audit results, use the new Headless Chrome (`--chrome-flags="--headless=new"`) or standard Chrome.

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

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.

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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.

Failing Elements
head > meta <meta content="width=device-width,initial-scale=1,minimum-scale=1,maximum-scale=1" name="viewport">

These items highlight common accessibility best practices.

Background and foreground colors do not have a sufficient contrast ratio.

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

Failing Elements
HOME <a class="home-link" href="https://www.օք.հայ/">
HOME <div class="blog-pager" id="blog-pager">
CREATED WITH BY BEAUTYTEMPLATES AND EDITED BY ME <p>
CREATED WITH BY BEAUTYTEMPLATES AND EDITED BY ME BACK TO TOP <footer id="footer-copyright">
BY <em>
CREATED WITH BY BEAUTYTEMPLATES AND EDITED BY ME BACK TO TOP <footer id="footer-copyright">
BEAUTYTEMPLATES <a href="http://www.beautytemplates.com/" id="bloggg" ref="dofollow" style="visibility: visible;">
CREATED WITH BY BEAUTYTEMPLATES AND EDITED BY ME BACK TO TOP <footer id="footer-copyright">
BACK TO TOP <a class="to-top" href="#">
CREATED WITH BY BEAUTYTEMPLATES AND EDITED BY ME BACK TO TOP <footer id="footer-copyright">

Links rely on color to be distinguishable.

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Failing Elements
BEAUTYTEMPLATES <a href="http://www.beautytemplates.com/" id="bloggg" ref="dofollow" style="visibility: visible;">
CREATED WITH BY BEAUTYTEMPLATES AND EDITED BY ME <p>

These are opportunities to improve the legibility of your content.

<html> element does not have a [lang] attribute

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.

Failing Elements
html <html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" xmlns:b="http://www.google.com/2005/gml/b" xmlns:data="http://www.google.com/2005/gml/data" xmlns:expr="http://www.google.com/2005/gml/expr">

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

Links do not have a discernible name

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.

Failing Elements
div.nav-ba > div.menu-mobile > div.slicknav_menu > a.slicknav_btn <a href="#" aria-haspopup="true" tabindex="0" class="slicknav_btn slicknav_collapsed">

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.

Show Hide

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.

The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.

Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.

The user's focus is directed to new content added to the page

If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.

HTML5 landmark elements are used to improve navigation

Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.

Custom controls have associated labels

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.

These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.

Show Hide

[aria-*] attributes match their roles

Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.

[aria-hidden="true"] is not present on the document <body>

Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.

[aria-*] attributes have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

[aria-*] attributes are valid and not misspelled

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Image elements have [alt] attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.

ARIA attributes are used as specified for the element's role

Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.

[aria-hidden="true"] elements do not contain focusable descendents

Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.

Elements use only permitted ARIA attributes

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Document has a <title> element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

<frame> or <iframe> elements have a title

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Lists contain only <li> elements and script supporting elements (<script> and <template>).

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

List items (<li>) are contained within <ul>, <ol> or <menu> parent elements

Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.

No element has a [tabindex] value greater than 0

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.

Touch targets have sufficient size and spacing.

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.

Heading elements appear in a sequentially-descending order

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Uses ARIA roles only on compatible elements

Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.

Image elements do not have [alt] attributes that are redundant text.

Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.

Show Hide

[accesskey] values are unique

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.

button, link, and menuitem elements have accessible names

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Deprecated ARIA roles were not used

Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.

Elements with role="dialog" or role="alertdialog" have accessible names.

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

ARIA input fields have accessible names

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

ARIA meter elements have accessible names

When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.

ARIA progressbar elements have accessible names

When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.

[role]s have all required [aria-*] attributes

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Elements with an ARIA [role] that require children to contain a specific [role] have all required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

[role]s are contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

[role] values are valid

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Elements with the role=text attribute do not have focusable descendents.

Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.

ARIA toggle fields have accessible names

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.

ARIA treeitem elements have accessible names

When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.

Buttons have an accessible name

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.

The page contains a heading, skip link, or landmark region

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.

<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Definition list items are wrapped in <dl> elements

Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.

ARIA IDs are unique

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.

No form fields have multiple labels

Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.

<html> element has a valid value for its [lang] attribute

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.

<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.

If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.

Input buttons have discernible text.

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

<input type="image"> elements have [alt] text

When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.

Form elements have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

The document does not use <meta http-equiv="refresh">

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

<object> elements have alternate text

Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.

Select elements have associated label elements.

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.

Tables have different content in the summary attribute and <caption>.

The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.

Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.

<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.

[lang] attributes have a valid value

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.

<video> elements contain a <track> element with [kind="captions"]

When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.

Best Practices

Browser errors were logged to the console

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

Source	Description
/?m=1:3295:279 (www.xn--ybbb.xn--y9a3aq)	ReferenceError: postperpage is not defined at loophalaman (https://www.օք.հայ/?m=1:3295:280) at hitungtotaldata (https://www.օք.հայ/?m=1:3295:2874) at https://www.օք.հայ/feeds/posts/summary?max-results=1&alt=json-in-script&callback=hitungtotaldata:2:1

Source

Description

/?m=1:3295:279

(www.xn--ybbb.xn--y9a3aq)

ReferenceError: postperpage is not defined
    at loophalaman (https://www.օք.հայ/?m=1:3295:280)
    at hitungtotaldata (https://www.օք.հայ/?m=1:3295:2874)
    at https://www.օք.հայ/feeds/posts/summary?max-results=1&alt=json-in-script&callback=hitungtotaldata:2:1

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.

Name	Version
jQuery	1.11.0

Ensure CSP is effective against XSS attacks

A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS

Description	Directive	Severity
No CSP found in enforcement mode		High

Use a strong HSTS policy

Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.

Description	Directive	Severity
No HSTS header found		High

Ensure proper origin isolation with COOP

The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.

Description	Directive	Severity
No COOP header found		High

Mitigate clickjacking with XFO or CSP

The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.

Description	Severity
No frame control policy found	High

Show Hide

Uses HTTPS

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.

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Avoids third-party cookies

Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.

Allows users to paste into input fields

Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Displays images with correct aspect ratio

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

Serves images with appropriate resolution

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.

Document uses legible font sizes 95.26% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.

Source	Selector	% of Page Text	Font Size
credly.com
/assets/embed-b4eebb4….css:1:411 (cdn.credly.com)	html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video	1.97%	7.04px
/assets/embed-b4eebb4….css:1:1133 (cdn.credly.com)	#badge-expired	0.81%	8px
Unattributable
/?m=1:818:36 (www.xn--ybbb.xn--y9a3aq)	.site-social-networks.show-title a	1.97%	10px
Legible text		95.26%	≥ 12px

Page has the HTML doctype

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

Properly defines charset

A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

No issues in the Issues panel in Chrome Devtools

Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Page has valid source maps

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.

Show Hide

Redirects HTTP traffic to HTTPS

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

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.

Show Hide

Structured data is valid

Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.

Run these additional validators on your site to check additional SEO best practices.

Show Hide

Page isn’t blocked from indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Document has a <title> element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Page has successful HTTP status code

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

Links have descriptive text

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Links are crawlable

Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

robots.txt is valid

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.

Image elements have [alt] attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.

Document has a valid hreflang

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.

Document has a valid rel=canonical

Canonical links suggest which URL to show in search results. Learn more about canonical links.