4.5 sec in total
854 ms
2.9 sec
797 ms
Click here to check amazing Funimg content for Russia. Otherwise, check out these important facts you probably never knew about funimg.ru
Visit funimg.ruWe analyzed Funimg.ru page load time and found that the first response time was 854 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
funimg.ru performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value8.1 s
2/100
25%
Value8.7 s
16/100
10%
Value1,830 ms
9/100
30%
Value0.222
56/100
15%
Value20.3 s
2/100
10%
854 ms
256 ms
278 ms
387 ms
170 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 38% of them (40 requests) were addressed to the original Funimg.ru, 19% (20 requests) were made to Vk.com and 11% (12 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Funimg.ru.
Page size can be reduced by 696.9 kB (25%)
2.8 MB
2.1 MB
In fact, the total size of Funimg.ru main page is 2.8 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 77.1 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 77.1 kB or 86% of the original size.
Potential reduce by 285.9 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, Funimg needs image optimization as it can save up to 285.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 226.0 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 226.0 kB or 73% of the original size.
Potential reduce by 108.0 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. Funimg.ru needs all CSS files to be minified and compressed as it can save up to 108.0 kB or 84% of the original size.
Number of requests can be reduced by 28 (28%)
100
72
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funimg. 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 4 to 1 for CSS and as a result speed up the page load time.
funimg.ru
854 ms
bootstrap.css
256 ms
style.css
278 ms
openapi.js
387 ms
watch.js
170 ms
watch.js
461 ms
plusone.js
76 ms
twitter.png
140 ms
logonew.jpg
328 ms
13329.png
516 ms
13328.png
996 ms
13327.png
632 ms
13326.png
838 ms
13325.png
973 ms
13324.png
926 ms
13323.png
1145 ms
13322.jpeg
878 ms
13321.png
1142 ms
13320.png
1006 ms
thumb_220x0_3210.jpeg
1057 ms
thumb_220x0_3757.png
1142 ms
thumb_220x0_3233.jpeg
1141 ms
thumb_220x0_2264.jpeg
1142 ms
thumb_220x0_3829.jpeg
1189 ms
thumb_220x0_3211.jpeg
1222 ms
thumb_220x0_2265.jpeg
1230 ms
thumb_220x0_11057.jpeg
1241 ms
thumb_220x0_11191.png
1251 ms
thumb_220x0_2566.jpeg
1266 ms
thumb_220x0_2273.jpeg
1318 ms
thumb_220x0_2269.jpeg
1354 ms
thumb_220x0_2271.jpeg
1358 ms
thumb_220x0_11228.png
1365 ms
thumb_220x0_3755.jpeg
1372 ms
thumb_220x0_2266.jpeg
1391 ms
thumb_220x0_11030.jpeg
1449 ms
thumb_220x0_3213.jpeg
1481 ms
thumb_220x0_2268.jpeg
1486 ms
thumb_220x0_11226.jpeg
1490 ms
thumb_220x0_2272.jpeg
1493 ms
thumb_220x0_3756.png
1521 ms
thumb_220x0_11094.jpeg
1580 ms
thumb_220x0_11041.png
1607 ms
all.js
24 ms
widgets.js
86 ms
upload.gif
287 ms
widget_like.php
405 ms
widget_like.php
530 ms
116 ms
widget_like.php
519 ms
xd_arbiter.php
16 ms
xd_arbiter.php
42 ms
cb=gapi.loaded_0
16 ms
widget_like.php
508 ms
widget_like.php
500 ms
widget_like.php
496 ms
widget_like.php
500 ms
widget_like.php
643 ms
widget_like.php
630 ms
widget_like.php
619 ms
thumb_220x0_11208.jpeg
1483 ms
widget_like.php
611 ms
aci.js
202 ms
hit
280 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
154 ms
cb=gapi.loaded_1
29 ms
fastbutton
73 ms
advert.gif
119 ms
xd_arbiter.php
40 ms
postmessageRelay
76 ms
1
181 ms
131 ms
227 ms
cb=gapi.loaded_0
30 ms
cb=gapi.loaded_1
30 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
52 ms
like.php
126 ms
3193398744-postmessagerelay.js
33 ms
rpc:shindig_random.js
36 ms
hit
160 ms
like.php
190 ms
loader_nav19188_3.js
290 ms
lite.css
294 ms
lite.js
639 ms
lang3_0.js
400 ms
widgets.css
417 ms
xdm.js
419 ms
al_like.js
418 ms
like.php
159 ms
cb=gapi.loaded_0
9 ms
like.php
160 ms
like.php
168 ms
like.php
148 ms
like.php
218 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ru.html
86 ms
like.php
229 ms
like.php
247 ms
like.php
208 ms
like.php
213 ms
9S-PuPSi5xI.js
89 ms
LVx-xkvaJ0b.png
81 ms
248 ms
match
192 ms
jot.html
28 ms
like_widget.png
124 ms
funimg.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
funimg.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
funimg.ru SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funimg.ru 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Funimg.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.
funimg.ru
Open Graph description is not detected on the main page of Funimg. 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: