Tools & Wizards About Us
36n6.com.ua screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

36n6.com.ua

Здоровье в Украине, поиск врачей, клиник, лекарств - 36n6.com.ua

Page Load Speed

6.4 sec in total

First Response

561 ms

Resources Loaded

3.9 sec

Page Rendered

2 sec

36n6.com.ua screenshot

About Website

Click here to check amazing 36 N 6 content for Ukraine. Otherwise, check out these important facts you probably never knew about 36n6.com.ua

Информационный портал о здоровье в Украине, врачи, клиники, запись на приме отзывы.

Visit 36n6.com.ua

Key Findings

We analyzed 36n6.com.ua page load time and found that the first response time was 561 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

36n6.com.ua performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

36n6.com.ua

561 ms

analytics.js

14 ms

main-header.js

669 ms

main-header.css

718 ms

cache

531 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 20% of them (10 requests) were addressed to the original 36n6.com.ua, 27% (13 requests) were made to Vk.com and 20% (10 requests) were made to Media.36n6.ru. The less responsive or slowest element that took the longest time to load (997 ms) relates to the external source Media.36n6.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 754.8 kB (75%)

Content Size

1.0 MB

After Optimization

253.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 36n6.com.ua main page is 1.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 492.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 82.9 kB

  • Original 103.3 kB
  • After minification 86.1 kB
  • After compression 20.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 17.2 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 82.9 kB or 80% of the original size.

Image Optimization

-27%

Potential reduce by 12.9 kB

  • Original 47.2 kB
  • After minification 34.2 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, 36 N 6 needs image optimization as it can save up to 12.9 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 361.2 kB

  • Original 492.2 kB
  • After minification 433.2 kB
  • After compression 131.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 361.2 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 297.8 kB

  • Original 365.9 kB
  • After minification 352.6 kB
  • After compression 68.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 36n6.com.ua needs all CSS files to be minified and compressed as it can save up to 297.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (55%)

Requests Now

42

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 36 N 6. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

36n6.com.ua

36n6.com.ua

561 ms

analytics.js

analytics.js

14 ms

main-header.js

main-header.js

669 ms

main-header.css

main-header.css

718 ms

cache

cache

531 ms

main-footer.js

main-footer.js

997 ms

main-footer.css

main-footer.css

538 ms

ajax-loading.gif

ajax-loading.gif

232 ms

logo.png

logo.png

119 ms

user-logo.png

user-logo.png

139 ms

breadcrumbs-h.png

breadcrumbs-h.png

120 ms

profile_avatar_default-mini.png

profile_avatar_default-mini.png

115 ms

222.jpg

222.jpg

195 ms

logo.jpg

logo.jpg

238 ms

ajax-loader.gif

ajax-loader.gif

194 ms

context.js

context.js

451 ms

opensanscondlight.woff

opensanscondlight.woff

450 ms

title-arrow.png

title-arrow.png

332 ms

list-arrow.png

list-arrow.png

328 ms

openapi.js

openapi.js

393 ms

footer-bg.png

footer-bg.png

304 ms

hit;36n6

hit;36n6

345 ms

watch.js

watch.js

2 ms

3279

3279

174 ms

ajax-long-loader.gif

ajax-long-loader.gif

102 ms

hit;36n6

hit;36n6

146 ms

context_static_r1084.js

context_static_r1084.js

338 ms

upload.gif

upload.gif

128 ms

widget_community.php

widget_community.php

315 ms

loader_nav19239_3.js

loader_nav19239_3.js

129 ms

lite.css

lite.css

131 ms

lite.js

lite.js

621 ms

lang3_0.js

lang3_0.js

260 ms

widget_community.css

widget_community.css

262 ms

xdm.js

xdm.js

264 ms

al_community.js

al_community.js

264 ms

146024

146024

143 ms

watch.js

watch.js

1 ms

gPy0Kqt-7Hk.jpg

gPy0Kqt-7Hk.jpg

504 ms

e_10159985.jpg

e_10159985.jpg

476 ms

2F49KXO2CaY.jpg

2F49KXO2CaY.jpg

467 ms

YRLtaYOMFP0.jpg

YRLtaYOMFP0.jpg

464 ms

1478bgbPXT4.jpg

1478bgbPXT4.jpg

477 ms

1cYylGNNg84.jpg

1cYylGNNg84.jpg

357 ms

3a2imzcpql0.jpg

3a2imzcpql0.jpg

475 ms

camera_50.png

camera_50.png

193 ms

w_logo.png

w_logo.png

185 ms

3279

3279

140 ms

openapi.js

openapi.js

253 ms

Accessibility Review

36n6.com.ua accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Names and labels

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.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

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

Best Practices

36n6.com.ua best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

36n6.com.ua SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    UA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 36n6.com.ua can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed language. Our system also found out that 36n6.com.ua main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

36n6.com.ua

Open Graph description is not detected on the main page of 36 N 6. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: