Tools & Wizards About Us
1c.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

1c.com

1C Company

Page Load Speed

2.8 sec in total

First Response

226 ms

Resources Loaded

2.4 sec

Page Rendered

195 ms

1c.com screenshot

About Website

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

1C:DN | 1C:Developer Network - official site

Visit 1c.com

Key Findings

We analyzed 1c.com page load time and found that the first response time was 226 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

1c.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

1c-dn.com

226 ms

1c-dn.com

768 ms

kernel_main.css

631 ms

template_7456ef61dedae2ef4d6e80265b2b011b.css

789 ms

kernel_main.js

956 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 1c.com, 12% (8 requests) were made to 1c-dn.com and 12% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source 1c-dn.com.js.1c-bitrix-cdn.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 740.4 kB (65%)

Content Size

1.1 MB

After Optimization

407.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1c.com main page is 1.1 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. 55% of websites need less resources to load. Javascripts take 741.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 42.7 kB

  • Original 56.3 kB
  • After minification 54.1 kB
  • After compression 13.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 42.7 kB or 76% of the original size.

Image Optimization

-12%

Potential reduce by 22.6 kB

  • Original 192.4 kB
  • After minification 169.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. Obviously, 1C needs image optimization as it can save up to 22.6 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

-73%

Potential reduce by 539.7 kB

  • Original 741.4 kB
  • After minification 714.1 kB
  • After compression 201.7 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 539.7 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 135.4 kB

  • Original 157.4 kB
  • After minification 138.5 kB
  • After compression 22.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. 1c.com needs all CSS files to be minified and compressed as it can save up to 135.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (58%)

Requests Now

66

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1c-dn.com

1c-dn.com

226 ms

1c-dn.com

1c-dn.com

768 ms

kernel_main.css

kernel_main.css

631 ms

template_7456ef61dedae2ef4d6e80265b2b011b.css

template_7456ef61dedae2ef4d6e80265b2b011b.css

789 ms

kernel_main.js

kernel_main.js

956 ms

core_db.min.js

core_db.min.js

641 ms

core_frame_cache.min.js

core_frame_cache.min.js

639 ms

template_bf9e194192962dc18931733c8ddc2312.js

template_bf9e194192962dc18931733c8ddc2312.js

1115 ms

slide-3-01.png

slide-3-01.png

75 ms

page-wrapper.png

page-wrapper.png

394 ms

logo.png

logo.png

167 ms

header-nav.gif

header-nav.gif

394 ms

header-nav-li.gif

header-nav-li.gif

395 ms

input.png

input.png

397 ms

nav-bg.gif

nav-bg.gif

398 ms

nav-tabs.gif

nav-tabs.gif

396 ms

slider-bg.png

slider-bg.png

499 ms

homeblock-top.gif

homeblock-top.gif

499 ms

pageicons.png

pageicons.png

493 ms

homeblock-bottom.gif

homeblock-bottom.gif

499 ms

content-bottom-bg.gif

content-bottom-bg.gif

499 ms

arrow.gif

arrow.gif

497 ms

icon.png

icon.png

646 ms

about-button.gif

about-button.gif

653 ms

content-bottom-bullet.gif

content-bottom-bullet.gif

653 ms

content-bottom-li.gif

content-bottom-li.gif

652 ms

wrap-content-footer.gif

wrap-content-footer.gif

652 ms

footer-column-head.png

footer-column-head.png

652 ms

footer-column-li.png

footer-column-li.png

803 ms

author.png

author.png

811 ms

footer.png

footer.png

811 ms

footer-logo.png

footer-logo.png

810 ms

sociallogos.png

sociallogos.png

812 ms

slide-3-02.png

slide-3-02.png

111 ms

slide-3-03.png

slide-3-03.png

110 ms

slide-3-04.png

slide-3-04.png

190 ms

slide-3-05.png

slide-3-05.png

161 ms

ba.js

ba.js

191 ms

ga.js

ga.js

37 ms

all.js

all.js

36 ms

widgets.js

widgets.js

94 ms

in.js

in.js

85 ms

plusone.js

plusone.js

135 ms

sprite-1x.png

sprite-1x.png

79 ms

__utm.gif

__utm.gif

33 ms

169 ms

secureAnonymousFramework

secureAnonymousFramework

95 ms

xd_arbiter.php

xd_arbiter.php

35 ms

xd_arbiter.php

xd_arbiter.php

70 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

158 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

25 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

42 ms

fastbutton

fastbutton

101 ms

bx_stat

bx_stat

263 ms

share

share

115 ms

sprite_connect_v14.png

sprite_connect_v14.png

74 ms

postmessageRelay

postmessageRelay

71 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

26 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

25 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

37 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

41 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

27 ms

rpc:shindig_random.js

rpc:shindig_random.js

33 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

jot

jot

92 ms

xd_arbiter.php

xd_arbiter.php

6 ms

like.php

like.php

69 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

11 ms

Accessibility Review

1c.com accessibility score

89

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

Best Practices

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

SEO Factors

1c.com SEO score

83

Search Engine Optimization Advices

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

    EN

  • 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.com can be misinterpreted by Google and other search engines. Our service has detected that English 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.com 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.com

Open Graph description is not detected on the main page of 1C. 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: