10.5 sec in total
411 ms
9.3 sec
722 ms
Click here to check amazing Generator content for Russia. Otherwise, check out these important facts you probably never knew about generator.ru
Группа компаний «ВЕПРЬ» более 20 лет является лидером на российском рынке по проектированию, производству, продаже и сервисному обслуживанию электрооборудования бытового, профессионального и специальн...
Visit generator.ruWe analyzed Generator.ru page load time and found that the first response time was 411 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
generator.ru performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.5 s
37/100
25%
Value17.3 s
0/100
10%
Value3,520 ms
1/100
30%
Value0.015
100/100
15%
Value47.2 s
0/100
10%
411 ms
1092 ms
26 ms
437 ms
438 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 76% of them (99 requests) were addressed to the original Generator.ru, 8% (11 requests) were made to Api-maps.yandex.ru and 3% (4 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Generator.ru.
Page size can be reduced by 1.3 MB (10%)
12.7 MB
11.4 MB
In fact, the total size of Generator.ru main page is 12.7 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. 70% of websites need less resources to load. Images take 11.3 MB which makes up the majority of the site volume.
Potential reduce by 332.2 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 332.2 kB or 78% of the original size.
Potential reduce by 836.4 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. Generator images are well optimized though.
Potential reduce by 76.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. This website has mostly compressed JavaScripts.
Potential reduce by 43.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. Generator.ru needs all CSS files to be minified and compressed as it can save up to 43.6 kB or 19% of the original size.
Number of requests can be reduced by 54 (45%)
121
67
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Generator. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
generator.ru
411 ms
generator.ru
1092 ms
jquery.fancybox.min.css
26 ms
styles.css
437 ms
owl.carousel.min.css
438 ms
styles.css
406 ms
mobile.css
640 ms
slick.css
438 ms
slick-theme.css
503 ms
mdl.css
788 ms
style.css
814 ms
style.css
836 ms
style.css
804 ms
style.css
1044 ms
core.js
1614 ms
protobuf.js
1196 ms
model.js
815 ms
rest.client.js
1308 ms
pull.client.js
830 ms
jquery.fancybox.min.js
23 ms
654 ms
jquery.min.js
531 ms
jquery-3.3.1.min.js
20 ms
jquery.validate.min.js
20 ms
mdl.js
844 ms
owl.carousel.min.js
1450 ms
slick.min.js
857 ms
custom.js
869 ms
jquery.maskedinput.js
881 ms
mask.js
892 ms
script.js
904 ms
script.js
914 ms
script.js
924 ms
script.js
934 ms
script.js
945 ms
jqueryui.js
300 ms
data.js
840 ms
regions_districts.js
851 ms
script.js
859 ms
455 ms
ba.js
307 ms
css2
40 ms
map.js
512 ms
tag.js
980 ms
logo_menu.svg
393 ms
logos.svg
386 ms
7b50a61a7c976b622924091e5df79ec1.png
552 ms
8e49ee152b32803ca7cef5b9e0c15396.png
418 ms
6f50a8ea83631b5a7a7a0a6870ed3477.png
418 ms
83252be40d9a47ce0a437da0027210fd.png
502 ms
0c164c8b2de7df93e34130244fafcc44.png
774 ms
8c21f9afcd8d2e1b65099af53b71779a.png
938 ms
5e2fad485d9b9e596da9a65a428aa385.png
948 ms
b8c7f2ec9e53582d189be41f1d7c5687.png
814 ms
v94wu1oy69gnet3wrcn4xts8gkdahjpq.png
1472 ms
1753868c87f46d85001e5c150c22064e.jpg
1200 ms
97b0cffebd77b94f050e7cb3322bf3f2.png
1979 ms
bf418830c4fab9aeea64eb9913143f19.jpg
1225 ms
b0f09a04121bcd2ab97fdce3c2ea62a4.jpg
1893 ms
about1.svg
1341 ms
about2.svg
1577 ms
about3.svg
1369 ms
7b50a61a7c976b622924091e5df79ec1.png
2424 ms
b58e632969342cfbd1c804554732d0f1.png
1788 ms
8e49ee152b32803ca7cef5b9e0c15396.png
2362 ms
caf52545533b40c26a9d8ce2a2dcfeed.png
2388 ms
6f50a8ea83631b5a7a7a0a6870ed3477.png
2172 ms
cb3022e9cce09690793f44ff987d8caa.png
2882 ms
83252be40d9a47ce0a437da0027210fd.png
2788 ms
c7801630277bd5ac2b99546c39fe9012.png
2556 ms
0c164c8b2de7df93e34130244fafcc44.png
3083 ms
29d2e10d09ee030e8831d8cc7e932e95.png
3115 ms
8c21f9afcd8d2e1b65099af53b71779a.png
3159 ms
6639780a1986bdb0e953147f2eab23b9.png
2938 ms
5e2fad485d9b9e596da9a65a428aa385.png
3527 ms
806f63fecbf9388f6c10e805411464a7.png
3416 ms
b8c7f2ec9e53582d189be41f1d7c5687.png
3084 ms
4ee28355f46b5e2f0e85e5029bb7dc61.png
3914 ms
aa484aa3bf9120784a31f22d799875b3.png
3460 ms
e366bf7ff3eed1490e95c21d5ef328ef.png
3956 ms
font
63 ms
loader_6_0qhrr3.js
785 ms
bx_stat
187 ms
d2780f1e17b36cd44611e14d83efb39f.png
3621 ms
fc5f3af6b5951acf585a0c75c65b8ab9.png
3829 ms
c55ecb52f41adec2b483118b4fe8d931.png
3465 ms
7d6919ada0fe30f2f629f338e26d98bc.png
3824 ms
combine.js
2150 ms
combine.js
1504 ms
41825b8cde5bb1763a8c28c372350878.png
3734 ms
8a585c9cccc78e5f6ede1e34ade8c7a2.png
4124 ms
3eb47946ed2a825edc1f30e0df510f2c.jpg
3788 ms
call.tracker.js
171 ms
styles.min.css
1098 ms
script.min.js
1339 ms
9ffc679f6df703981306e48d297c4b9f.png
3808 ms
e35c26d51be883b7867363f6484b451d.jpg
3980 ms
advert.gif
695 ms
5caea621077dc129f8af48a098bc4123.jpg
3473 ms
d3c7e9ce4dc84858c6ece255c2d7ee3e.jpg
3846 ms
38bc58db7c54987b69c42a423944de4e.svg
3643 ms
18d43ac86911368f812d6b3b9d9e23f2.svg
3683 ms
f04a57e1c28cd7a918fe54def2836ff4.svg
3699 ms
b0037e4083cf4c8553fd16334358c24a.svg
3732 ms
sync_cookie_image_decide
144 ms
97e0b9361ba8245ce25a7d725e4328b5.svg
3519 ms
969935e38e91e49e6d9c965eb4ec6ffb.svg
3505 ms
563ec0119a2b684f6793eeeaa1f42feb.svg
3454 ms
util_cursor_storage_grab.cur
147 ms
util_cursor_storage_grabbing.cur
290 ms
util_cursor_storage_help.cur
387 ms
util_cursor_storage_zoom_in.cur
424 ms
1
145 ms
167c32cfae41240a2e5d2cd7a2731778.svg
3297 ms
tag_phone.js
195 ms
logo_bottom.svg
3236 ms
pay1.svg
3293 ms
pay2.svg
3260 ms
pay3.svg
2980 ms
apszo.svg
3022 ms
util_cursor_storage_grab.cur
150 ms
combine.js
150 ms
close_menu.svg
3008 ms
phone_icon.svg
3015 ms
search_icon.svg
2929 ms
arrow_bottom_icon.svg
2974 ms
ajax-loader.gif
2983 ms
service.webp
3064 ms
main.js
2733 ms
upload-man-mini-1.png
122 ms
generator.ru accessibility score
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
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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 IDs are not unique
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 [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>).
generator.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
Browser errors were logged to the console
Page has valid source maps
generator.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 Generator.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 Generator.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.
generator.ru
Open Graph description is not detected on the main page of Generator. 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: