Tools & Wizards About Us
imobis.ru screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

imobis.ru

ИМОБИС сервис автоматической массовой рассылки клиентам сообщений через СМС, Вайбер, ВК

Page Load Speed

6.4 sec in total

First Response

423 ms

Resources Loaded

5.4 sec

Page Rendered

522 ms

imobis.ru screenshot

About Website

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

Официальные каналы, открытое API для рассылки, гибкие цены. Помогаем бизнесу доставлять таргетированные сообщения клиентам

Visit imobis.ru

Key Findings

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

Performance Metrics

imobis.ru performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value19.4 s

0/100

10%

TBT (Total Blocking Time)

Value5,970 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.578

12/100

15%

TTI (Time to Interactive)

Value47.0 s

0/100

10%

Network Requests Diagram

imobis.ru

423 ms

imobis.ru

1280 ms

style.min.css

417 ms

styles.css

414 ms

cf7msm.css

415 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 59% of them (52 requests) were addressed to the original Imobis.ru, 9% (8 requests) were made to Vk.com and 7% (6 requests) were made to Cdn-ru.bitrix24.ru. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Imobis.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (31%)

Content Size

6.3 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imobis.ru main page is 6.3 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. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 428.9 kB

  • Original 522.6 kB
  • After minification 503.5 kB
  • After compression 93.7 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 428.9 kB or 82% of the original size.

Image Optimization

-19%

Potential reduce by 711.4 kB

  • Original 3.8 MB
  • After minification 3.1 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. Obviously, Imobis needs image optimization as it can save up to 711.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 453.7 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 788.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 453.7 kB or 37% of the original size.

CSS Optimization

-46%

Potential reduce by 323.8 kB

  • Original 711.4 kB
  • After minification 704.6 kB
  • After compression 387.6 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. Imobis.ru needs all CSS files to be minified and compressed as it can save up to 323.8 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (65%)

Requests Now

80

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imobis.ru

imobis.ru

423 ms

imobis.ru

imobis.ru

1280 ms

style.min.css

style.min.css

417 ms

styles.css

styles.css

414 ms

cf7msm.css

cf7msm.css

415 ms

intlTelInput.min.css

intlTelInput.min.css

554 ms

countrySelect.min.css

countrySelect.min.css

569 ms

font-awesome.min.css

font-awesome.min.css

569 ms

front.min.css

front.min.css

551 ms

pum-site-styles.css

pum-site-styles.css

552 ms

flatsome.css

flatsome.css

831 ms

style.css

style.css

826 ms

css

css

36 ms

jquery.min.js

jquery.min.js

963 ms

jquery-migrate.min.js

jquery-migrate.min.js

690 ms

jquery.maskedinput.js

jquery.maskedinput.js

708 ms

twocolumns.css

twocolumns.css

709 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

826 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

849 ms

wp-polyfill.min.js

wp-polyfill.min.js

1175 ms

index.js

index.js

960 ms

cf7msm.min.js

cf7msm.min.js

998 ms

intlTelInput.min.js

intlTelInput.min.js

999 ms

countrySelect.min.js

countrySelect.min.js

1035 ms

flatsome-live-search.js

flatsome-live-search.js

1137 ms

front.min.js

front.min.js

1136 ms

core.min.js

core.min.js

1137 ms

pum-site-scripts.js

pum-site-scripts.js

1137 ms

wpcf7-recaptcha-controls.js

wpcf7-recaptcha-controls.js

1174 ms

api.js

api.js

35 ms

hoverIntent.min.js

hoverIntent.min.js

1235 ms

flatsome.js

flatsome.js

1508 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

208 ms

gtm.js

gtm.js

162 ms

Fromni_logo.png

Fromni_logo.png

431 ms

logo.png

logo.png

266 ms

telegram-3.png

telegram-3.png

408 ms

whatsapp-v1.png

whatsapp-v1.png

309 ms

vk.png

vk.png

309 ms

sms.png

sms.png

396 ms

viber.png

viber.png

404 ms

icons8_push_notifications.svg

icons8_push_notifications.svg

453 ms

4-150x100.png

4-150x100.png

452 ms

hoff-150x100.png

hoff-150x100.png

533 ms

5-1-150x100.png

5-1-150x100.png

540 ms

6-150x100.png

6-150x100.png

547 ms

2-1-150x100.png

2-1-150x100.png

595 ms

1-1-150x100.png

1-1-150x100.png

594 ms

novost-pro-gut-1.jpg

novost-pro-gut-1.jpg

1423 ms

novost-3.png

novost-3.png

1153 ms

novost-pro-telegu-3.jpg

novost-pro-telegu-3.jpg

1504 ms

loader_25.js

loader_25.js

538 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

133 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

134 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

136 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

664 ms

map-footer.png

map-footer.png

678 ms

pattern-learn.png

pattern-learn.png

1147 ms

bg_white.svg

bg_white.svg

674 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

208 ms

upload.gif

upload.gif

230 ms

widget_community.php

widget_community.php

362 ms

loader_3_w0khpw.js

loader_3_w0khpw.js

745 ms

loader_29.js

loader_29.js

507 ms

loader_3.js

loader_3.js

511 ms

fl-icons.css

fl-icons.css

624 ms

rtrg

rtrg

305 ms

form.polyfill.js

form.polyfill.js

270 ms

loader_nav211113092742_3.js

loader_nav211113092742_3.js

248 ms

fonts_cnt.c7a76efe.css

fonts_cnt.c7a76efe.css

1021 ms

lite.6d09ff63.css

lite.6d09ff63.css

771 ms

lang3_2.js

lang3_2.js

544 ms

c3d11fba.093082a5.js

c3d11fba.093082a5.js

639 ms

xdm.js

xdm.js

625 ms

base.c26e5b58.css

base.c26e5b58.css

646 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

527 ms

app.js

app.js

310 ms

tag.js

tag.js

1144 ms

recaptcha__ru.js

recaptcha__ru.js

218 ms

fl-icons.ttf

fl-icons.ttf

313 ms

app.bundle.min.css

app.bundle.min.css

579 ms

app.bundle.min.js

app.bundle.min.js

828 ms

upload.gif

upload.gif

100 ms

code.js

code.js

769 ms

advert.gif

advert.gif

525 ms

fb8df59b9500a7beafbd19d29ab15492.png

fb8df59b9500a7beafbd19d29ab15492.png

129 ms

counter

counter

131 ms

dyn-goal-config.js

dyn-goal-config.js

256 ms

Accessibility Review

imobis.ru accessibility score

77

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

[aria-*] attributes do not match their roles

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

High

Page has valid source maps

SEO Factors

imobis.ru SEO score

92

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

    RU

  • Encoding

    UTF-8

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

imobis.ru

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