Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

vitaliypodoba.com

Блог Віталія Подоби - Програмування, Саморозвиток, IT сфера

Page Load Speed

4.2 sec in total

First Response

244 ms

Resources Loaded

3.6 sec

Page Rendered

383 ms

vitaliypodoba.com screenshot

About Website

Click here to check amazing Vitaliypodoba content for Ukraine. Otherwise, check out these important facts you probably never knew about vitaliypodoba.com

Навчання програмістів початківців, Python та Django напрямок.

Visit vitaliypodoba.com

Key Findings

We analyzed Vitaliypodoba.com page load time and found that the first response time was 244 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

vitaliypodoba.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value6,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

vitaliypodoba.com

244 ms

www.vitaliypodoba.com

971 ms

www.vitaliypodoba.com

514 ms

crayon.min.css

282 ms

social_widget.css

191 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 51% of them (38 requests) were addressed to the original Vitaliypodoba.com, 11% (8 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Vitaliypodoba.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (59%)

Content Size

2.4 MB

After Optimization

958.5 kB

In fact, the total size of Vitaliypodoba.com main page is 2.4 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 144.8 kB

  • Original 188.1 kB
  • After minification 186.0 kB
  • After compression 43.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 144.8 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 31.0 kB

  • Original 499.7 kB
  • After minification 468.6 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. Vitaliypodoba images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 850.3 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 389.6 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 850.3 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 381.2 kB

  • Original 438.0 kB
  • After minification 391.4 kB
  • After compression 56.9 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. Vitaliypodoba.com needs all CSS files to be minified and compressed as it can save up to 381.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (56%)

Requests Now

62

After Optimization

27

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

Accessibility Review

vitaliypodoba.com accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

vitaliypodoba.com 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

Uses deprecated APIs

SEO Factors

vitaliypodoba.com SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    UK

  • Language Claimed

    UK

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vitaliypodoba.com can be misinterpreted by Google and other search engines. Our service has detected that Ukrainian is used on the page, and it matches the claimed language. Our system also found out that Vitaliypodoba.com 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

Open Graph description is not detected on the main page of Vitaliypodoba. 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: