Tools & Wizards About Us
1c-ei.ru screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

1c-ei.ru

Enterprise Integrator

Page Load Speed

22.8 sec in total

First Response

420 ms

Resources Loaded

22.1 sec

Page Rendered

282 ms

1c-ei.ru screenshot

About Website

Visit 1c-ei.ru now to see the best up-to-date 1 C Ei content for Russia and also check out these interesting facts you probably never knew about 1c-ei.ru

Набор профессиональных инструментов для специалистов, поддерживающих и разрабатывающих решения на платформе 1С:Предприятие 8.

Visit 1c-ei.ru

Key Findings

We analyzed 1c-ei.ru page load time and found that the first response time was 420 ms and then it took 22.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

1c-ei.ru performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.069

96/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

1c-ei.ru

420 ms

main.1c-ei.ru

823 ms

standard-css-default-ltr-ltr.css

80 ms

allthemes-view.css

96 ms

jot_min_view__ru.js

106 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 1c-ei.ru, 27% (17 requests) were made to Apis.google.com and 9% (6 requests) were made to Main.1c-ei.ru. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Gcount.charanj.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.4 kB (31%)

Content Size

268.4 kB

After Optimization

184.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1c-ei.ru main page is 268.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 125.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 32.6 kB

  • Original 45.7 kB
  • After minification 45.2 kB
  • After compression 13.1 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 32.6 kB or 71% of the original size.

Image Optimization

-6%

Potential reduce by 7.1 kB

  • Original 125.3 kB
  • After minification 118.2 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. 1 C Ei images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 44.6 kB

  • Original 93.8 kB
  • After minification 93.7 kB
  • After compression 49.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 44.6 kB or 48% of the original size.

CSS Optimization

-2%

Potential reduce by 70 B

  • Original 3.6 kB
  • After minification 3.6 kB
  • After compression 3.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. 1c-ei.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (59%)

Requests Now

56

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1c-ei.ru

1c-ei.ru

420 ms

main.1c-ei.ru

main.1c-ei.ru

823 ms

standard-css-default-ltr-ltr.css

standard-css-default-ltr-ltr.css

80 ms

allthemes-view.css

allthemes-view.css

96 ms

jot_min_view__ru.js

jot_min_view__ru.js

106 ms

2.jpg

2.jpg

220 ms

radar-icon.png

radar-icon.png

258 ms

Safari.png

Safari.png

262 ms

ifr

ifr

181 ms

blogger.gif

blogger.gif

149 ms

ifr

ifr

176 ms

1292704474_currency_dollar%20green.png;width=46

1292704474_currency_dollar%20green.png;width=46

177 ms

ifr

ifr

162 ms

gwt-logo2.png

gwt-logo2.png

334 ms

browse-all-color.png

browse-all-color.png

416 ms

1284578050_Burn.png

1284578050_Burn.png

355 ms

bestseller.png

bestseller.png

477 ms

customLogo.gif

customLogo.gif

116 ms

1306606342_bug.png

1306606342_bug.png

141 ms

%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA39.png

%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA39.png

171 ms

bg_sprites.gif

bg_sprites.gif

96 ms

tree_ltr.gif

tree_ltr.gif

115 ms

icon_page.gif

icon_page.gif

129 ms

analytics.js

analytics.js

461 ms

platform.js

platform.js

984 ms

core.js

core.js

101 ms

enterprise-integrator

enterprise-integrator

20051 ms

plusone.js

plusone.js

972 ms

videoseries

videoseries

439 ms

collect

collect

162 ms

tz

tz

149 ms

www-embed-player-vfl5foy2V.css

www-embed-player-vfl5foy2V.css

453 ms

www-embed-player.js

www-embed-player.js

646 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

288 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

270 ms

fastbutton

fastbutton

344 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

170 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

85 ms

badge

badge

296 ms

postmessageRelay

postmessageRelay

248 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

273 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

134 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

609 ms

postmessageRelay

postmessageRelay

270 ms

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

326 ms

ad_status.js

ad_status.js

321 ms

rs=AGLTcCN535c_Pm7E98TMX1EdOFE9-2anyw

rs=AGLTcCN535c_Pm7E98TMX1EdOFE9-2anyw

59 ms

rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A

rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A

147 ms

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

351 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

300 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

294 ms

photo.jpg

photo.jpg

402 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

462 ms

rpc:shindig_random.js

rpc:shindig_random.js

376 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

266 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

278 ms

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

38 ms

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

83 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

ga.js

ga.js

38 ms

element.js

element.js

105 ms

__utm.gif

__utm.gif

43 ms

translateelement.css

translateelement.css

321 ms

main.js

main.js

378 ms

Accessibility Review

1c-ei.ru accessibility score

74

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

button, link, and menuitem elements do not have accessible names.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

1c-ei.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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

1c-ei.ru SEO score

89

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1c-ei.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 1c-ei.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

1c-ei.ru

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