Tools & Wizards About Us
algocom.ru screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

algocom.ru

Курьерская служба для бизнеса

Page Load Speed

4.3 sec in total

First Response

517 ms

Resources Loaded

3.7 sec

Page Rendered

102 ms

algocom.ru screenshot

About Website

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

Компании «Алгоритм» - это служба доставки заказов для бизнеса по Москве и в регионы. Звоните +7 (495) 150-60-78.

Visit algocom.ru

Key Findings

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

Performance Metrics

algocom.ru performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

algocom.ru

517 ms

algocom.ru

555 ms

www.algocom.ru

794 ms

css

32 ms

css

51 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 63% of them (35 requests) were addressed to the original Algocom.ru, 9% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Widget.mango-office.ru. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Algocom.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 812.6 kB (50%)

Content Size

1.6 MB

After Optimization

823.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Algocom.ru main page is 1.6 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. 45% of websites need less resources to load. Javascripts take 983.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 133.4 kB

  • Original 175.8 kB
  • After minification 163.0 kB
  • After compression 42.4 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 133.4 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 28.5 kB

  • Original 414.1 kB
  • After minification 385.6 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. Algocom images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 645.6 kB

  • Original 983.0 kB
  • After minification 983.0 kB
  • After compression 337.4 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 645.6 kB or 66% of the original size.

CSS Optimization

-8%

Potential reduce by 5.2 kB

  • Original 62.7 kB
  • After minification 62.7 kB
  • After compression 57.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. Algocom.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (50%)

Requests Now

42

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

algocom.ru

algocom.ru

517 ms

algocom.ru

algocom.ru

555 ms

www.algocom.ru

www.algocom.ru

794 ms

css

css

32 ms

css

css

51 ms

ui.design-tokens.min.css

ui.design-tokens.min.css

253 ms

ui.font.opensans.min.css

ui.font.opensans.min.css

381 ms

main.popup.bundle.min.css

main.popup.bundle.min.css

383 ms

template_896e81c4f7faad5fc4e1915d0690de6c_v1.css

template_896e81c4f7faad5fc4e1915d0690de6c_v1.css

676 ms

player_api

player_api

135 ms

core.min.js

core.min.js

917 ms

kernel_main_v1.js

kernel_main_v1.js

800 ms

dexie3.bundle.min.js

dexie3.bundle.min.js

658 ms

core_ls.min.js

core_ls.min.js

507 ms

core_frame_cache.min.js

core_frame_cache.min.js

509 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

886 ms

main.popup.bundle.min.js

main.popup.bundle.min.js

770 ms

ajax.min.js

ajax.min.js

790 ms

template_95e5bb6197c5b1bbe667276be02b97db_v1.js

template_95e5bb6197c5b1bbe667276be02b97db_v1.js

1067 ms

c-t-w.min.js

c-t-w.min.js

745 ms

www.algocom.ru

www.algocom.ru

896 ms

logo.png

logo.png

885 ms

3ef374cee772cdcc3bf41fa9b7362dd8.png

3ef374cee772cdcc3bf41fa9b7362dd8.png

885 ms

6a3a3bc15604193bd3b5f7ad6fb3139e.png

6a3a3bc15604193bd3b5f7ad6fb3139e.png

962 ms

928c1000487d5235c9ac76194501f33e.png

928c1000487d5235c9ac76194501f33e.png

995 ms

ea86ad8448e16d430f743e430c82d951.png

ea86ad8448e16d430f743e430c82d951.png

1000 ms

bc0472a724175511ac7f6476e03bd37a.png

bc0472a724175511ac7f6476e03bd37a.png

1009 ms

f7fdbba54c82dd62dec6c764a0357ea4.png

f7fdbba54c82dd62dec6c764a0357ea4.png

1045 ms

www-widgetapi.js

www-widgetapi.js

42 ms

b27cd4c4bebfe399d1415921cb38abb0.jpg

b27cd4c4bebfe399d1415921cb38abb0.jpg

1068 ms

501e8cdff8f3eda71eba96ff8780b3ce.svg

501e8cdff8f3eda71eba96ff8780b3ce.svg

475 ms

fad413910eaec2ede2ccaf38bfa024f4.svg

fad413910eaec2ede2ccaf38bfa024f4.svg

478 ms

7e2e989fb7c39aa36c5a0c58de787c4e.svg

7e2e989fb7c39aa36c5a0c58de787c4e.svg

489 ms

8742515ec4cbd034b9181a4f5985f590.svg

8742515ec4cbd034b9181a4f5985f590.svg

494 ms

opensans-regular.woff

opensans-regular.woff

455 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVc.ttf

21 ms

opensans-light.woff

opensans-light.woff

564 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVc.ttf

29 ms

opensans-semibold.woff

opensans-semibold.woff

571 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4taVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4taVc.ttf

34 ms

opensans-bold.woff

opensans-bold.woff

578 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVc.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4taVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4taVc.ttf

40 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

589 ms

ba.js

ba.js

281 ms

widget-data

widget-data

196 ms

widget-data

widget-data

273 ms

analytics.js

analytics.js

23 ms

watch.js

watch.js

16 ms

loader_2_sshbnd.js

loader_2_sshbnd.js

749 ms

scroll.png

scroll.png

236 ms

collect

collect

13 ms

collect

collect

28 ms

js

js

70 ms

ga-audiences

ga-audiences

119 ms

set-view

set-view

637 ms

Accessibility Review

algocom.ru accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

algocom.ru SEO score

90

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

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

algocom.ru

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