Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

ridepost.com

RidePost - Shuttle and Bus Booking Engine

Page Load Speed

875 ms in total

First Response

181 ms

Resources Loaded

571 ms

Page Rendered

123 ms

ridepost.com screenshot

About Website

Welcome to ridepost.com homepage info - get ready to check Ride Post best content for United States right away, or after learning these important things about ridepost.com

RidePost is a bus and shuttle booking platform for businesses and universities.

Visit ridepost.com

Key Findings

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

Performance Metrics

ridepost.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

ridepost.com

181 ms

www.ridepost.com

104 ms

initial-c3282068c357e3fd670f9a6da6bc132a.css

130 ms

font-awesome.css

37 ms

ssk3jgr.js

221 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 29% of them (2 requests) were addressed to the original Ridepost.com, 29% (2 requests) were made to D2259kfzdkbdvw.cloudfront.net and 29% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (221 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.5 kB (73%)

Content Size

41.7 kB

After Optimization

11.2 kB

In fact, the total size of Ridepost.com main page is 41.7 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. Only 10% of websites need less resources to load. CSS take 34.2 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 3.2 kB

  • Original 4.9 kB
  • After minification 4.1 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 760 B, which is 16% 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 3.2 kB or 67% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.6 kB
  • After minification 2.6 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. Ride Post images are well optimized though.

CSS Optimization

-80%

Potential reduce by 27.2 kB

  • Original 34.2 kB
  • After minification 29.2 kB
  • After compression 7.0 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. Ridepost.com needs all CSS files to be minified and compressed as it can save up to 27.2 kB or 80% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ride Post. According to our analytics all requests are already optimized.

Accessibility Review

ridepost.com accessibility score

75

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ridepost.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

ridepost.com SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ridepost.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 Ridepost.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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