Tools & Wizards About Us
bus.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

bus.com

Safe and reliable charter bus & shuttle rentals | Bus.com

Page Load Speed

1.7 sec in total

First Response

75 ms

Resources Loaded

708 ms

Page Rendered

870 ms

bus.com screenshot

About Website

Click here to check amazing Bus content for United States. Otherwise, check out these important facts you probably never knew about bus.com

Bus.com provides safe & efficient charter bus rentals, shuttle services, & sprinter van rentals for groups of any size. Book now, pay later!

Visit bus.com

Key Findings

We analyzed Bus.com page load time and found that the first response time was 75 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

bus.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.851

4/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

bus.com

75 ms

www.bus.com

60 ms

bat.js

32 ms

fs.js

39 ms

top-style23.css

19 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 44% of them (8 requests) were addressed to the original Bus.com, 6% (1 request) were made to Bat.bing.com and 6% (1 request) were made to Edge.fullstory.com. The less responsive or slowest element that took the longest time to load (335 ms) relates to the external source Sc.lfeeder.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.4 kB (10%)

Content Size

626.4 kB

After Optimization

566.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bus.com main page is 626.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 418.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 60.4 kB

  • Original 77.0 kB
  • After minification 71.2 kB
  • After compression 16.6 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 60.4 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 418.7 kB
  • After minification 418.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. Bus images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 17 B

  • Original 120.2 kB
  • After minification 120.2 kB
  • After compression 120.1 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 32 B

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

Requests Breakdown

Number of requests can be reduced by 10 (63%)

Requests Now

16

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

bus.com

bus.com

75 ms

www.bus.com

www.bus.com

60 ms

bat.js

bat.js

32 ms

fs.js

fs.js

39 ms

top-style23.css

top-style23.css

19 ms

btm-style21.css

btm-style21.css

36 ms

scripts-secondary.min.js

scripts-secondary.min.js

39 ms

scripts-all.min.js

scripts-all.min.js

74 ms

swiper-bundle.min.js

swiper-bundle.min.js

81 ms

email-decode.min.js

email-decode.min.js

26 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

88 ms

analytics.min.js

analytics.min.js

319 ms

bus-header-image-1-800x600.png

bus-header-image-1-800x600.png

96 ms

insight.min.js

insight.min.js

39 ms

lftracker_v1_JMvZ8gbBrkPa2pOd.js

lftracker_v1_JMvZ8gbBrkPa2pOd.js

335 ms

main.js

main.js

11 ms

insight_tag_errors.gif

insight_tag_errors.gif

249 ms

tr-rc.lfeeder.com

tr-rc.lfeeder.com

47 ms

Accessibility Review

bus.com accessibility score

95

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

<frame> or <iframe> elements do not have a title

Best Practices

bus.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

bus.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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

bus.com

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