5.7 sec in total
536 ms
4.4 sec
754 ms
Click here to check amazing Greesha content. Otherwise, check out these important facts you probably never knew about greesha.ru
Visit greesha.ruWe analyzed Greesha.ru page load time and found that the first response time was 536 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
greesha.ru performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value6.3 s
11/100
25%
Value7.0 s
33/100
10%
Value380 ms
70/100
30%
Value0.385
27/100
15%
Value9.1 s
33/100
10%
536 ms
1353 ms
133 ms
64 ms
292 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 59% of them (41 requests) were addressed to the original Greesha.ru, 9% (6 requests) were made to Google.com and 7% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Greesha.ru.
Page size can be reduced by 451.8 kB (34%)
1.3 MB
867.1 kB
In fact, the total size of Greesha.ru main page is 1.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. 50% of websites need less resources to load. Images take 800.9 kB which makes up the majority of the site volume.
Potential reduce by 50.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. 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 50.3 kB or 77% of the original size.
Potential reduce by 77.0 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. Greesha images are well optimized though.
Potential reduce by 246.8 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 246.8 kB or 69% of the original size.
Potential reduce by 77.7 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. Greesha.ru needs all CSS files to be minified and compressed as it can save up to 77.7 kB or 84% of the original size.
Number of requests can be reduced by 36 (56%)
64
28
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greesha. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
greesha.ru
536 ms
www.greesha.ru
1353 ms
wp-emoji-release.min.js
133 ms
css
64 ms
style.css
292 ms
colorbox.css
384 ms
sphinxsearch.css
421 ms
ios-orientationchange-fix.js
425 ms
jquery.js
686 ms
jquery-migrate.min.js
428 ms
jquery.flexslider-min.js
568 ms
jquery.fitvids.js
510 ms
jquery.colorbox-min.js
549 ms
jsapi
44 ms
gfdynamicfeedcontrol.js
47 ms
quoteofday.css
550 ms
mediaelement-and-player.min.js
956 ms
wp-mediaelement.js
633 ms
masonry.min.js
805 ms
gfdynamicfeedcontrol.js
33 ms
library.js
534 ms
bg-paper1.jpg
399 ms
greesha-pm100.jpg
142 ms
search.png
144 ms
facebook.png
142 ms
twitter.png
210 ms
vimeo.png
293 ms
linkedin.png
293 ms
1.png
978 ms
user.png
339 ms
time.png
358 ms
ribbon.png
385 ms
link.png
397 ms
2015-04-14-12-22-22-%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82-%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B01.png
476 ms
superbia.png
491 ms
1418049612_12-nedel-v-godu.png
638 ms
sql.jpg
525 ms
3dd7c17eb8_ir-t-webursitetru-20-amp-l-as2-amp-o-1-amp-a-B004JLMUJU.
583 ms
icon-ivinco.png
627 ms
rss.png
632 ms
linkedin.ico
696 ms
facebook.ico
712 ms
vimeo.ico
762 ms
webursitet.png
764 ms
it-map.png
766 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
59 ms
PIPMHY90P7jtyjpXuZ2cLKCWcynf_cDxXwCLxiixG1c.ttf
75 ms
27 ms
default+en.css
3 ms
default+en.I.js
7 ms
widgets.js
39 ms
watch.js
445 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
5 ms
overlay.png
498 ms
syndication
111 ms
378234612696109056
246 ms
proxy.jpg
258 ms
proxy.jpg
350 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
3 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
5 ms
advert.gif
135 ms
14MF6lvf_normal.jpeg
72 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
51 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
95 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
10 ms
proxy.jpg
191 ms
proxy.jpg
172 ms
1
84 ms
Gfeeds
126 ms
jot.html
2 ms
greesha.ru 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
Links do not have a discernible name
greesha.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
greesha.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greesha.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 Greesha.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.
greesha.ru
Open Graph description is not detected on the main page of Greesha. 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: