Tools & Wizards About Us
otogar.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

otogar.com

Otobüs Bileti - Otogar.com

Page Load Speed

6.3 sec in total

First Response

66 ms

Resources Loaded

5.7 sec

Page Rendered

563 ms

otogar.com screenshot

About Website

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.com

Key Findings

We analyzed Otogar.com page load time and found that the first response time was 66 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

otogar.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

otogar.com

66 ms

otogar.com

441 ms

www.otogar.com

1841 ms

master.css

22 ms

yoda.css

34 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 86% of them (44 requests) were addressed to the original Otogar.com, 6% (3 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Otogar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 256.9 kB (16%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Otogar.com main page is 1.6 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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 231.3 kB

  • Original 285.4 kB
  • After minification 285.4 kB
  • After compression 54.1 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 231.3 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 25.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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.

JavaScript Optimization

-0%

Potential reduce by 214 B

  • Original 130.4 kB
  • After minification 130.4 kB
  • After compression 130.2 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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 29.8 kB
  • After minification 29.8 kB
  • After compression 29.8 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (49%)

Requests Now

43

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 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 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

otogar.com

otogar.com

66 ms

otogar.com

otogar.com

441 ms

www.otogar.com

www.otogar.com

1841 ms

master.css

master.css

22 ms

yoda.css

yoda.css

34 ms

quorra.js

quorra.js

33 ms

jquery.validate.min.js

jquery.validate.min.js

32 ms

additional-methods.min.js

additional-methods.min.js

26 ms

jquery-ui-1.9.2.custom.min.css

jquery-ui-1.9.2.custom.min.css

970 ms

jquery-ui-1.9.2.custom.min.js

jquery-ui-1.9.2.custom.min.js

38 ms

datepicker-tr.js

datepicker-tr.js

43 ms

datepicker-de.js

datepicker-de.js

42 ms

datepicker-ru.js

datepicker-ru.js

44 ms

datepicker-en-GB.js

datepicker-en-GB.js

50 ms

custom.js

custom.js

52 ms

turkey.png

turkey.png

472 ms

united-kingdom.png

united-kingdom.png

494 ms

germany.png

germany.png

493 ms

russia.png

russia.png

494 ms

otogarcomb.png

otogarcomb.png

903 ms

css

css

46 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

26 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1688 ms

istanbul.png

istanbul.png

693 ms

ankara.png

ankara.png

487 ms

izmir.png

izmir.png

489 ms

antalya.png

antalya.png

539 ms

appstore.png

appstore.png

597 ms

googleplay.png

googleplay.png

1045 ms

comodo-ssl.png

comodo-ssl.png

1057 ms

js

js

72 ms

counter.js

counter.js

45 ms

ccs.png

ccs.png

952 ms

ticket-tr-icon.png

ticket-tr-icon.png

1042 ms

css_sprites.png

css_sprites.png

734 ms

bgimages.jpg

bgimages.jpg

913 ms

location.png

location.png

999 ms

calendar.png

calendar.png

988 ms

dot-left.png

dot-left.png

1008 ms

ios_app.png

ios_app.png

1088 ms

android_app.png

android_app.png

1166 ms

whyweare.png

whyweare.png

1356 ms

otogar-safe.png

otogar-safe.png

2471 ms

dot-center.png

dot-center.png

2429 ms

siluet.png

siluet.png

1439 ms

footerLogo.png

footerLogo.png

1524 ms

t.php

t.php

104 ms

www.otogar.com

www.otogar.com

2120 ms

main.js

main.js

193 ms

Accessibility Review

otogar.com accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

otogar.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

otogar.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    TR

  • Encoding

    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.

Social Sharing Optimization

otogar.com

Open Graph data is detected on the main page of Otogar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: