8.2 sec in total
1.4 sec
6.5 sec
261 ms
Visit funtastik.by now to see the best up-to-date Funtastik content for Belarus and also check out these interesting facts you probably never knew about funtastik.by
Сеть магазинов детских игрушек FUNtastik - широкий выбор игрушек на любой вкус
Visit funtastik.byWe analyzed Funtastik.by page load time and found that the first response time was 1.4 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
funtastik.by performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value18.1 s
0/100
25%
Value21.1 s
0/100
10%
Value27,510 ms
0/100
30%
Value0
100/100
15%
Value42.4 s
0/100
10%
1407 ms
1494 ms
395 ms
399 ms
1001 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 77% of them (66 requests) were addressed to the original Funtastik.by, 6% (5 requests) were made to Mc.yandex.ru and 5% (4 requests) were made to W.uptolike.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Funtastik.by.
Page size can be reduced by 1.0 MB (34%)
3.1 MB
2.0 MB
In fact, the total size of Funtastik.by main page is 3.1 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 65.8 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 65.8 kB or 78% of the original size.
Potential reduce by 137.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. Funtastik images are well optimized though.
Potential reduce by 683.5 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 683.5 kB or 76% of the original size.
Potential reduce by 141.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. Funtastik.by needs all CSS files to be minified and compressed as it can save up to 141.0 kB or 87% of the original size.
Number of requests can be reduced by 20 (25%)
79
59
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funtastik. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
funtastik.by
1407 ms
www.funtastik.by
1494 ms
kernel_main0.css
395 ms
template_e748727d402d9761db89a2a5daa7ca950.css
399 ms
kernel_main.js
1001 ms
template_92d3c17b58700ca27bb1ae2ccbf82c3f.js
404 ms
jquery-1.9.1.js
599 ms
hoverIntent.js
406 ms
main.js
592 ms
jcarousel.basic.css
594 ms
jquery.jcarousel.min.js
595 ms
zp.js
860 ms
ba.js
168 ms
menu-bot.png
199 ms
logo2.png
397 ms
korzina0.png
202 ms
velcom.png
206 ms
mts.png
202 ms
poisk.png
204 ms
menu-seporator.png
397 ms
usermenu.png
402 ms
menu_block_bg.png
402 ms
5826a0f98caef01ec1b4a19d3fa096b1.png
402 ms
9238390dd37af272d140e644ba363637.png
598 ms
1f800ac38f60287af99776fba9aef623.png
594 ms
095df73671c4be5d796eac7e51dbc54a.png
799 ms
cc5db0406dbfe6057622734869a3ad2c.png
600 ms
84268dbfeef0c82d7405927ac756c90f.png
802 ms
6bef2e1489a81d9b62371a800368206d.png
598 ms
7cfbbb00b6aa67c264ee8e2d3cfb9907.png
800 ms
c0863202108980289ec694ddd63c8d9d.png
996 ms
bd95610316d30b55c0f51903e56a790e.png
800 ms
f3442377c0194cd0f584c8be0b2cf32c.png
804 ms
9140fd2d05dadda589e66a208e85e9a6.png
990 ms
1724208844a4e65ec81a5177fa1e6706.png
990 ms
4e86070e447220478ac5d22f0cd67bf6.png
1190 ms
437816bd0d2e1ae5b39b2b12a12cccc4.png
1192 ms
90ba02b683a6e4909e456ad12a5335cd.png
998 ms
e1d4f8d982fbd6d0ff02a8e5c39ad1aa.png
1187 ms
0b390c2b1fb961dd722c61a6a25ca1d8.png
1187 ms
0dc806af2a9c44c5edb6d199d63ab603.jpg
1987 ms
bacaecd81f12cf19a79666ad0c4e50e2.jpg
1792 ms
44337339faa45cf512b9991d594620bc.jpg
2176 ms
de6fb1530026f49cee2c93853df44830.jpg
2177 ms
0da8b8717bdb7f02fac961b94a4bd461.jpg
2179 ms
6aad4ace296670201916f945e6017fb8.jpg
1389 ms
54552c40299281ba79f7b076d3cb55dd.jpeg
1785 ms
32b5037a12007e962fdf8a89b5af5852.jpg
2182 ms
5bf677b9b09595330bd3d117b93ce1a3.jpg
1982 ms
watch.js
180 ms
acode.js
292 ms
ga.js
36 ms
impression.html
308 ms
sync
264 ms
extra.js
317 ms
__utm.gif
11 ms
bx_stat
215 ms
2df843069df333e5bb9624c1c2b79b70.jpg
1993 ms
5969bec923439839d84f59905d1f5348.png
1997 ms
video3.gif
2179 ms
fe405854ee696b61c061dd72923bf754.jpg
2178 ms
17d170ce42fb8781cd8f6b04fc9a46df.JPG
2179 ms
watch.js
551 ms
pixel
23 ms
383 ms
9140fd2d05dadda589e66a208e85e9a6.png
1992 ms
e1d4f8d982fbd6d0ff02a8e5c39ad1aa.png
1995 ms
pixel
20 ms
bepaid.png
1997 ms
visa.png
2177 ms
visa2.png
2178 ms
match
116 ms
master.png
1988 ms
master2.png
1987 ms
button.png
1992 ms
novinka.png
1997 ms
advert.gif
90 ms
akciya.png
1978 ms
slon-spit.png
1978 ms
personal.png
1978 ms
mobile.png
1979 ms
adlik
190 ms
slon-na-lestnice.png
1983 ms
1
91 ms
21506392
92 ms
support.html
320 ms
funtastik.by 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
Form elements do not have associated labels
Links do not have a discernible name
funtastik.by 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
Page has valid source maps
funtastik.by 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funtastik.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Funtastik.by 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.
funtastik.by
Open Graph description is not detected on the main page of Funtastik. 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: