Tools & Wizards About Us
mobi-c.ru screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

mobi-c.ru

Мобильная торговля для 1С. Программа для мобильной торговли.

Page Load Speed

5.2 sec in total

First Response

665 ms

Resources Loaded

3.8 sec

Page Rendered

730 ms

mobi-c.ru screenshot

About Website

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

Моби-С предоставляет великолепный инструмент для мобильной торговли. Автоматизации 1С торговли. Контроль и мотивация торговых представителей.

Visit mobi-c.ru

Key Findings

We analyzed Mobi-c.ru page load time and found that the first response time was 665 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

mobi-c.ru performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

mobi-c.ru

665 ms

mobi-c.ru

697 ms

tag.js

902 ms

index.php

171 ms

rokbox.css

290 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 89% of them (66 requests) were addressed to the original Mobi-c.ru, 3% (2 requests) were made to Code.jivo.ru and 3% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Mobi-c.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 838.7 kB (35%)

Content Size

2.4 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 127.6 kB

  • Original 149.9 kB
  • After minification 137.7 kB
  • After compression 22.3 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 127.6 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 7.6 kB

  • Original 1.0 MB
  • After minification 1.0 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. Mobi C images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 694.7 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 389.8 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 694.7 kB or 64% of the original size.

CSS Optimization

-7%

Potential reduce by 8.8 kB

  • Original 133.8 kB
  • After minification 133.7 kB
  • After compression 124.9 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. Mobi-c.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (62%)

Requests Now

69

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobi-c.ru

mobi-c.ru

665 ms

mobi-c.ru

mobi-c.ru

697 ms

tag.js

tag.js

902 ms

index.php

index.php

171 ms

rokbox.css

rokbox.css

290 ms

legacy.min.css

legacy.min.css

355 ms

bootstrap.min.css

bootstrap.min.css

478 ms

fontawesome-all.min.css

fontawesome-all.min.css

358 ms

template.css

template.css

621 ms

megamenu.css

megamenu.css

370 ms

off-canvas.min.css

off-canvas.min.css

406 ms

squeezebox.css

squeezebox.css

471 ms

settings.css

settings.css

487 ms

dynamic-captions.css

dynamic-captions.css

492 ms

static-captions.css

static-captions.css

523 ms

wk-styles-98d83878.css

wk-styles-98d83878.css

708 ms

jquery.min.js

jquery.min.js

830 ms

jquery-noconflict.js

jquery-noconflict.js

594 ms

jquery-migrate.min.js

jquery-migrate.min.js

614 ms

caption.js

caption.js

653 ms

mootools-core.js

mootools-core.js

948 ms

core.js

core.js

736 ms

mootools-more.js

mootools-more.js

986 ms

rokbox.js

rokbox.js

874 ms

bootstrap.min.js

bootstrap.min.js

939 ms

off-canvas.js

off-canvas.js

858 ms

script.min.js

script.min.js

945 ms

menu.min.js

menu.min.js

984 ms

animate.min.js

animate.min.js

1021 ms

resize.js

resize.js

1056 ms

jquery.easing.min.js

jquery.easing.min.js

1062 ms

squeezebox.min.js

squeezebox.min.js

1062 ms

owl.carousel.js

owl.carousel.js

1225 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1106 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1341 ms

uikit2-d39d1e11.js

uikit2-d39d1e11.js

1405 ms

wk-scripts-3f39a829.js

wk-scripts-3f39a829.js

1178 ms

roma.css

roma.css

1179 ms

BAzqMoDJDU

BAzqMoDJDU

182 ms

jquery.parallax.js

jquery.parallax.js

1252 ms

jquery.unveilEffects.js

jquery.unveilEffects.js

1137 ms

retina-1.1.0.js

retina-1.1.0.js

1018 ms

fhmm.js

fhmm.js

999 ms

application.js

application.js

997 ms

logo.png

logo.png

149 ms

05_bg.jpg

05_bg.jpg

545 ms

S23Ultra.png

S23Ultra.png

149 ms

04_bg.jpg

04_bg.jpg

152 ms

01_setup.png

01_setup.png

150 ms

arm.png

arm.png

150 ms

clients.png

clients.png

432 ms

service1.png

service1.png

434 ms

service2.png

service2.png

537 ms

service3.png

service3.png

435 ms

service4.png

service4.png

434 ms

download.png

download.png

539 ms

update.png

update.png

540 ms

GooglePlay.png

GooglePlay.png

544 ms

qr-code(gp).png

qr-code(gp).png

539 ms

1

1

361 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

836 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

828 ms

arm_background.jpg

arm_background.jpg

791 ms

gridtile.png

gridtile.png

790 ms

featuredbg.jpg

featuredbg.jpg

784 ms

klients_background.jpg

klients_background.jpg

785 ms

footermap.png

footermap.png

748 ms

analytics.js

analytics.js

239 ms

loader.gif

loader.gif

475 ms

BAzqMoDJDU

BAzqMoDJDU

205 ms

revicons.woff

revicons.woff

467 ms

advert.gif

advert.gif

160 ms

collect

collect

16 ms

js

js

76 ms

Accessibility Review

mobi-c.ru accessibility score

78

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.

Best Practices

mobi-c.ru best practices score

58

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

mobi-c.ru SEO score

98

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

High

Tap targets are not sized appropriately

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 Mobi-c.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 Mobi-c.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

mobi-c.ru

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