9.7 sec in total
694 ms
8.8 sec
163 ms
Click here to check amazing Geolife content for Russia. Otherwise, check out these important facts you probably never knew about geolife.org
Информационный портал группы компаний "Геолайф". Новости и события геоинформационного сообщества. Телематические услуги.
Visit geolife.orgWe analyzed Geolife.org page load time and found that the first response time was 694 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
geolife.org performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value15.3 s
0/100
25%
Value17.7 s
0/100
10%
Value430 ms
65/100
30%
Value0.202
61/100
15%
Value24.0 s
1/100
10%
694 ms
134 ms
255 ms
252 ms
273 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 83% of them (50 requests) were addressed to the original Geolife.org, 3% (2 requests) were made to Bitrix.info and 3% (2 requests) were made to Cs15.livetex.ru. The less responsive or slowest element that took the longest time to load (7.3 sec) belongs to the original domain Geolife.org.
Page size can be reduced by 258.6 kB (6%)
4.2 MB
4.0 MB
In fact, the total size of Geolife.org main page is 4.2 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. 35% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 26.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. 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 26.0 kB or 74% of the original size.
Potential reduce by 80.5 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. Geolife images are well optimized though.
Potential reduce by 143.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 143.9 kB or 41% of the original size.
Potential reduce by 8.2 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. Geolife.org needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 31% of the original size.
Number of requests can be reduced by 14 (25%)
55
41
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geolife. 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 from 6 to 1 for CSS and as a result speed up the page load time.
geolife.org
694 ms
common.css
134 ms
kernel_main.css
255 ms
page_d94ef7c2866ca24a136315579988764a.css
252 ms
template_8bb36ad8961247451d3cd988428f5806.css
273 ms
kernel_main.js
766 ms
kernel_bisexpert.owlslider.js
527 ms
template_c92b2bab1ff13375168667f12d884c5d.js
265 ms
colors.css
377 ms
jquery-1.11.3.min.js
552 ms
lightbox.min.js
400 ms
lightbox.css
401 ms
owl.carousel.min.js
502 ms
ba.js
138 ms
3_0_DBDBDBFF_BBBBBBFF_0_pageviews
248 ms
close.png
131 ms
loading.gif
128 ms
prev.png
129 ms
next.png
128 ms
header.png
129 ms
logo.svg
258 ms
ce1bd03eef3f34a25d2eb4bf2914f4d4.png
1767 ms
e2eccc13a422bcf3397c18bb36e82d5b.png
1760 ms
adfb468c2d4c12cb28be7301a1c7cfda.jpg
2191 ms
b4ad269ff5ffc734e1e06f91510f3bad.png
7324 ms
50de92193ff9be290828cb6c9efdc9f7.png
1723 ms
89f90b9a1ad6a3795841c37155083278.png
1435 ms
bf8e840b8ec475ee6137786c80c058a3.jpeg
1564 ms
f2552b6f015ab32ebbe1ce2b8479cb01.jpg
1693 ms
67956d9de38cdd56fda1f1fe9966b934.jpg
1822 ms
b058b28d80162b4d9f482ee32264797a.jpg
1859 ms
123f1f23ec7d0e953da62c05a78986ba.jpg
1886 ms
fc617faa4e0b602fce770a058eaf9606.jpg
1893 ms
7bab7c01bce5d2103ad1215c3ace2dce.jpg
1951 ms
02503f9fa2c1cd774d829e314083b772.jpg
1992 ms
c7f3df631cf9b917d5877fd8da56b27c.jpg
2012 ms
a0ab09c8b1edddf7ba91261abc0c61b6.gif
2023 ms
g_ru_glonass.svg
2081 ms
g_ru_payment.svg
2126 ms
g_ru_assistant.svg
2137 ms
g_ru_security.svg
2149 ms
g_ru_auto.svg
2209 ms
g_ru_persona.svg
2260 ms
g_ru_insurance.svg
2263 ms
1_vk.png
2276 ms
2_fb.png
2317 ms
6_odn.png
2337 ms
3_tw.png
2390 ms
8_yt.png
2388 ms
4_g+.png
2401 ms
client.js
525 ms
watch.js
0 ms
analytics.js
21 ms
slider-arrow-left.png
2372 ms
collect
27 ms
bx_stat
70 ms
slider-arrow-right.png
2342 ms
client.js
536 ms
widgetsSettings.json
448 ms
app3.js
502 ms
geolife.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
geolife.org 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
geolife.org 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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geolife.org 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 Geolife.org 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.
geolife.org
Open Graph description is not detected on the main page of Geolife. 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: