Tools & Wizards About Us

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

ediary.by

Знай · бай - Электронные дневники и журналы в Беларуси

Page Load Speed

4.8 sec in total

First Response

1 sec

Resources Loaded

3.5 sec

Page Rendered

238 ms

About Website

Click here to check amazing Ediary content for Belarus. Otherwise, check out these important facts you probably never knew about ediary.by

Единая цифровая платформа для школ. Электронные аналоги бумажного дневника и классного журнала. Электронные учебники. Школьные платежи. Бесплатное подключение!

Visit ediary.by

Key Findings

We analyzed Ediary.by page load time and found that the first response time was 1 sec and then it took 3.8 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

ediary.by performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value24.0 s

0/100

25%

SI (Speed Index)

Value24.7 s

0/100

10%

TBT (Total Blocking Time)

Value22,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.434

21/100

15%

TTI (Time to Interactive)

Value33.2 s

0/100

10%

Network Requests Diagram

ediary.by

1005 ms

bootstrap.min.css

343 ms

datepicker.css

831 ms

jquery.Jcrop.min.css

815 ms

ediary-styles.css

1186 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 98% of them (39 requests) were addressed to the original Ediary.by, 3% (1 request) were made to Cdn.ckeditor.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Ediary.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 791.0 kB (60%)

Content Size

1.3 MB

After Optimization

532.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ediary.by main page is 1.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. 35% of websites need less resources to load. Javascripts take 770.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 43.3 kB

  • Original 51.0 kB
  • After minification 42.9 kB
  • After compression 7.6 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 8.1 kB, which is 16% 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 43.3 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 16.3 kB

  • Original 288.9 kB
  • After minification 272.7 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. Ediary images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 550.9 kB

  • Original 770.1 kB
  • After minification 714.0 kB
  • After compression 219.2 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 550.9 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 180.5 kB

  • Original 213.2 kB
  • After minification 183.0 kB
  • After compression 32.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. Ediary.by needs all CSS files to be minified and compressed as it can save up to 180.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (51%)

Requests Now

39

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

ediary.by accessibility score

88

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.

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ediary.by 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

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

ediary.by 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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ediary.by can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Ediary.by 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 data is detected on the main page of Ediary. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: