10.7 sec in total
1.3 sec
8.8 sec
604 ms
Welcome to funnysharky.ru homepage info - get ready to check Funnysharky best content for Russia right away, or after learning these important things about funnysharky.ru
Интернет Магазин. Надувные и каркасные бассейны.
Visit funnysharky.ruWe analyzed Funnysharky.ru page load time and found that the first response time was 1.3 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
funnysharky.ru performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value1.2 s
100/100
25%
Value1.0 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.0 s
100/100
10%
1348 ms
287 ms
1868 ms
704 ms
705 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 69% of them (25 requests) were addressed to the original Funnysharky.ru, 19% (7 requests) were made to Api-maps.yandex.ru and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Funnysharky.ru.
Page size can be reduced by 309.9 kB (32%)
969.5 kB
659.6 kB
In fact, the total size of Funnysharky.ru main page is 969.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. 20% of websites need less resources to load. Images take 541.9 kB which makes up the majority of the site volume.
Potential reduce by 90.7 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 90.7 kB or 60% of the original size.
Potential reduce by 21.0 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. Funnysharky images are well optimized though.
Potential reduce by 142.6 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 142.6 kB or 67% of the original size.
Potential reduce by 55.7 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. Funnysharky.ru needs all CSS files to be minified and compressed as it can save up to 55.7 kB or 88% of the original size.
Number of requests can be reduced by 16 (55%)
29
13
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funnysharky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
funnysharky.ru
1348 ms
287 ms
k2.css
1868 ms
colorbox.css
704 ms
general.css
705 ms
mootools-core.js
1513 ms
core.js
867 ms
jquery.min.js
30 ms
k2.js
532 ms
caption.js
730 ms
jquery.min.js
2591 ms
jquery.colorbox-min.js
1011 ms
css
60 ms
788 ms
combine.xml
987 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
169 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
223 ms
4965b66fe115b2f2ed500ece66514d86.cur
396 ms
77492cf358d8b12629399322926c93f2.cur
599 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
300 ms
body_bg.jpg
161 ms
header_bg.jpg
3775 ms
logo.png
335 ms
skypes.png
155 ms
icon_mailto.gif
158 ms
menu_bg.png
163 ms
cart.png
326 ms
menu_line.png
343 ms
menu_marker.png
328 ms
block_header_bg.gif
813 ms
christmarket.png
1493 ms
funnysharky.png
514 ms
footer_photo.png
5078 ms
footer_bg.png
2128 ms
watch.js
73 ms
overlay.png
559 ms
funnysharky.ru accessibility score
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
Document doesn't have a <title> element
funnysharky.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
funnysharky.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funnysharky.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), while the claimed language is Russian. Our system also found out that Funnysharky.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.
funnysharky.ru
Open Graph description is not detected on the main page of Funnysharky. 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: