Tools & Wizards About Us
thebus.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

thebus.com

Rutland Public Transportation | Paratransit & Daily Services | The Bus

Page Load Speed

841 ms in total

First Response

43 ms

Resources Loaded

413 ms

Page Rendered

385 ms

thebus.com screenshot

About Website

Click here to check amazing The Bus content. Otherwise, check out these important facts you probably never knew about thebus.com

Serving residents of the greater Rutland area for over 35 years, The Bus offers transportation services throughout all of Rutland country.

Visit thebus.com

Key Findings

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

Performance Metrics

thebus.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.29

41/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

thebus.com

43 ms

thebus.com

58 ms

css

36 ms

style.min.css

14 ms

automatic.css

20 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 73% of them (33 requests) were addressed to the original Thebus.com, 20% (9 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 (186 ms) relates to the external source Acsbapp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.0 kB (5%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 61.1 kB

  • Original 79.2 kB
  • After minification 78.3 kB
  • After compression 18.2 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 61.1 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 535 B

  • 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. The Bus images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 6.0 kB

  • Original 49.7 kB
  • After minification 49.4 kB
  • After compression 43.6 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 6.0 kB or 12% of the original size.

CSS Optimization

-17%

Potential reduce by 13.4 kB

  • Original 80.1 kB
  • After minification 80.0 kB
  • After compression 66.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. Thebus.com needs all CSS files to be minified and compressed as it can save up to 13.4 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (52%)

Requests Now

33

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thebus.com

thebus.com

43 ms

thebus.com

thebus.com

58 ms

css

css

36 ms

style.min.css

style.min.css

14 ms

automatic.css

automatic.css

20 ms

automatic-gutenberg.css

automatic-gutenberg.css

28 ms

oxygen.css

oxygen.css

29 ms

jquery.min.js

jquery.min.js

37 ms

wpgmza_data.js

wpgmza_data.js

28 ms

51.css

51.css

27 ms

69.css

69.css

30 ms

universal.css

universal.css

61 ms

automatic-oxygen.css

automatic-oxygen.css

33 ms

aos.css

aos.css

33 ms

frontend.css

frontend.css

59 ms

aos.js

aos.js

58 ms

frontend.min.js

frontend.min.js

134 ms

accessible-megamenu.js

accessible-megamenu.js

135 ms

megamenu-init.js

megamenu-init.js

137 ms

minimal-analytics.js

minimal-analytics.js

143 ms

app.js

app.js

186 ms

the-bus-logo.png

the-bus-logo.png

108 ms

tansit-icon.png

tansit-icon.png

108 ms

transit-icon-header.png

transit-icon-header.png

107 ms

home-hero.jpg

home-hero.jpg

177 ms

home-transit-logo-300x68.webp

home-transit-logo-300x68.webp

108 ms

home-transit-screenshots.webp

home-transit-screenshots.webp

108 ms

home-bus-routes.webp

home-bus-routes.webp

117 ms

home-trip-planner.webp

home-trip-planner.webp

114 ms

home-bus-fares.webp

home-bus-fares.webp

114 ms

home-about-bg.webp

home-about-bg.webp

115 ms

home-bottom-bg.jpg

home-bottom-bg.jpg

140 ms

footer-logo-min.png

footer-logo-min.png

131 ms

footer-facebook-icon.jpg

footer-facebook-icon.jpg

131 ms

footer-transit-app-icon.png

footer-transit-app-icon.png

131 ms

collect

collect

127 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

28 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

47 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

63 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

66 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

64 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

63 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

65 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

65 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

65 ms

Accessibility Review

thebus.com accessibility score

93

Accessibility Issues

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

Best Practices

thebus.com best practices score

92

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

SEO Factors

thebus.com SEO score

99

Search Engine Optimization Advices

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

thebus.com

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