Tools & Wizards About Us
znaj.by screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 70% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

znaj.by

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

Page Load Speed

6 sec in total

First Response

633 ms

Resources Loaded

3.9 sec

Page Rendered

1.5 sec

znaj.by screenshot

About Website

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

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

Visit znaj.by

Key Findings

We analyzed Znaj.by page load time and found that the first response time was 633 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

znaj.by performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.434

21/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

znaj.by

633 ms

css

337 ms

js

83 ms

context.js

1490 ms

gpt.js

951 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 53% of them (48 requests) were addressed to the original Znaj.by, 5% (5 requests) were made to Pagead2.googlesyndication.com and 4% (4 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Znaj.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 201.3 kB (14%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Znaj.by main page is 1.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 75.9 kB

  • Original 92.2 kB
  • After minification 72.8 kB
  • After compression 16.2 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 19.4 kB, which is 21% 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 75.9 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 70.5 kB

  • Original 1.0 MB
  • After minification 963.9 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. Znaj images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 54.9 kB

  • Original 364.3 kB
  • After minification 364.3 kB
  • After compression 309.4 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 54.9 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (39%)

Requests Now

74

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

znaj.by

znaj.by

633 ms

css

css

337 ms

js

js

83 ms

context.js

context.js

1490 ms

gpt.js

gpt.js

951 ms

main

main

950 ms

tag.js

tag.js

1361 ms

analytics.js

analytics.js

423 ms

fbevents.js

fbevents.js

350 ms

by-phone-number.svg

by-phone-number.svg

342 ms

znaj-logo-white-1.svg

znaj-logo-white-1.svg

340 ms

Google-Play.svg

Google-Play.svg

536 ms

App-Store.svg

App-Store.svg

526 ms

AppGallery.svg

AppGallery.svg

838 ms

350x410.png

350x410.png

1105 ms

Youtube.svg

Youtube.svg

846 ms

Viber.svg

Viber.svg

833 ms

1540x349.png

1540x349.png

1553 ms

1.svg

1.svg

850 ms

2.svg

2.svg

1117 ms

3.svg

3.svg

1555 ms

4.svg

4.svg

1530 ms

ornament.svg

ornament.svg

1101 ms

20up.svg

20up.svg

1321 ms

80down.svg

80down.svg

1339 ms

15up.svg

15up.svg

1342 ms

ornament_lg.svg

ornament_lg.svg

1539 ms

2_1.png

2_1.png

1551 ms

2_2.png

2_2.png

1542 ms

2_3.png

2_3.png

1581 ms

2_5.png

2_5.png

1586 ms

2_6.png

2_6.png

1551 ms

2_7.png

2_7.png

1672 ms

ornament_footer_top.svg

ornament_footer_top.svg

1669 ms

mobcon_isolated_pms5275_rgb.png

mobcon_isolated_pms5275_rgb.png

1665 ms

spinner.gif

spinner.gif

1636 ms

2290734091229423

2290734091229423

426 ms

collect

collect

32 ms

collect

collect

302 ms

welcome-page-wrapper.jpg

welcome-page-wrapper.jpg

1081 ms

pubads_impl_2022092901.js

pubads_impl_2022092901.js

158 ms

ppub_config

ppub_config

153 ms

icon_menu-level-1.svg

icon_menu-level-1.svg

874 ms

with-dots-svg.svg

with-dots-svg.svg

985 ms

ga-audiences

ga-audiences

316 ms

ProximaNova-Regular.otf

ProximaNova-Regular.otf

943 ms

ProximaNova-RegularItalic.otf

ProximaNova-RegularItalic.otf

945 ms

ProximaNovaRegularItalic.otf

ProximaNovaRegularItalic.otf

945 ms

ProximaNova-Semibold.otf

ProximaNova-Semibold.otf

945 ms

ProximaNova-Extrabold.otf

ProximaNova-Extrabold.otf

1123 ms

ProximaNova-Bold.otf

ProximaNova-Bold.otf

1009 ms

MaterialIcons-Regular-upd.woff

MaterialIcons-Regular-upd.woff

1048 ms

MuseoSansCyrl-500.woff

MuseoSansCyrl-500.woff

764 ms

MuseoSansCyrl-700.woff

MuseoSansCyrl-700.woff

765 ms

MuseoSansCyrl-900.woff

MuseoSansCyrl-900.woff

789 ms

integrator.js

integrator.js

321 ms

ads

ads

451 ms

container.html

container.html

268 ms

ornament_accordion_bottom.svg

ornament_accordion_bottom.svg

415 ms

icon_li.svg

icon_li.svg

435 ms

icon_li_opacity.svg

icon_li_opacity.svg

437 ms

ornament_accordion_top.svg

ornament_accordion_top.svg

436 ms

icon_contacts@2x.png

icon_contacts@2x.png

404 ms

xgemius.js

xgemius.js

875 ms

advert.gif

advert.gif

529 ms

gen_204

gen_204

155 ms

pixel

pixel

191 ms

ad

ad

234 ms

window_focus.js

window_focus.js

188 ms

qs_click_protection.js

qs_click_protection.js

188 ms

rx_lidar.js

rx_lidar.js

189 ms

pixel

pixel

42 ms

pixel

pixel

43 ms

pixel

pixel

34 ms

rum

rum

4 ms

express_html_inpage_rendering_lib_200_276.js

express_html_inpage_rendering_lib_200_276.js

165 ms

omrhp.js

omrhp.js

13 ms

abg_lite.js

abg_lite.js

11 ms

bounce

bounce

151 ms

rum

rum

6 ms

UFYwWwmt.js

UFYwWwmt.js

136 ms

sync_cookie_image_decide

sync_cookie_image_decide

151 ms

pixel

pixel

30 ms

Enqz_20U.html

Enqz_20U.html

38 ms

activeview

activeview

19 ms

YrdBSjzfIHcYhYLmavhSyO_EhBrLUWpx5ykdL7H9Kqg.js

YrdBSjzfIHcYhYLmavhSyO_EhBrLUWpx5ykdL7H9Kqg.js

14 ms

240x400.html

240x400.html

35 ms

img;adv=11122207570744;ec=11122226302456;adv.a=6266241;c.a=25978842;s.a=3213511;p.a=304868342;a.a=497863972;cache=2142491279;

img;adv=11122207570744;ec=11122226302456;adv.a=6266241;c.a=25978842;s.a=3213511;p.a=304868342;a.a=497863972;cache=2142491279;

108 ms

createjs_2015.11.26_54e1c3722102182bb133912ad4442e19_min.js

createjs_2015.11.26_54e1c3722102182bb133912ad4442e19_min.js

26 ms

240x400.js

240x400.js

214 ms

sync_cookie_image_decide

sync_cookie_image_decide

125 ms

Accessibility Review

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

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

znaj.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 Znaj.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 Znaj.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

znaj.by

Open Graph data is detected on the main page of Znaj. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: