Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

infolex.ru

Когнитивные аспекты лексикографии

Page Load Speed

1.7 sec in total

First Response

461 ms

Resources Loaded

1.1 sec

Page Rendered

176 ms

infolex.ru screenshot

About Website

Welcome to infolex.ru homepage info - get ready to check Infolex best content for Russia right away, or after learning these important things about infolex.ru

Visit infolex.ru

Key Findings

We analyzed Infolex.ru page load time and found that the first response time was 461 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

infolex.ru performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

infolex.ru

461 ms

mystyle.css

128 ms

xaramenu.js

373 ms

egypta.js

253 ms

Background.jpg

396 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that all of those requests were addressed to Infolex.ru and no external sources were called. The less responsive or slowest element that took the longest time to load (461 ms) belongs to the original domain Infolex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.3 kB (61%)

Content Size

23.3 kB

After Optimization

9.1 kB

In fact, the total size of Infolex.ru main page is 23.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 9.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 3.6 kB

  • Original 5.2 kB
  • After minification 5.2 kB
  • After compression 1.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. 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 3.6 kB or 69% of the original size.

Image Optimization

-11%

Potential reduce by 439 B

  • Original 4.1 kB
  • After minification 3.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. Obviously, Infolex needs image optimization as it can save up to 439 B or 11% 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 7.0 kB

  • Original 9.9 kB
  • After minification 9.9 kB
  • After compression 2.9 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 7.0 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 3.2 kB

  • Original 4.0 kB
  • After minification 3.6 kB
  • After compression 821 B

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. Infolex.ru needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

16

After Optimization

7

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

Accessibility Review

infolex.ru accessibility score

55

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

infolex.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

infolex.ru SEO score

58

Search Engine Optimization Advices

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

    RU

  • Language Claimed

    N/A

  • Encoding

    KOI8-R

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infolex.ru 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 Infolex.ru main page’s claimed encoding is koi8-r. 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 Infolex. 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: