Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

ilex.by

Информационно-правовой портал для бухгалтеров, юристов и руководителей

Page Load Speed

6.9 sec in total

First Response

508 ms

Resources Loaded

4.1 sec

Page Rendered

2.3 sec

ilex.by screenshot

About Website

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

ilex — oнлайн-сервис готовых правовых решений по бухучету, налогообложению и праву для бухгалтеров, юристов, руководителей.

Visit ilex.by

Key Findings

We analyzed Ilex.by page load time and found that the first response time was 508 ms and then it took 6.4 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

ilex.by performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value22,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value32.1 s

0/100

10%

Network Requests Diagram

ilex.by

508 ms

ilex.by

566 ms

es5-shims.min.js

24 ms

share.js

26 ms

style.min.css

107 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 87% of them (86 requests) were addressed to the original Ilex.by, 2% (2 requests) were made to Yastatic.net and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Ilex.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 647.0 kB (35%)

Content Size

1.8 MB

After Optimization

1.2 MB

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

HTML Optimization

-88%

Potential reduce by 246.3 kB

  • Original 280.1 kB
  • After minification 191.0 kB
  • After compression 33.8 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 89.1 kB, which is 32% 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 246.3 kB or 88% of the original size.

Image Optimization

-28%

Potential reduce by 340.0 kB

  • Original 1.2 MB
  • After minification 864.8 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, Ilex needs image optimization as it can save up to 340.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 31.1 kB

  • Original 237.4 kB
  • After minification 234.9 kB
  • After compression 206.3 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 31.1 kB or 13% of the original size.

CSS Optimization

-25%

Potential reduce by 29.6 kB

  • Original 117.6 kB
  • After minification 117.5 kB
  • After compression 88.0 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. Ilex.by needs all CSS files to be minified and compressed as it can save up to 29.6 kB or 25% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

45

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

Accessibility Review

ilex.by accessibility score

71

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

ilex.by best practices score

75

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

Page has valid source maps

SEO Factors

ilex.by SEO score

84

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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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