10.7 sec in total
1.6 sec
8.9 sec
257 ms
Welcome to otogar.com homepage info - get ready to check Otogar best content for Turkey right away, or after learning these important things about otogar.com
Otobüs bileti Otogar.com'da! Firmaları, seferleri ve en ucuz otobüs biletini sorgula, bul ve satın al.Metro, Pamukkale, Nilüfer Turizm, Ulusoy +180 firma.
Visit otogar.comWe analyzed Otogar.com page load time and found that the first response time was 1.6 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
otogar.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value7.0 s
6/100
25%
Value6.4 s
40/100
10%
Value240 ms
85/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
1553 ms
977 ms
713 ms
446 ms
739 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 75% of them (46 requests) were addressed to the original Otogar.com, 5% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Otogar.com.
Page size can be reduced by 1.1 MB (35%)
3.0 MB
2.0 MB
In fact, the total size of Otogar.com main page is 3.0 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. 40% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 71.5 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 71.5 kB or 78% of the original size.
Potential reduce by 185.8 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. Otogar images are well optimized though.
Potential reduce by 419.3 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 419.3 kB or 75% of the original size.
Potential reduce by 379.2 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. Otogar.com needs all CSS files to be minified and compressed as it can save up to 379.2 kB or 88% of the original size.
Number of requests can be reduced by 33 (60%)
55
22
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otogar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
otogar.com
1553 ms
bootstrap.css
977 ms
otogar-v2.css
713 ms
chosen.css
446 ms
forms.css
739 ms
responsive.css
472 ms
wrap-ribbon-light.css
1369 ms
fa.css
1058 ms
jquery-2.1.1.min.js
1362 ms
bootstrap.js
1598 ms
bootstrap-notify.js
1202 ms
chosen.jquery.js
1273 ms
jquery.validate.js
1454 ms
additional-methods.min.js
1398 ms
jquery-ui-1.9.2.custom.css
1557 ms
jquery-ui-1.9.2.custom.js
2143 ms
datepicker-tr.js
1595 ms
datepicker-de.js
1734 ms
datepicker-ru.js
1875 ms
datepicker-en-GB.js
1910 ms
custom.js
1981 ms
otogar_logo.png
792 ms
turkey.png
988 ms
united-kingdom.png
1138 ms
germany.png
1135 ms
russia.png
1198 ms
main-top-bg.jpg
2540 ms
location.png
1363 ms
calendar.png
1384 ms
Otogar.com.tr_iPhone6app.png
2591 ms
Otogar.com.tr_Android_app.png
2724 ms
app-store.png
1648 ms
googleplay.png
1842 ms
istanbul.png
2302 ms
ankara.png
2592 ms
izmir.png
2826 ms
antalya.png
3376 ms
whyweare.png
2975 ms
otogar-safe.png
3010 ms
comodo-ssl.png
3054 ms
creditcards.png
3190 ms
counter.js
26 ms
SohoGothicPro-Medium.otf
3863 ms
SohoGothicPro-Regular.otf
3916 ms
fontawesome-webfont.woff
4053 ms
t.php
384 ms
analytics.js
44 ms
atrk.js
103 ms
sdk.js
148 ms
collect
29 ms
collect
86 ms
atrk.gif
77 ms
ga-audiences
41 ms
127 ms
xd_arbiter.php
156 ms
like.php
59 ms
vpc6VNjRPXV.js
148 ms
LVx-xkvaJ0b.png
159 ms
www.otogar.com
2099 ms
www.otogar.com
2053 ms
collect
6 ms
otogar.com 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
Links do not have a discernible name
otogar.com 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
otogar.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
TR
TR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otogar.com can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it matches the claimed language. Our system also found out that Otogar.com 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.
otogar.com
Open Graph description is not detected on the main page of Otogar. 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: