4.6 sec in total
347 ms
3.7 sec
604 ms
Visit yell.ru now to see the best up-to-date Yell content for Russia and also check out these interesting facts you probably never knew about yell.ru
Рейтинг лучших компаний в Москве. Адреса и телефоны, видео и акции в справочнике Yell.
Visit yell.ruWe analyzed Yell.ru page load time and found that the first response time was 347 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
yell.ru performance score
name
value
score
weighting
Value3.2 s
45/100
10%
Value7.4 s
4/100
25%
Value5.6 s
53/100
10%
Value1,480 ms
14/100
30%
Value0
100/100
15%
Value8.3 s
40/100
10%
347 ms
449 ms
33 ms
144 ms
26 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 17% of them (9 requests) were addressed to the original Yell.ru, 19% (10 requests) were made to Fonts.gstatic.com and 15% (8 requests) were made to Static.ysites.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Static.ysites.ru.
Page size can be reduced by 1.1 MB (47%)
2.4 MB
1.3 MB
In fact, the total size of Yell.ru main page is 2.4 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. 65% of websites need less resources to load. HTML takes 944.9 kB which makes up the majority of the site volume.
Potential reduce by 716.2 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 716.2 kB or 76% of the original size.
Potential reduce by 26.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. Yell images are well optimized though.
Potential reduce by 181.1 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 181.1 kB or 67% of the original size.
Potential reduce by 183.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. Yell.ru needs all CSS files to be minified and compressed as it can save up to 183.1 kB or 84% of the original size.
Number of requests can be reduced by 20 (54%)
37
17
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yell. 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.
yell.ru
347 ms
449 ms
css
33 ms
1a1638c0dffb1f61a421c0da97e79bff.css
144 ms
angular.min.js
26 ms
jquery.min.js
24 ms
underscore-min.js
13 ms
4d7c9e9240a4ffcbba311f4a531e6f3c.js
268 ms
jquery.easing.min.js
9 ms
angular-cookies.min.js
13 ms
ng-tags-input.min.js
10 ms
267 ms
4a0dc088576d7f69e448667a4efddef2.js
468 ms
logo
314 ms
1px.gif
203 ms
803 ms
gtm.js
45 ms
r_0_38_254u80x74mydeabb_1442423300.jpg
1189 ms
yell-red-trans.svg
197 ms
r_1162947_nar6urloagcljrg7lvqc.jpg
1051 ms
r_597818_9r1ijzleqrdpa79p5qst.jpg
620 ms
r_942529_e2sqcmjr2bgiua1ael8d.jpg
513 ms
r_349044_hk7dsxnnj0ouuk5u7cd0.jpg
1046 ms
r_597137_7mrr8ujfchxae5k9efnq.jpg
1046 ms
r_831876_dhkprqqjj6int2ioke3z.jpg
1415 ms
r_831876_tnr7epcry8vkmapa9s2i.jpg
1273 ms
oeEVQYYBjVpg-nn8NItjTw.ttf
52 ms
ZLqKeelYbATG60EpZBSDy6CWcynf_cDxXwCLxiixG1c.ttf
52 ms
0eC6fl06luXEYWpBSJvXCKCWcynf_cDxXwCLxiixG1c.ttf
55 ms
77FXFjRbGzN4aCrSFhlh3qCWcynf_cDxXwCLxiixG1c.ttf
52 ms
s7gftie1JANC-QmDJvMWZqCWcynf_cDxXwCLxiixG1c.ttf
53 ms
9VbgU8TpQQiT0xzIj6bUWvesZW2xOQ-xsNqO47m55DA.ttf
55 ms
OLffGBTaF0XFOW1gnuHF0VwIJl2YiaXHM0xUx_ugXFg.ttf
55 ms
7m8l7TlFO-S3VkhHuR0at1wIJl2YiaXHM0xUx_ugXFg.ttf
51 ms
t6Nd4cfPRhZP44Q5QAjcC1wIJl2YiaXHM0xUx_ugXFg.ttf
107 ms
bmC0pGMXrhphrZJmniIZpVwIJl2YiaXHM0xUx_ugXFg.ttf
111 ms
context.js
263 ms
dc.js
67 ms
hit;newyell_2010
298 ms
__utm.gif
39 ms
context_static_r1084.js
349 ms
hit;newyell_2010
134 ms
131228
370 ms
watch.js
3 ms
tcounter.js
297 ms
watch.js
247 ms
sprite.symbol.svg
800 ms
169 ms
y150
172 ms
y150
244 ms
y150
328 ms
256207655
968 ms
__utm.gif
13 ms
yell.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
yell.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
yell.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
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 Yell.ru 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 Yell.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.
yell.ru
Open Graph description is not detected on the main page of Yell. 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: