Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

didan.org

. DiDAN.

Page Load Speed

8.9 sec in total

First Response

1 sec

Resources Loaded

7.3 sec

Page Rendered

549 ms

didan.org screenshot

About Website

Visit didan.org now to see the best up-to-date DiDAN content for Ukraine and also check out these interesting facts you probably never knew about didan.org

Digital Dream Advance Network

Visit didan.org

Key Findings

We analyzed Didan.org page load time and found that the first response time was 1 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

didan.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

36/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

didan.org

1017 ms

style_div.css

274 ms

popup.css

279 ms

scriptslide.js

282 ms

jquery.min.js

823 ms

Our browser made a total of 158 requests to load all elements on the main page. We found that 50% of them (79 requests) were addressed to the original Didan.org, 8% (12 requests) were made to Vk.com and 7% (11 requests) were made to W.uptolike.com. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 627.1 kB (27%)

Content Size

2.3 MB

After Optimization

1.7 MB

In fact, the total size of Didan.org main page is 2.3 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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 144.8 kB

  • Original 171.1 kB
  • After minification 166.3 kB
  • After compression 26.3 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 85% of the original size.

Image Optimization

-12%

Potential reduce by 211.5 kB

  • Original 1.8 MB
  • After minification 1.6 MB

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, DiDAN needs image optimization as it can save up to 211.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 227.4 kB

  • Original 322.5 kB
  • After minification 264.2 kB
  • After compression 95.1 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 227.4 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 43.4 kB

  • Original 54.0 kB
  • After minification 43.7 kB
  • After compression 10.7 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. Didan.org needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (42%)

Requests Now

150

After Optimization

87

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

Accessibility Review

didan.org accessibility score

42

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

Image elements do not have [alt] attributes

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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 [lang] attribute

Best Practices

didan.org best practices score

58

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

SEO Factors

didan.org SEO score

58

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Didan.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Didan.org main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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