Tools & Wizards About Us
amebas.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

amebas.ru

Амёбы — эволюция искусственной жизни на вашем компьютере

Page Load Speed

8.4 sec in total

First Response

978 ms

Resources Loaded

6.7 sec

Page Rendered

775 ms

amebas.ru screenshot

About Website

Visit amebas.ru now to see the best up-to-date Amebas content for Russia and also check out these interesting facts you probably never knew about amebas.ru

Онлайн-игра, в которой пользователи соревнуются в разведении виртуальных «амёб». Для выращивания амеб используется клиентская программа Amebas, в которой виртуальные существа в ходе искусственной эвол...

Visit amebas.ru

Key Findings

We analyzed Amebas.ru page load time and found that the first response time was 978 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

amebas.ru performance score

0

Network Requests Diagram

amebas.ru

978 ms

all.css

782 ms

jquery.min.js

205 ms

514 ms

jquery.cookie.js

367 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 43% of them (36 requests) were addressed to the original Amebas.ru, 7% (6 requests) were made to My1.imgsmail.ru and 5% (4 requests) were made to Connect.mail.ru. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Amebas.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 434.3 kB (34%)

Content Size

1.3 MB

After Optimization

859.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amebas.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. 45% of websites need less resources to load. Images take 786.9 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 17.4 kB

  • Original 25.7 kB
  • After minification 24.7 kB
  • After compression 8.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 17.4 kB or 68% of the original size.

Image Optimization

-4%

Potential reduce by 33.6 kB

  • Original 786.9 kB
  • After minification 753.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. Amebas images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 312.2 kB

  • Original 399.5 kB
  • After minification 256.2 kB
  • After compression 87.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 312.2 kB or 78% of the original size.

CSS Optimization

-87%

Potential reduce by 71.2 kB

  • Original 82.0 kB
  • After minification 64.8 kB
  • After compression 10.8 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. Amebas.ru needs all CSS files to be minified and compressed as it can save up to 71.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (37%)

Requests Now

78

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amebas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

amebas.ru

amebas.ru

978 ms

all.css

all.css

782 ms

jquery.min.js

jquery.min.js

205 ms

514 ms

jquery.cookie.js

jquery.cookie.js

367 ms

openapi.js

openapi.js

499 ms

share.js

share.js

356 ms

common.js

common.js

358 ms

loader.js

loader.js

398 ms

loader.js

loader.js

332 ms

loader.js

loader.js

390 ms

bg-html.jpg

bg-html.jpg

147 ms

bg-body.jpg

bg-body.jpg

2160 ms

watch.js

watch.js

0 ms

ameba_site_logo.png

ameba_site_logo.png

437 ms

ico02.png

ico02.png

141 ms

ico04.png

ico04.png

141 ms

ico05.png

ico05.png

296 ms

ico01.png

ico01.png

294 ms

ico03.png

ico03.png

295 ms

ico06.png

ico06.png

418 ms

main_display.png

main_display.png

399 ms

main_dna.png

main_dna.png

417 ms

main_experiment.png

main_experiment.png

527 ms

main_rating.png

main_rating.png

529 ms

all.js

all.js

257 ms

bg-w1.jpg

bg-w1.jpg

570 ms

bg-wrapper.jpg

bg-wrapper.jpg

3780 ms

bg-date.png

bg-date.png

592 ms

bg-nav.png

bg-nav.png

644 ms

bottom.png

bottom.png

644 ms

grstat

grstat

1197 ms

api_min.js

api_min.js

605 ms

news.png

news.png

896 ms

arrow01.png

arrow01.png

698 ms

seporator.png

seporator.png

757 ms

bg-text.png

bg-text.png

758 ms

btn01.png

btn01.png

1223 ms

bg-pass.png

bg-pass.png

1650 ms

bg-main.jpg

bg-main.jpg

1648 ms

bg-blog.png

bg-blog.png

1663 ms

btn04.png

btn04.png

2097 ms

bg-so.png

bg-so.png

1712 ms

widgets.js

widgets.js

238 ms

grstat

grstat

1125 ms

share.php

share.php

371 ms

share_logo.png

share_logo.png

2022 ms

bg-footer-holder.png

bg-footer-holder.png

1767 ms

m.png

m.png

1932 ms

bullet01.gif

bullet01.gif

1771 ms

J_vWJUs84wI

J_vWJUs84wI

272 ms

318 ms

xd_arbiter.php

xd_arbiter.php

181 ms

xd_arbiter.php

xd_arbiter.php

351 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

1345 ms

www-embed-player-vfl5foy2V.css

www-embed-player-vfl5foy2V.css

511 ms

www-embed-player.js

www-embed-player.js

958 ms

base.js

base.js

1093 ms

share_friends

share_friends

1618 ms

share_button

share_button

1663 ms

counter

counter

792 ms

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

136 ms

ad_status.js

ad_status.js

134 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

128 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

179 ms

tweet_button.fd774b599f565016d763dd860cb31c79.ru.html

tweet_button.fd774b599f565016d763dd860cb31c79.ru.html

101 ms

jot

jot

172 ms

jquery.js

jquery.js

1049 ms

uber-share.js

uber-share.js

676 ms

20.css

20.css

669 ms

_avatarsmall

_avatarsmall

2494 ms

button_micro.gif

button_micro.gif

497 ms

mm-oval.png

mm-oval.png

194 ms

preloader.gif

preloader.gif

196 ms

grstat

grstat

347 ms

d525461.gif

d525461.gif

1041 ms

code.js

code.js

171 ms

counter

counter

172 ms

tracker

tracker

167 ms

xd_arbiter.php

xd_arbiter.php

57 ms

like.php

like.php

119 ms

OZhivdPHVp_.js

OZhivdPHVp_.js

229 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

240 ms

SEO Factors

amebas.ru SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amebas.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 Amebas.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.

Social Sharing Optimization

amebas.ru

Open Graph description is not detected on the main page of Amebas. 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: