13.2 sec in total
1.2 sec
11 sec
922 ms
Visit georex.ru now to see the best up-to-date Georex content for Russia and also check out these interesting facts you probably never knew about georex.ru
Отличные цены на геосинтетику, геосинтетические материалы в Москве и Подмосковье - Звоните ☏ +7 (495) 215 53 29
Visit georex.ruWe analyzed Georex.ru page load time and found that the first response time was 1.2 sec and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
georex.ru performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value9.0 s
1/100
25%
Value8.4 s
18/100
10%
Value2,760 ms
3/100
30%
Value0.039
99/100
15%
Value17.5 s
4/100
10%
1235 ms
290 ms
297 ms
305 ms
305 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 63% of them (74 requests) were addressed to the original Georex.ru, 9% (11 requests) were made to Vk.com and 7% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Connect.facebook.net.
Page size can be reduced by 916.2 kB (34%)
2.7 MB
1.7 MB
In fact, the total size of Georex.ru main page is 2.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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 52.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 52.2 kB or 79% of the original size.
Potential reduce by 59.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. Georex images are well optimized though.
Potential reduce by 620.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 620.3 kB or 73% of the original size.
Potential reduce by 184.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. Georex.ru needs all CSS files to be minified and compressed as it can save up to 184.6 kB or 83% of the original size.
Number of requests can be reduced by 51 (44%)
115
64
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Georex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
georex.ru
1235 ms
default.css
290 ms
bar.css
297 ms
light.css
305 ms
dark.css
305 ms
nivo-slider.css
306 ms
jquery.nivo.slider.pack.js
309 ms
jquery.min.js
101 ms
swfobject.min.js
445 ms
newyear.js
457 ms
style.css
465 ms
kernel_main.css
462 ms
template_21afbfbebd808c35d04b7b0a80d8738a_3443ce5f88a2c78be88b034a377cb297.css
641 ms
colors.css
469 ms
kernel_main.js
802 ms
jquery-1.8.3.min.js
836 ms
kernel_altasib.up.js
653 ms
style.css
639 ms
template_d9d20714128cab469e7c1c3fe9ff89b3_052c96e2a5d35ead7940496d1dfb120c.js
868 ms
jquery.nivo.slider.js
828 ms
script.php
644 ms
modal.css
735 ms
fo4.jpg
196 ms
fo2.jpg
283 ms
tr1.png
283 ms
fo5.jpg
282 ms
logo_GeoRex3.png
193 ms
handst.png
280 ms
chat-support.png
351 ms
georex.jpg
858 ms
reshetka-meba1.jpg
868 ms
bn_georex.jpg
710 ms
bn_georex_1191x300-2.jpg
896 ms
akcija-na-georeshetku5.jpg
2672 ms
aa17e8435b086d23aaa3bb68da066163.jpg
579 ms
0abf1f1ec2fd56c054f84592acd0c734.jpg
670 ms
06a9fd8120183c299a3689d06e54709e.jpeg
854 ms
3e75d3eac1e8ddb26e42d985cb7cf095.png
894 ms
5ca89c481d0a5d6318968b2ee12f0ce1.png
1012 ms
kx.png
1012 ms
aadb1485ac4d7ad7754fbb58c962a8cc.jpg
1012 ms
426e8f63a8b56faccbf1eef051e59140.jpg
1018 ms
93fd26c2fe359a054fc54c69aeb23bf4.jpg
1018 ms
3725276bb4f68e234b24f08e54011236.png
1207 ms
68bda7992ec4978210892ccd685f88c4.jpg
1220 ms
oformit_zakaz4.png
1226 ms
dodm.png
1240 ms
hru.png
1387 ms
skid.png
1353 ms
timer.png
1373 ms
kach.png
1381 ms
zakazat-stroitel-nye-uslugi.jpg
2788 ms
a29de8f79b097c8bfc4382d5ddba2f2e.jpg
1579 ms
916860a23012ea5996e16d2f2ab1a8e6.jpg
2182 ms
d4ad88aa7e5c71b13aa5bd31e84f48ae.jpg
2324 ms
810722ab4b3f1b80211a22aae6ecc043.jpeg
2333 ms
90567253130f1b29a3c3b2901a65546e.jpg
1710 ms
TriAx_170_white.ashx.jpg
1828 ms
analytics.js
136 ms
watch.js
3 ms
Lawn_lattice_romb.jpg
1832 ms
collect
57 ms
4d9f160aa85f9cfc49b0c5402b5b47e2.jpg
1913 ms
bbb919929e267ff940d40600becdcdbd.gif
2053 ms
e686119ea9c983c8a6927814c65ee4b3.jpg
2076 ms
21650fabda14b87d62f80578b1be366e.jpg
2197 ms
d9e8a726cd22d2e72b83dd2b212602bb.jpg
2207 ms
css
133 ms
5.png
2144 ms
H5zQYJUksp
288 ms
bg_popup.png
1909 ms
f1.jpg
1969 ms
loading.gif
1936 ms
widget_ru_RU.js
255 ms
rex.png
1792 ms
gui.png
2156 ms
kp.png
1898 ms
star1.png
1905 ms
footer_h4_bg1.png
1900 ms
3.png
1804 ms
spacer.gif
1985 ms
widgets.js
1383 ms
all.js
2931 ms
plusone.js
303 ms
openapi.js
459 ms
chat_ru_RU.js
2020 ms
georex.ru
424 ms
bullets.png
192 ms
cb=gapi.loaded_0
31 ms
cb=gapi.loaded_1
71 ms
fastbutton
144 ms
postmessageRelay
104 ms
cb=gapi.loaded_0
56 ms
cb=gapi.loaded_1
44 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
354 ms
upload.gif
188 ms
widget_like.php
412 ms
1077434459-postmessagerelay.js
284 ms
rpc:shindig_random.js
43 ms
cb=gapi.loaded_0
72 ms
loader_nav19239_3.js
786 ms
lite.css
2200 ms
lite.js
1608 ms
lang3_0.js
1350 ms
widgets.css
1350 ms
xdm.js
1352 ms
al_like.js
1367 ms
button.71000885400e222c3c0eec823f8f93f0.js
730 ms
main.css
1660 ms
tweet_button.fd774b599f565016d763dd860cb31c79.ru.html
71 ms
jot
451 ms
225 ms
xd_arbiter.php
278 ms
xd_arbiter.php
579 ms
like.php
319 ms
like_widget.png
153 ms
OZhivdPHVp_.js
2118 ms
LVx-xkvaJ0b.png
2546 ms
georex.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
<frame> or <iframe> elements do not have a title
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
georex.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
georex.ru SEO score
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Georex.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 Georex.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.
georex.ru
Open Graph description is not detected on the main page of Georex. 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: