7.3 sec in total
595 ms
6.5 sec
209 ms
Click here to check amazing Yell content for Georgia. Otherwise, check out these important facts you probably never knew about yell.ge
თბილისის და საქართველოს სხვა ქალაქების ორგანიზაციების ბიზნეს საინფორმაციო ცნობარი – ტელეფონები, მისამართები და სხვა ინფორმაცია. თბილისის რუკა.
Visit yell.geWe analyzed Yell.ge page load time and found that the first response time was 595 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
yell.ge performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value13.2 s
0/100
25%
Value11.7 s
4/100
10%
Value2,320 ms
5/100
30%
Value0.365
29/100
15%
Value18.0 s
3/100
10%
595 ms
1444 ms
606 ms
451 ms
453 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 91% of them (124 requests) were addressed to the original Yell.ge, 2% (3 requests) were made to Cdnjs.cloudflare.com and 1% (2 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Yell.ge.
Page size can be reduced by 586.9 kB (20%)
2.9 MB
2.3 MB
In fact, the total size of Yell.ge 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 407.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 407.8 kB or 88% of the original size.
Potential reduce by 139.2 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 39.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 39.1 kB or 12% of the original size.
Potential reduce by 845 B
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.ge has all CSS files already compressed.
Number of requests can be reduced by 24 (18%)
131
107
The browser has sent 131 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 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
yell.ge
595 ms
www.yell.ge
1444 ms
bootstrap.min.css
606 ms
slick.css
451 ms
slick-theme.css
453 ms
style_sidebar.css
459 ms
styles_2020.css
460 ms
style_index.css
466 ms
current_keyboard.js
599 ms
script_search.js
621 ms
script_PP.js
622 ms
script_SLD_banners.js
623 ms
script_map_address.js
623 ms
jquery.min.js
37 ms
popper.min.js
43 ms
bootstrap.min.js
900 ms
slick.js
905 ms
solid.js
50 ms
fontawesome.js
59 ms
mtLocationHash.js
757 ms
script_DD.js
762 ms
js
87 ms
jquery.mCustomScrollbar.min.css
54 ms
jquery.mCustomScrollbar.concat.min.js
56 ms
script_SR.js
762 ms
css
33 ms
close_2.png
263 ms
login_user_icon.png
264 ms
login_input_email_l.png
262 ms
login_input_pass_l.png
264 ms
login_with_facebook_geo.gif
261 ms
logo.png
263 ms
lan_sep.gif
363 ms
search_company.png
363 ms
search_tel.png
364 ms
search_address.png
360 ms
SI_3.png
361 ms
input_1_right.png
365 ms
create_edit.png
654 ms
428.jpg
995 ms
424.gif
2596 ms
420.jpg
998 ms
pr_restaurants.png
654 ms
pr_taxi.png
655 ms
pr_tourism.png
656 ms
pr_hotels.png
657 ms
pr_medicine.png
657 ms
pr_pharmacies.png
796 ms
574.jpg
996 ms
skype-logo.png
797 ms
fb.png
995 ms
747.jpg
1096 ms
707.jpg
1068 ms
543.jpg
1218 ms
794.jpg
1087 ms
662.jpg
1089 ms
365.jpg
1217 ms
735.jpg
1390 ms
627.png
1240 ms
774.jpg
1457 ms
350.jpg
1514 ms
analytics.js
43 ms
info_banner_icon.png
1362 ms
collect
21 ms
collect
242 ms
js
239 ms
bpg_nino_mtavruli_bold.woff
1137 ms
bpg_algeti_compact.ttf
1710 ms
496.jpg
1285 ms
593.jpg
1290 ms
683.jpg
1450 ms
568.jpg
1391 ms
104.jpg
1339 ms
750.jpg
1344 ms
294.jpg
1456 ms
640.jpg
1655 ms
357.jpg
1494 ms
637.jpg
1401 ms
696.jpg
1314 ms
407.jpg
1364 ms
644.jpg
1463 ms
whatsapp.png
1464 ms
205.jpg
1499 ms
243.jpg
1369 ms
461.jpg
1559 ms
795.jpg
1380 ms
slick.woff
1273 ms
204.jpg
1359 ms
761.jpg
1360 ms
70.jpg
1560 ms
553.jpg
1348 ms
481.jpg
1372 ms
470.jpg
1379 ms
732.jpg
1384 ms
700.jpg
1499 ms
630.jpg
1395 ms
185.jpg
1382 ms
670.jpg
1267 ms
681.jpg
1323 ms
437.jpg
1288 ms
801.jpg
1269 ms
697.jpg
1413 ms
71.jpg
1244 ms
463.jpg
1316 ms
636.jpg
1199 ms
790.jpg
1200 ms
628.jpg
1217 ms
633.jpg
1386 ms
775.jpg
1199 ms
649.jpg
1160 ms
758.jpg
1083 ms
450.jpg
1060 ms
773.jpg
1068 ms
333.jpg
1115 ms
706.jpg
1261 ms
699.jpg
1086 ms
704.jpg
1107 ms
612.jpg
1082 ms
737.jpg
1088 ms
777.jpg
1051 ms
641.jpg
1003 ms
409.jpg
1025 ms
770.jpg
1037 ms
364.jpg
1050 ms
594.jpg
1048 ms
603.jpg
1007 ms
764.jpg
1043 ms
800.jpg
1050 ms
foot_logo.png
979 ms
info_banner_icon_15x15.png
969 ms
mag_index.png
1002 ms
login_form_display_icon_c.png
992 ms
catecories_arrow.png
1121 ms
info_banner_sep.png
1041 ms
face_foot.png
1040 ms
ajax-loader.gif
1010 ms
yell.ge accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
yell.ge 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
yell.ge 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
Tap targets are not sized appropriately
KA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yell.ge can be misinterpreted by Google and other search engines. Our service has detected that Georgian 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 Yell.ge 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.ge
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: