13.4 sec in total
2.2 sec
11.1 sec
136 ms
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.inWe 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.
geetabus.in performance score
name
value
score
weighting
Value11.3 s
0/100
10%
Value11.6 s
0/100
25%
Value21.1 s
0/100
10%
Value2,290 ms
5/100
30%
Value0.1
89/100
15%
Value16.6 s
5/100
10%
2216 ms
423 ms
1636 ms
449 ms
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 size can be reduced by 150.2 kB (7%)
2.0 MB
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.
Potential reduce by 114.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.
Potential reduce by 4.0 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. Geeta Bus images are well optimized though.
Potential reduce by 24.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.
Potential reduce by 7.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. 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.
Number of requests can be reduced by 36 (49%)
73
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.
geetabus.in
2216 ms
ashapurabus.in
423 ms
ashapurabus.in
1636 ms
style.css
449 ms
StyleComman.css
664 ms
animate.css
838 ms
font-awesome.css
841 ms
jquery-1.12.min.js
877 ms
jquery.carouFredSel-5.5.0-packed.js
1064 ms
functions.js
874 ms
bootstrap.min.css
884 ms
bootstrap.js
1223 ms
bootstrap-dialog.min.js
1034 ms
bootstrap-datetimepicker.min.css
1078 ms
bootstrap-datetimepicker.min.js
1086 ms
bootstrap-select.min.css
1086 ms
bootstrap-select.min.js
1445 ms
jquery.validation.css
1259 ms
jSonHandlerScript.js
1278 ms
WebResource.axd
1108 ms
ScriptResource.axd
1096 ms
ScriptResource.axd
1213 ms
ScriptResource.axd
1260 ms
ScriptResource.axd
1283 ms
ScriptResource.axd
1293 ms
ScriptResource.axd
1332 ms
ScriptResource.axd
1418 ms
ScriptResource.axd
1452 ms
ScriptResource.axd
1467 ms
ScriptResource.axd
1500 ms
ScriptResource.axd
1500 ms
ScriptResource.axd
1547 ms
ScriptResource.axd
1612 ms
ScriptResource.axd
1650 ms
ScriptResource.axd
1661 ms
ScriptResource.axd
1696 ms
ScriptResource.axd
1700 ms
ScriptResource.axd
1760 ms
ScriptResource.axd
1803 ms
style.css
1619 ms
stylecomman.css
1416 ms
logo.png
1277 ms
gplay-icon.png
1270 ms
slide11.jpg
1313 ms
slide07.jpg
1341 ms
bootstrap.min.css
1380 ms
slide08.jpg
1244 ms
slide09.jpg
1249 ms
bootstrap-datetimepicker.min.css
1241 ms
slide10.jpg
1316 ms
slide06.jpg
1320 ms
slide01.jpg
1241 ms
slide02.jpg
1210 ms
jsonhandlerscript.js
1227 ms
scriptresource.axd
1224 ms
webresource.axd
1309 ms
scriptresource.axd
1191 ms
slide03.jpg
1214 ms
scriptresource.axd
1209 ms
scriptresource.axd
1225 ms
scriptresource.axd
1230 ms
scriptresource.axd
1269 ms
scriptresource.axd
1213 ms
scriptresource.axd
1204 ms
scriptresource.axd
1204 ms
scriptresource.axd
1207 ms
scriptresource.axd
1240 ms
scriptresource.axd
1249 ms
scriptresource.axd
1233 ms
scriptresource.axd
1205 ms
scriptresource.axd
1209 ms
scriptresource.axd
1210 ms
scriptresource.axd
1260 ms
scriptresource.axd
1231 ms
scriptresource.axd
1252 ms
css
27 ms
slide04.jpg
1203 ms
welcome-bus.png
1223 ms
logo.png
1215 ms
6aez4K2oVqwIvtU2Gg.ttf
24 ms
6ae84K2oVqwItm4TCpAy3w.ttf
28 ms
gplay-icon.png
3098 ms
slide11.jpg
3027 ms
slide07.jpg
3592 ms
img-journey.png
2935 ms
slide08.jpg
3330 ms
slide09.jpg
3298 ms
cardicon01.jpg
3093 ms
slide10.jpg
3392 ms
slide06.jpg
3615 ms
slide01.jpg
3392 ms
slide02.jpg
3535 ms
cardicon02.jpg
3296 ms
cardicon03.jpg
3468 ms
cardicon04.jpg
3398 ms
cardicon05.jpg
3380 ms
slide03.jpg
3621 ms
cardicon06.jpg
3512 ms
cardicon07.jpg
3492 ms
cardicon08.jpg
3486 ms
close_red.png
3408 ms
progressbar.gif
3398 ms
slide04.jpg
3124 ms
lock.png
3115 ms
bannershadow.png
3125 ms
icon-cal.png
3125 ms
top-destbg.jpg
3148 ms
destinationarrow.png
3206 ms
sap01.png
3291 ms
welcome-bus.png
3315 ms
sap02.png
3292 ms
sap03.png
3294 ms
sap05.jpg
3319 ms
icon-iipl.png
3387 ms
fontawesome-webfont.woff
3455 ms
glyphicons-halflings-regular.woff
3484 ms
analytics.js
1885 ms
img-journey.png
1621 ms
collect
11 ms
fontawesome-webfont.woff
218 ms
geetabus.in 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 input fields do not have accessible names
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
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
geetabus.in 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
geetabus.in 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
EN
EN
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.
geetabus.in
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: