4.3 sec in total
490 ms
2.8 sec
1 sec
Click here to check amazing Fanfishka content for Russia. Otherwise, check out these important facts you probably never knew about fanfishka.ru
Сайт посвящен прекрасному миру аквариумных рыбок и акваскейпу
Visit fanfishka.ruWe analyzed Fanfishka.ru page load time and found that the first response time was 490 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fanfishka.ru performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value11.9 s
0/100
25%
Value6.3 s
41/100
10%
Value330 ms
76/100
30%
Value0.45
20/100
15%
Value9.5 s
30/100
10%
490 ms
459 ms
554 ms
338 ms
339 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 48% of them (58 requests) were addressed to the original Fanfishka.ru, 10% (12 requests) were made to Vk.com and 5% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fanfishka.ru.
Page size can be reduced by 658.6 kB (23%)
2.9 MB
2.2 MB
In fact, the total size of Fanfishka.ru main page is 2.9 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. 60% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 170.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 170.9 kB or 85% of the original size.
Potential reduce by 31.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. Fanfishka images are well optimized though.
Potential reduce by 373.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 373.9 kB or 62% of the original size.
Potential reduce by 81.9 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. Fanfishka.ru needs all CSS files to be minified and compressed as it can save up to 81.9 kB or 83% of the original size.
Number of requests can be reduced by 52 (44%)
117
65
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanfishka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fanfishka.ru
490 ms
jquery.js
459 ms
jqueryui.js
554 ms
dle_js.js
338 ms
style.css
339 ms
media-queries.css
224 ms
engine.css
341 ms
jquery.bpopup.min.js
335 ms
script.js
447 ms
brand
29 ms
adsbygoogle.js
7 ms
openapi.js
390 ms
brand
64 ms
bg_top.png
604 ms
bg_bottom.png
905 ms
logo.png
174 ms
home_icon.png
172 ms
feedback_icon.png
172 ms
sitemap_icon.png
174 ms
top_menu_bg.png
225 ms
search_bg.png
227 ms
search_btn.png
226 ms
1.png
222 ms
2.png
331 ms
3.png
330 ms
4.png
329 ms
5.png
333 ms
6.png
498 ms
google_custom_search_watermark.gif
78 ms
context.js
231 ms
bg_block.png
490 ms
head_block.png
491 ms
%D0%91%D0%90%D0%9D%D0%9D%D0%95%D0%A0-200_400.jpg
593 ms
BanNav%202.jpg
811 ms
sovmestimost_akvaryb.png
658 ms
akvariumnye_rastenija.png
878 ms
so2_dlja_akvariuma_glavnaja.png
665 ms
vodorosli_v_akvariume.png
847 ms
mutnyj_akvarium.png
872 ms
davinchi.png
810 ms
neony.png
1091 ms
skaljarii.png
902 ms
ca-pub-2023908958884497.js
59 ms
zrt_lookup.html
46 ms
show_ads_impl.js
51 ms
vote_btn.png
919 ms
results_btn.png
954 ms
text_top_bg.png
963 ms
1456493027_02.jpg
972 ms
read_more_bg.png
988 ms
1455880828_azot-broshurar.jpg
1006 ms
1455810512_hemiantus-kuba-glavnaya.jpg
1174 ms
1455809054_cooltext166254989594745.png
1075 ms
1455809097_cooltext166255058666041.png
1083 ms
upload.gif
131 ms
ads
219 ms
widget_community.php
269 ms
code.js
564 ms
hit
256 ms
watch.js
182 ms
1455626718_post-1-0-82774400-1453902496.jpg
992 ms
1455274644_akara-glav.jpg
1007 ms
1455274649_akara-nadpis.png
1059 ms
osd.js
17 ms
1455027828_moh-na-koryage.jpg
1071 ms
ads
199 ms
navigation_bg.png
1027 ms
200_400.gif
1168 ms
purefish01.gif
1180 ms
1439548866_tetralogo.png
1115 ms
context_static_r1065.js
353 ms
question_btn.png
1005 ms
khomoakvarius.jpg
1022 ms
FFVK.png
1031 ms
watch.js
489 ms
Partner%20FF.png
1113 ms
5864399677923014378
58 ms
abg.js
58 ms
m_js_controller.js
76 ms
googlelogo_color_112x36dp.png
136 ms
hit
175 ms
loader_nav19130_3.js
167 ms
lite.css
169 ms
lite.js
517 ms
lang3_0.js
262 ms
widget_community.css
263 ms
xdm.js
276 ms
al_community.js
279 ms
s
65 ms
x_button_blue2.png
72 ms
imgad
19 ms
nessie_icon_thin_arrow_big_white.png
18 ms
footer_line.png
948 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
12 ms
145633
151 ms
counter2
163 ms
counter
157 ms
mnevkusno.ru
270 ms
x90
52 ms
y90
42 ms
my-dreams.info
356 ms
bad-magazin.org
485 ms
advert.gif
84 ms
XtoIeZdpGd8.jpg
386 ms
8P3WyZxGFX4.jpg
257 ms
dNvyr3eRG0g.jpg
256 ms
e_7691d0a4.jpg
387 ms
xmpVDam9Xaw.jpg
385 ms
SpxVlBuCnLc.jpg
401 ms
1SqyJAF8-yo.jpg
251 ms
QwT3JcXg2TM.jpg
397 ms
6DZGsfiPg20.jpg
628 ms
FLjULfjkoaE.jpg
259 ms
rNLDuDPsUrs.jpg
398 ms
TFQ0wHRw1Mc.jpg
399 ms
j0_Vmqo8lYQ.jpg
386 ms
camera_50.png
132 ms
w_logo.png
131 ms
1
86 ms
145633
85 ms
tracker
159 ms
ui
16 ms
fanfishka.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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fanfishka.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fanfishka.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanfishka.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 Fanfishka.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.
fanfishka.ru
Open Graph description is not detected on the main page of Fanfishka. 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: