Tools & Wizards About Us
kontur365.ru screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

kontur365.ru

Контур 365

Page Load Speed

3.2 sec in total

First Response

397 ms

Resources Loaded

2.4 sec

Page Rendered

401 ms

kontur365.ru screenshot

About Website

Welcome to kontur365.ru homepage info - get ready to check Kontur 365 best content right away, or after learning these important things about kontur365.ru

Официальный сайт Microsoft Office. Наборы офисных программ для дома и для бизнеса.

Visit kontur365.ru

Key Findings

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

Performance Metrics

kontur365.ru performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value4,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

kontur365.ru

397 ms

106 ms

288 ms

jquery-1.11.3.min.js

163 ms

Bootstrap.js

62 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kontur365.ru, 50% (42 requests) were made to C.s-microsoft.com and 8% (7 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (597 ms) relates to the external source C.microsoft.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (71%)

Content Size

2.0 MB

After Optimization

561.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kontur365.ru main page is 2.0 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. CSS take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 63.6 kB

  • Original 82.7 kB
  • After minification 70.0 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 12.7 kB, which is 15% 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 63.6 kB or 77% of the original size.

Image Optimization

-23%

Potential reduce by 90.5 kB

  • Original 389.4 kB
  • After minification 298.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, Kontur 365 needs image optimization as it can save up to 90.5 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 188.1 kB

  • Original 316.2 kB
  • After minification 301.1 kB
  • After compression 128.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 188.1 kB or 59% of the original size.

CSS Optimization

-90%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 115.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. Kontur365.ru needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (61%)

Requests Now

75

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kontur365.ru

kontur365.ru

397 ms

106 ms

288 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

163 ms

Bootstrap.js

Bootstrap.js

62 ms

wt.js

wt.js

44 ms

style.csx

style.csx

46 ms

style.csx

style.csx

50 ms

style.csx

style.csx

56 ms

style.csx

style.csx

59 ms

style.csx

style.csx

59 ms

style.csx

style.csx

55 ms

style.csx

style.csx

59 ms

style.csx

style.csx

57 ms

style.csx

style.csx

60 ms

style.csx

style.csx

59 ms

style.csx

style.csx

59 ms

style.csx

style.csx

62 ms

script.jsx

script.jsx

66 ms

ms.js

ms.js

597 ms

kjBREBZX.min.js

kjBREBZX.min.js

340 ms

microsoft.png

microsoft.png

401 ms

Logo_Office_76x24.png

Logo_Office_76x24.png

94 ms

Logo_Office_Orange_76x24.png

Logo_Office_Orange_76x24.png

72 ms

fallback_icon_chevron.png

fallback_icon_chevron.png

88 ms

Hero_ProductsHP_1920x760.jpg

Hero_ProductsHP_1920x760.jpg

95 ms

CTA_Arrow_White_19x19.png

CTA_Arrow_White_19x19.png

96 ms

Image_BuiltForTeamwork_713x437.png

Image_BuiltForTeamwork_713x437.png

71 ms

Image_Windows10_713x374.png

Image_Windows10_713x374.png

118 ms

Image_WorksForYou_713x213.png

Image_WorksForYou_713x213.png

95 ms

pmg-close-orange.PNG.png

pmg-close-orange.PNG.png

95 ms

Icon_WindowsPhone_40x82.png

Icon_WindowsPhone_40x82.png

117 ms

Icon_AndroidPhone_40x78.png

Icon_AndroidPhone_40x78.png

150 ms

Icon_iPhone_33x69.png

Icon_iPhone_33x69.png

149 ms

Icon_WindowsTablet_94x60.png

Icon_WindowsTablet_94x60.png

150 ms

Icon_AndroidTablet_85x62.png

Icon_AndroidTablet_85x62.png

150 ms

Icon_iPad_84x59.png

Icon_iPad_84x59.png

154 ms

Icon_PC_116x81.png

Icon_PC_116x81.png

223 ms

Icon_Mac_99x82.png

Icon_Mac_99x82.png

294 ms

pmg-blue-arrow.png

pmg-blue-arrow.png

294 ms

Icon_YouTube_48x20.png

Icon_YouTube_48x20.png

293 ms

Icon_LinkedIn_24x20.png

Icon_LinkedIn_24x20.png

294 ms

PMG_Office_Logo.png

PMG_Office_Logo.png

376 ms

windows_symbol.png

windows_symbol.png

365 ms

windowsphone_symbol.png

windowsphone_symbol.png

394 ms

xbox_symbol.png

xbox_symbol.png

398 ms

skype_symbol.png

skype_symbol.png

399 ms

Logo_MSN_24x24.png

Logo_MSN_24x24.png

463 ms

bing_symbol.png

bing_symbol.png

463 ms

store_symbol.png

store_symbol.png

467 ms

globe_icon.png

globe_icon.png

482 ms

serverComponent.php

serverComponent.php

115 ms

sizzle.min.js

sizzle.min.js

67 ms

optimize.js

optimize.js

91 ms

sdk.js

sdk.js

195 ms

latest.woff

latest.woff

252 ms

latest.woff

latest.woff

358 ms

latest.woff

latest.woff

434 ms

latest.woff

latest.woff

421 ms

latest.woff

latest.woff

428 ms

ip.json

ip.json

305 ms

pixel

pixel

387 ms

2

2

494 ms

15f45229b12fc5a55c38702ef101181c.js

15f45229b12fc5a55c38702ef101181c.js

165 ms

2675dcb4f0b492d3500baeea576a3624.js

2675dcb4f0b492d3500baeea576a3624.js

258 ms

e9ea5c84faf25b23bc9b138a4d29a4ca.js

e9ea5c84faf25b23bc9b138a4d29a4ca.js

351 ms

ff5d44f21cb7f4b9e3c9ef45ad20cef3.js

ff5d44f21cb7f4b9e3c9ef45ad20cef3.js

350 ms

cb1c8739d747e5c9c83d7628883b7e00.js

cb1c8739d747e5c9c83d7628883b7e00.js

350 ms

getid.js

getid.js

473 ms

PMGC2CGlobalConfig.js

PMGC2CGlobalConfig.js

439 ms

trans_pixel.aspx

trans_pixel.aspx

173 ms

387 ms

xd_arbiter.php

xd_arbiter.php

308 ms

fbevents.js

fbevents.js

107 ms

ld.js

ld.js

251 ms

pixel

pixel

90 ms

254 ms

254 ms

bat.js

bat.js

282 ms

broker.js

broker.js

132 ms

2

2

44 ms

event

event

120 ms

event

event

350 ms

c.gif

c.gif

26 ms

Accessibility Review

kontur365.ru accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

kontur365.ru best practices score

75

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

kontur365.ru SEO score

93

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

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 Kontur365.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 Kontur365.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

kontur365.ru

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