Tools & Wizards About Us

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

archive.ru

Электронный архив: организация архива документов организации. Cоздание, обработка и организация электронного архива документов предприятия - ЭЛАР

Page Load Speed

10.5 sec in total

First Response

542 ms

Resources Loaded

9.3 sec

Page Rendered

640 ms

About Website

Visit archive.ru now to see the best up-to-date Archive content and also check out these interesting facts you probably never knew about archive.ru

Корпорация ЭЛАР — крупнейшее в Европе специализированное предприятие по созданию, комплексному оснащению и наполнению электронных архивов, внедрению передовой техники, информационных технологий и реше...

Visit archive.ru

Key Findings

We analyzed Archive.ru page load time and found that the first response time was 542 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

archive.ru performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.1 s

0/100

25%

SI (Speed Index)

Value27.4 s

0/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value30.1 s

0/100

10%

Network Requests Diagram

archive.ru

542 ms

www.elar.ru

510 ms

elar.ru

1311 ms

css2

42 ms

style.css

381 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Archive.ru, 74% (51 requests) were made to Elar.ru and 10% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Elar.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (46%)

Content Size

3.8 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Archive.ru main page is 3.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. 60% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 62.6 kB

  • Original 75.5 kB
  • After minification 49.1 kB
  • After compression 12.9 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 26.4 kB, which is 35% 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 62.6 kB or 83% of the original size.

Image Optimization

-12%

Potential reduce by 186.5 kB

  • Original 1.6 MB
  • After minification 1.4 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, Archive needs image optimization as it can save up to 186.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

-63%

Potential reduce by 1.1 MB

  • Original 1.7 MB
  • After minification 1.6 MB
  • After compression 633.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 1.1 MB or 63% of the original size.

CSS Optimization

-90%

Potential reduce by 410.9 kB

  • Original 457.4 kB
  • After minification 396.6 kB
  • After compression 46.5 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. Archive.ru needs all CSS files to be minified and compressed as it can save up to 410.9 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (52%)

Requests Now

58

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

archive.ru accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

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

archive.ru 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

archive.ru 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

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Archive.ru 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 Archive.ru 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 description is not detected on the main page of Archive. 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: