8 sec in total
786 ms
6.7 sec
495 ms
Welcome to greedman.com homepage info - get ready to check Greedman best content for Russia right away, or after learning these important things about greedman.com
главная страница сайта
Visit greedman.comWe analyzed Greedman.com page load time and found that the first response time was 786 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
greedman.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.3 s
69/100
25%
Value4.5 s
72/100
10%
Value2,010 ms
7/100
30%
Value0
100/100
15%
Value9.3 s
31/100
10%
786 ms
167 ms
684 ms
871 ms
1157 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 66% of them (67 requests) were addressed to the original Greedman.com, 7% (7 requests) were made to Api-maps.yandex.ru and 5% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Api-maps.yandex.ru.
Page size can be reduced by 484.2 kB (50%)
965.5 kB
481.2 kB
In fact, the total size of Greedman.com main page is 965.5 kB. 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. Javascripts take 433.2 kB which makes up the majority of the site volume.
Potential reduce by 48.9 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 48.9 kB or 80% of the original size.
Potential reduce by 39.6 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, Greedman needs image optimization as it can save up to 39.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 271.4 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 271.4 kB or 63% of the original size.
Potential reduce by 124.3 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. Greedman.com needs all CSS files to be minified and compressed as it can save up to 124.3 kB or 84% of the original size.
Number of requests can be reduced by 46 (51%)
91
45
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greedman. 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 14 to 1 for CSS and as a result speed up the page load time.
greedman.com
786 ms
subscribe.css
167 ms
qonline.css
684 ms
faq.css
871 ms
doska.css
1157 ms
catalog.css
977 ms
js_start_functions_on_load.js
323 ms
js_photogallery.js
976 ms
photogallery.css
839 ms
js_lib_general.js
958 ms
objajax.php
989 ms
js_general_send_message_email.js
985 ms
lib_upload_files.js
1135 ms
301 ms
manager_yandex_maps.php
1249 ms
js_set_geo_user.js
1151 ms
jsqonline.js
1241 ms
js_main_config_sp.php
1244 ms
css_bowwindow_main_sp.php
1301 ms
js_bowwindow_main_sp.php
1298 ms
js_abuse_adv.js
1300 ms
driver_slide_doska.js
1325 ms
js_abuse_object.js
1343 ms
css
248 ms
css
296 ms
jquery.min.js
2986 ms
stylehablon.css
1433 ms
indexstyle.css
1439 ms
api.js
247 ms
modernizr.custom.js
1434 ms
jquery.nicescroll.js
2792 ms
component.css
1490 ms
down.css
2168 ms
font-awesome.css
1578 ms
adsbygoogle.js
121 ms
cbpAnimatedHeader.min.js
1576 ms
classie.js
1635 ms
860 ms
combine.xml
3000 ms
recaptcha__en.js
422 ms
bannerovich_ru_file_4378_726x110(PRJ746).jpg
829 ms
logo.png
2099 ms
arrow_left.png
195 ms
arrow_right.png
193 ms
376o9ab6.png
197 ms
382o9b55.png
196 ms
386obb60.png
192 ms
378of4f8.png
611 ms
381o0078.png
1384 ms
380o35c1.png
375 ms
377o2e5c.png
1381 ms
383oae71.png
1792 ms
icon-category6.png
600 ms
icon_on_premium.png
744 ms
icon_on_vip.png
781 ms
icon_on_pickout.png
923 ms
icon_on_makegood.png
926 ms
icon_premium_small.png
1024 ms
icon_vip_small.png
1085 ms
icon_pickout_small.png
1373 ms
icon_up_small.png
1808 ms
default.jpg
1607 ms
b74aac8a87d2241c96c77bfc15f2f50b.jpg
1543 ms
1f05b7c39cf0da41a732d11e4a0bf362.jpg
1603 ms
icon_makegood_small.png
1731 ms
bb0338d682661a10275f72faba606f45.jpg
1731 ms
382o9b55.png
1735 ms
376o9ab6.png
1930 ms
icon-category6.png
1930 ms
fontawesome-webfont.woff
2622 ms
KelsonSansLight.woff
2642 ms
3_0_20CCFFFF_00ACFFFF_1_pageviews
1597 ms
icon_marger_geo_select.png
1912 ms
rss_icon_board.png
2340 ms
m.png
2006 ms
q.png
2208 ms
y.png
2115 ms
bannerovich_ru_file_3690_270x270(PRJ4965).jpg
1299 ms
ca-pub-6858665780008699.js
840 ms
zrt_lookup.html
447 ms
show_ads_impl.js
296 ms
watch.js
1 ms
hit
472 ms
analytics.js
157 ms
collect
81 ms
ads
385 ms
osd.js
253 ms
hit
193 ms
3938644442375544542
88 ms
abg.js
89 ms
m_js_controller.js
118 ms
googlelogo_color_112x36dp.png
48 ms
x_button_blue2.png
16 ms
s
65 ms
redir.html
463 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
332 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
346 ms
4965b66fe115b2f2ed500ece66514d86.cur
531 ms
77492cf358d8b12629399322926c93f2.cur
664 ms
iframe.html
53 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
58 ms
greedman.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
greedman.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
greedman.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greedman.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that Greedman.com 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.
greedman.com
Open Graph description is not detected on the main page of Greedman. 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: