9.5 sec in total
617 ms
8.7 sec
192 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 617 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yell.ge performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value13.3 s
0/100
25%
Value15.7 s
1/100
10%
Value2,040 ms
8/100
30%
Value0.365
30/100
15%
Value16.9 s
5/100
10%
617 ms
3318 ms
337 ms
504 ms
507 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 96% of them (132 requests) were addressed to the original Yell.ge, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Yell.ge.
Page size can be reduced by 311.3 kB (13%)
2.5 MB
2.1 MB
In fact, the total size of Yell.ge main page is 2.5 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 212.4 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 212.4 kB or 90% of the original size.
Potential reduce by 95.7 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 2.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 215 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 7 (5%)
133
126
The browser has sent 133 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 8 to 1 for JavaScripts and as a result speed up the page load time.
yell.ge
617 ms
www.yell.ge
3318 ms
style_index.css
337 ms
current_keyboard.js
504 ms
script_search.js
507 ms
script_PP.js
510 ms
script_SLD_banners.js
509 ms
script_map_address.js
527 ms
script_DD.js
542 ms
js
33 ms
logo.png
171 ms
lan_sep.gif
171 ms
sityvit.png
178 ms
telefonit.png
175 ms
misamartit.png
182 ms
siaxlovit.png
168 ms
SI_3.png
337 ms
input_1_right.png
339 ms
create_edit.png
340 ms
machvene%20rukaze.png
341 ms
close_2.png
352 ms
login_user_icon.png
362 ms
login_input_email_l.png
504 ms
login_input_pass_l.png
506 ms
login_with_facebook_geo.gif
508 ms
232.jpg
1015 ms
226.jpg
876 ms
432.jpg
541 ms
427.jpg
837 ms
472.jpg
843 ms
66.jpg
845 ms
277.jpg
903 ms
462.jpg
1170 ms
info_banner_icon.png
1011 ms
475.jpg
1181 ms
421.jpg
1225 ms
70.jpg
1264 ms
243.jpg
1349 ms
138.jpg
1182 ms
407.jpg
1504 ms
453.jpg
1519 ms
461.jpg
1521 ms
191.jpg
1401 ms
484.jpg
1444 ms
466.jpg
1517 ms
analytics.js
82 ms
watch.js
40 ms
8cea8925924bf02b8a310439f5427e73307f78fae738.html
1559 ms
collect
12 ms
collect
49 ms
bpg_nino_mtavruli_bold.ttf
1643 ms
bpg_algeti_compact.ttf
1844 ms
71.jpg
1525 ms
76.jpg
1521 ms
205.jpg
1520 ms
228.jpg
1575 ms
89.jpg
1528 ms
268.jpg
1695 ms
232.jpg
1693 ms
185.jpg
1591 ms
250.jpg
1640 ms
460.jpg
1671 ms
455.jpg
1603 ms
345.jpg
1664 ms
72.jpg
1674 ms
249.jpg
1827 ms
104.jpg
1363 ms
284.jpg
1359 ms
467.jpg
1436 ms
224.jpg
1657 ms
160.jpg
1445 ms
444.jpg
1527 ms
239.jpg
1358 ms
316.jpg
1288 ms
219.jpg
1334 ms
359.jpg
1522 ms
117.jpg
1316 ms
376.jpg
1370 ms
163.jpg
1334 ms
226.jpg
1311 ms
430.jpg
1263 ms
274.jpg
1205 ms
267.jpg
1291 ms
179.jpg
1498 ms
440.jpg
1354 ms
299.jpg
1300 ms
457.jpg
1188 ms
399.jpg
1202 ms
231.jpg
1291 ms
204.jpg
1291 ms
334.jpg
1231 ms
357.jpg
1190 ms
364.jpg
1157 ms
479.jpg
1173 ms
474.jpg
1169 ms
90.jpg
1185 ms
333.jpg
1187 ms
360.jpg
1190 ms
165.jpg
1343 ms
94.jpg
1169 ms
112.jpg
1175 ms
370.jpg
1185 ms
209.jpg
1187 ms
437.jpg
1111 ms
463.jpg
1166 ms
152.jpg
1154 ms
481.jpg
1183 ms
469.jpg
1098 ms
346.jpg
1045 ms
350.jpg
1097 ms
foot_logo.png
1152 ms
adsmo.png
1149 ms
addco.png
1088 ms
line_yellow.gif
1043 ms
left.png
1025 ms
center.png
1103 ms
right.png
1147 ms
input_0_left.png
1153 ms
input_0_center.png
1082 ms
input_0_right.png
1021 ms
mag_index.png
1022 ms
pr_restaurants.png
1112 ms
pr_hotels.png
1130 ms
pr_tourism.png
1055 ms
pr_taxi.png
1044 ms
pr_medicine.png
1022 ms
pr_pharmacies.png
1022 ms
login_form_display_icon_c.png
1121 ms
slide_bg.jpg
1106 ms
catecories_arrow.png
1055 ms
slide_arrow_l_1.png
1045 ms
slide_arrow_r_1.png
1020 ms
info_banner_sep.png
1023 ms
arrows_1.png
1131 ms
info_banner_icon_15x15.png
1021 ms
face_foot.png
1037 ms
bauweg_geo.png
1015 ms
yell.ge 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
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: