Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

geetabus.in

Online Bus Ticket Booking, Route, Time Schedule | Ashapura Travels

Page Load Speed

13.4 sec in total

First Response

2.2 sec

Resources Loaded

11.1 sec

Page Rendered

136 ms

geetabus.in screenshot

About Website

Visit geetabus.in now to see the best up-to-date Geeta Bus content and also check out these interesting facts you probably never knew about geetabus.in

Online Bus Ticket Booking at ashapurabus.in for Rajkot To Una, Rajkot To Kodinar . Get Route Time and Fare, Night Routes on our website.

Visit geetabus.in

Key Findings

We analyzed Geetabus.in page load time and found that the first response time was 2.2 sec and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

geetabus.in performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,290 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.1

89/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

geetabus.in

2216 ms

ashapurabus.in

423 ms

ashapurabus.in

1636 ms

style.css

449 ms

StyleComman.css

664 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Geetabus.in, 95% (114 requests) were made to Ashapurabus.in and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Ashapurabus.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 150.2 kB (7%)

Content Size

2.0 MB

After Optimization

1.9 MB

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

HTML Optimization

-78%

Potential reduce by 114.8 kB

  • Original 146.6 kB
  • After minification 103.6 kB
  • After compression 31.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. This page needs HTML code to be minified as it can gain 43.0 kB, which is 29% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 114.8 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 4.0 kB

  • Original 1.6 MB
  • After minification 1.6 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. Geeta Bus images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 24.2 kB

  • Original 239.1 kB
  • After minification 239.1 kB
  • After compression 214.8 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

-15%

Potential reduce by 7.2 kB

  • Original 47.9 kB
  • After minification 47.9 kB
  • After compression 40.7 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. Geetabus.in needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 15% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

37

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geeta Bus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

geetabus.in accessibility score

58

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

geetabus.in best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

geetabus.in SEO score

58

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geetabus.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Geetabus.in 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

Open Graph description is not detected on the main page of Geeta Bus. 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: