Access assistor.ru. Перенаправление домена не осуществляется

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

assistor.ru

687 ms

www.assistor.ru

1478 ms

jquery.min.js

19 ms

kernel_main.css

500 ms

kernel_socialservices.css

506 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 90% of them (73 requests) were addressed to the original Assistor.ru, 4% (3 requests) were made to Web.redhelper.ru and 2% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Assistor.ru.

Content Size

2.3 MB

After Optimization

1.8 MB

In fact, the total size of Assistor.ru main page is 2.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. 40% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 33.9 kB

Original 44.2 kB
After minification 38.7 kB
After compression 10.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. This page needs HTML code to be minified as it can gain 5.5 kB, which is 12% 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 33.9 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 80.0 kB

Original 1.8 MB
After minification 1.7 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. Assistor images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 305.3 kB

Original 377.6 kB
After minification 302.1 kB
After compression 72.3 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 305.3 kB or 81% of the original size.

CSS Optimization

-88%

Potential reduce by 81.1 kB

Original 92.2 kB
After minification 76.5 kB
After compression 11.1 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. Assistor.ru needs all CSS files to be minified and compressed as it can save up to 81.1 kB or 88% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

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

assistor.ru

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Перенаправление домена не осуществляется

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

assistor.ru

www.assistor.ru

jquery.min.js

kernel_main.css

kernel_socialservices.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

assistor.ru

www.assistor.ru

jquery.min.js

kernel_main.css

kernel_socialservices.css

template_eecd67de532a55b5d87c128b7e95dfc9.css

kernel_main.js

kernel_socialservices.js

slider_good1.js

main.js

slide.js

ba.js

spread.php

fon.png

header-bg.png

logo.png

vhod.jpg

slide.gif

batton_zau.gif

batton_au.gif

%D0%9A%D0%B0%D0%BB%D0%B8%D0%BD%D0%B8%D0%BD%D0%B0.png

12.jpg

yacuk.png

isakova.png

bqqenf.png

%D0%9D%D0%B0%D0%BC%D1%8B%D1%81%D1%82%D1%8E%D0%BA.png

a_ef74ef07.jpg

footer-left.gif

footer-right.gif

icons_v1.png

login-input.png

bg.png

line.gif

menu-bg.png

menu-right.png

menu-left.png

menu-slash.png

logo-1.png

logo-2.png

logo-3.png

logo-4.png

logo-5.png

logo-7.png