13 sec in total
1.1 sec
11 sec
883 ms
Welcome to graus.ru homepage info - get ready to check Graus best content for Russia right away, or after learning these important things about graus.ru
Надоел посторонний шум в квартире? Закажите шумоизоляцию стен, пола и потолков из современных звукопоглощающих материалов
Visit graus.ruWe analyzed Graus.ru page load time and found that the first response time was 1.1 sec and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
graus.ru performance score
name
value
score
weighting
Value3.3 s
42/100
10%
Value12.3 s
0/100
25%
Value6.8 s
35/100
10%
Value900 ms
32/100
30%
Value1.675
0/100
15%
Value8.9 s
34/100
10%
1127 ms
1964 ms
323 ms
3393 ms
322 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 87% of them (110 requests) were addressed to the original Graus.ru, 2% (2 requests) were made to Loginza.ru and 2% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Graus.ru.
Page size can be reduced by 946.5 kB (47%)
2.0 MB
1.1 MB
In fact, the total size of Graus.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. 50% of websites need less resources to load. Images take 975.9 kB which makes up the majority of the site volume.
Potential reduce by 76.0 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 26.4 kB, which is 28% 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 76.0 kB or 82% of the original size.
Potential reduce by 132.1 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, Graus needs image optimization as it can save up to 132.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 569.9 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 569.9 kB or 75% of the original size.
Potential reduce by 168.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. Graus.ru needs all CSS files to be minified and compressed as it can save up to 168.5 kB or 85% of the original size.
Number of requests can be reduced by 35 (30%)
117
82
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Graus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
graus.ru
1127 ms
kernel_main.css
1964 ms
template_270de10954a2e05a9956334b98878b96_6c161e0fc77154462ab12728669922f3.css
323 ms
kernel_main.js
3393 ms
kernel_tcsbank.kupivkredit.js
322 ms
template_1ff4a9abe21506b8d8b84ca5db1e2877_57e2f8219e37e76511118425982bc273.js
317 ms
style.css
2285 ms
catalog.css
800 ms
social-likes_classic.css
1314 ms
jquery.nouislider.css
496 ms
jquery.min.1.8.2.js
2751 ms
jquery.tools.min.js
1061 ms
jquery.fancybox.pack.js
2293 ms
jquery.selectbox.js
1650 ms
jquery.dotdotdot.min.js
1817 ms
jquery.bxslider.min.js
2152 ms
jquery.nouislider.min.js
2150 ms
scripts.js
2621 ms
social-likes.min.js
2306 ms
jquery.fancybox.css
2412 ms
mobilyslider.js
2422 ms
jquery.fancybox.pack.js
2612 ms
jquery.placeholder.js
2585 ms
jquery.validate.js
3024 ms
jquery.maskedinput.min.js
2732 ms
jquery.disable.text.select.pack.js
2757 ms
jivosite.css
2766 ms
jivosite.js
2908 ms
jquery.easing.js
2911 ms
script.js
3042 ms
widget.js
459 ms
ba.js
320 ms
sign_in_button_gray.gif
443 ms
slic_header_bg.png
426 ms
v1.png
430 ms
f1.png
430 ms
i1.png
997 ms
t1.png
428 ms
y1.png
1855 ms
logo.png
438 ms
83cdade70650abb8fe5d1fbad2c5df5b.jpeg
432 ms
nouser.png
432 ms
e84b0dafa64e1e55a7c67dfd4dbcbe1f.jpeg
435 ms
744dc31a410d79c7aee3f5cc74cec386.jpeg
581 ms
a5938b98b478fb2b939777eb2794bf47.jpeg
582 ms
2a9b90d268315da46915c80bdc15748a.jpg
778 ms
98d5ffe1db7cf7d36b56029c77d91ccb.png
775 ms
2a13a631f29a5c2731f947c51b38166b.gif
832 ms
a6884187d535418fd09af868ef14d05e.png
772 ms
a859702ffee9562d6e46f7aae5a1e605.jpg
851 ms
b1feb46656be8673218bd5070eddb65c.png
1837 ms
92bbc6e72d1f5d50f9797df332637604.gif
872 ms
ac9cc3bdcb90ebdd66a5c9c766e41ef6.jpg
1151 ms
7e426f2b100b7755e51f9bc3ea1bf99e.gif
1645 ms
3d29302e54ee56b9a03764c511b28af8.png
1026 ms
6ce66320c8e974d013f32361e76fec28.png
1127 ms
3ccf47b036def8a9938477c565cec8d3.jpg
1163 ms
fda9a2ee065ba171ad901417029c0131.png
1282 ms
f858e2512d3b760bda685b13be4fa7b4.JPG
1299 ms
dad6b36f003a3f331ebde0e104a55ae7.jpg
1337 ms
92db1b930fc970c219464de689ed9105.png
1886 ms
2820484453ad431a9614031e3c5eca33.gif
2386 ms
908105c697ba29f6c59daf5c1fcdc985.png
1713 ms
a2e9ac7139acca59318b64431b4d9387.png
2629 ms
e100f6f25ac30be42e64c5d09bdb084b.gif
1908 ms
8b924e3f20f2ff5a094508c9dab4665e.jpg
2181 ms
151ca521818ddaf6dc45140baae7514f.gif
2332 ms
e27e08884747065ae10c2b0b3bb51eeb.png
2041 ms
a141e15b6861113cbf5f3a7d4aae1904.png
2044 ms
41614
301 ms
watch.js
222 ms
analytics.js
1620 ms
analytics.js
240 ms
bx_stat
585 ms
RobotoCondensedBold.woff
2142 ms
OpenSansLight.woff
2000 ms
OpenSansBold.woff
2214 ms
RobotoCondensedLight.woff
3324 ms
HelveticaLight.woff
2109 ms
a37124a451bc70b1eda0953cdaa31323.png
2178 ms
5a9e6299135e2eb962bc00bfae8879a7.gif
2244 ms
8da674051e6e9fe0b8020353352feb81.jpg
2247 ms
fql
943 ms
count.json
54 ms
share.php
1251 ms
collect
310 ms
widget_ru_RU.js
1275 ms
cartprotector.js
226 ms
bdf6d45f2fdbc4c0c261bb652b734ead.gif
2156 ms
8e2f2f4420510a5bee7514309a044dd1.jpg
3323 ms
407b1164632c0799c5e2d66550423b39.png
2023 ms
259294044de76cdd9aff238ae203a963.gif
2060 ms
5d538f05ab23ca0f48bedba432bb632a.png
2052 ms
9ce7e1bae37027639a79e54be6c6cb7c.png
2233 ms
b301b660d95e50fd417d51f34d6f0610.png
2105 ms
c8590da3de25be2b2b07104ee75748d2.jpg
2119 ms
efb47ffc8289914c37aafc7c7005faf9.jpg
1998 ms
sprite.png
3285 ms
52fccfcc76caa5e98a51e5704b82ddfc.jpg
3510 ms
b988b1ed2457d23ace3209a58deace1c.jpg
2411 ms
0ae494cbae1c231d222bb5f8277e050f.jpg
2512 ms
45ddd831c4bf8ec5ba054d3aa8d03abb.jpg
2927 ms
3c61d7c167b0113e7a28a3f36b2a1cd5.jpg
3009 ms
1fa75e3283033ee02d86275c4afed508.jpg
3024 ms
3c3416a73ce754f1238367d495fcbb32.jpg
2724 ms
80383b16250b373f5a2038f7ada3732a.jpg
2798 ms
analytics.js
538 ms
67b16b0e8aba085a0b3f85630e6cdfca.jpg
2839 ms
line.png
2626 ms
6ec9194a080aced94ee72f5d5215399d.jpg
3687 ms
13197e451fd86aee3de44d8ffbd7ebe6.jpg
3112 ms
726967a0a2f913f9203cf5ee335469a4.jpg
3720 ms
acb62beeb578edaaf5aed3dc684928db.jpg
3711 ms
c5b5283efc9441dd20015693fb9c1809.jpg
2803 ms
56f8e81c8dd8fd24096dc9200e2ce0aa.jpg
2685 ms
ad39ae305d65cfa9f943c09a50868f4f.jpg
2862 ms
f509a905773f8e47edce5e837a89b745.jpg
2906 ms
rate-2.png
2607 ms
up-arrow.png
2711 ms
i3.png
2846 ms
i4.png
2865 ms
i1.png
3536 ms
shadow.png
2947 ms
i55.png
2975 ms
i54.png
3149 ms
iframe
116 ms
graus.ru accessibility score
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
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
graus.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
graus.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Graus.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 Graus.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.
graus.ru
Open Graph description is not detected on the main page of Graus. 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: