5.3 sec in total
1.2 sec
3.7 sec
332 ms
Welcome to i-hear.ru homepage info - get ready to check I Hear best content for Russia right away, or after learning these important things about i-hear.ru
Слуховые аппараты Москве - купить по выгодной цене в интернет-магазине «Я Слышу!» Бесплатный подбор и настройка. 2 года гарантии. Батарейки в подарок. Звоните: +7 (495) 642-39-70.
Visit i-hear.ruWe analyzed I-hear.ru page load time and found that the first response time was 1.2 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
i-hear.ru performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value11.4 s
0/100
25%
Value9.0 s
14/100
10%
Value760 ms
38/100
30%
Value0.098
90/100
15%
Value14.1 s
9/100
10%
1237 ms
605 ms
140 ms
412 ms
276 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 89% of them (64 requests) were addressed to the original I-hear.ru, 6% (4 requests) were made to Chaser.ru and 3% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain I-hear.ru.
Page size can be reduced by 397.0 kB (62%)
642.8 kB
245.8 kB
In fact, the total size of I-hear.ru main page is 642.8 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. 35% of websites need less resources to load. Javascripts take 236.5 kB which makes up the majority of the site volume.
Potential reduce by 45.0 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. This page needs HTML code to be minified as it can gain 12.2 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.0 kB or 82% of the original size.
Potential reduce by 32.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. Obviously, I Hear needs image optimization as it can save up to 32.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 172.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 172.6 kB or 73% of the original size.
Potential reduce by 147.1 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. I-hear.ru needs all CSS files to be minified and compressed as it can save up to 147.1 kB or 86% of the original size.
Number of requests can be reduced by 23 (34%)
68
45
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Hear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
i-hear.ru
1237 ms
www.i-hear.ru
605 ms
style.css
140 ms
jquery.1.11.2.min.js
412 ms
feedback.js
276 ms
owl.carousel.min.css
281 ms
owl.theme.default.min.css
279 ms
owl.carousel.js
496 ms
jquery.qtip.min.css
277 ms
jquery.qtip.min.js
544 ms
jquery.common.js
495 ms
jquery.common.forms.js
493 ms
float_menu_bg.jpg
167 ms
bg_header.png
167 ms
bg_header_start.png
168 ms
bg_header_end.jpg
167 ms
metro.jpg
279 ms
man.jpg
242 ms
woman.jpg
281 ms
logo.png
278 ms
callback_bg.png
276 ms
bg_menu.png
280 ms
bg_boxes.png
374 ms
adv_block_bg.jpg
412 ms
adv_block_lr.jpg
419 ms
bg_adv_box_1.jpg
413 ms
bul_1.png
420 ms
title_bg.png
423 ms
product_box_top.png
537 ms
bg_hot.png
547 ms
g1_7718.jpg
547 ms
bg_product_img.png
555 ms
odd_start.png
556 ms
odd_end.png
559 ms
g2_4598.jpg
672 ms
g3_9901.jpg
682 ms
g4_6823.jpg
679 ms
g5_9783.jpg
710 ms
g6_1407.jpg
688 ms
g7_3822.jpg
696 ms
g8_5069.jpg
806 ms
g9_8018.jpg
814 ms
g10_6557.jpg
814 ms
hit
281 ms
g11_6478.jpg
800 ms
g12_4891.jpg
800 ms
g13_1424.jpg
804 ms
watch.js
1 ms
g14_7559.jpg
898 ms
chaser.js
847 ms
g15_7375.jpg
797 ms
g16_1284.jpg
795 ms
g17_5771.jpg
820 ms
g18_8039.jpg
822 ms
pagenav_start.png
825 ms
pagenav_end.png
844 ms
brand_1.jpg
819 ms
brand_2.jpg
819 ms
brand_3.jpg
843 ms
brand_4.jpg
846 ms
brand_5.jpg
849 ms
hit
150 ms
brand_6.jpg
849 ms
f_icon_1.jpg
818 ms
f_icon_4.jpg
817 ms
f_icon_2.jpg
847 ms
f_icon_3.jpg
847 ms
feedback_l.png
843 ms
widget.css
311 ms
action.php
355 ms
css
25 ms
ie.css
155 ms
i-hear.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
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
i-hear.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
i-hear.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-hear.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 I-hear.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
i-hear.ru
Open Graph description is not detected on the main page of I Hear. 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: