Tools & Wizards About Us
ridesharing.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ridesharing.com

Ridesharing.com - Find a rideshare or offer rides | Canada and US

Page Load Speed

2.5 sec in total

First Response

65 ms

Resources Loaded

2.1 sec

Page Rendered

279 ms

ridesharing.com screenshot

About Website

Click here to check amazing Ridesharing content for Canada. Otherwise, check out these important facts you probably never knew about ridesharing.com

Rideshare for local carpool and long distance travel. Join a community of 150 000 members, connect with drivers & passengers to offer a ride or to book a seat.

Visit ridesharing.com

Key Findings

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

Performance Metrics

ridesharing.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.655

8/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

ridesharing.com

65 ms

www.ridesharing.com

1571 ms

analytics.js

34 ms

bootstrap.min.css

57 ms

bootstrap.css

75 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 85% of them (62 requests) were addressed to the original Ridesharing.com, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Ridesharing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 988.2 kB (53%)

Content Size

1.9 MB

After Optimization

869.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ridesharing.com main page is 1.9 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. Javascripts take 718.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 34.9 kB

  • Original 43.2 kB
  • After minification 34.5 kB
  • After compression 8.4 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 8.8 kB, which is 20% 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 34.9 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 23.5 kB

  • Original 576.5 kB
  • After minification 553.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. Ridesharing images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 477.1 kB

  • Original 718.9 kB
  • After minification 539.3 kB
  • After compression 241.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 477.1 kB or 66% of the original size.

CSS Optimization

-87%

Potential reduce by 452.8 kB

  • Original 518.8 kB
  • After minification 407.6 kB
  • After compression 66.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. Ridesharing.com needs all CSS files to be minified and compressed as it can save up to 452.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (31%)

Requests Now

68

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ridesharing.com

ridesharing.com

65 ms

www.ridesharing.com

www.ridesharing.com

1571 ms

analytics.js

analytics.js

34 ms

bootstrap.min.css

bootstrap.min.css

57 ms

bootstrap.css

bootstrap.css

75 ms

jquery.min.js

jquery.min.js

107 ms

modernizr.js

modernizr.js

116 ms

main.js

main.js

90 ms

jquery-1.11.min.js

jquery-1.11.min.js

115 ms

jquery-2.1.1.js

jquery-2.1.1.js

160 ms

dw_paus_scroller.js

dw_paus_scroller.js

93 ms

bootstrap.js

bootstrap.js

133 ms

bootstrap.min.js

bootstrap.min.js

102 ms

css

css

63 ms

style.css

style.css

133 ms

js

js

90 ms

js

js

66 ms

bsn.AutoSuggest_2.1.3.js

bsn.AutoSuggest_2.1.3.js

134 ms

autosuggest_inquisitor.css

autosuggest_inquisitor.css

134 ms

collect

collect

32 ms

collect

collect

48 ms

js

js

54 ms

ga-audiences

ga-audiences

157 ms

style_m_top.css

style_m_top.css

15 ms

panel.css

panel.css

16 ms

panel-searchbar.css

panel-searchbar.css

17 ms

logo_CV_FR.png

logo_CV_FR.png

22 ms

Fleche_Droite.png

Fleche_Droite.png

29 ms

Twitter.png

Twitter.png

23 ms

Facebook.png

Facebook.png

22 ms

Logo_CV_EN.png

Logo_CV_EN.png

22 ms

Ban_top_2017.jpg

Ban_top_2017.jpg

49 ms

Pointo.png

Pointo.png

41 ms

Pouce_Accueil.png

Pouce_Accueil.png

49 ms

Car_Accueil.png

Car_Accueil.png

37 ms

Pin_Accueil.png

Pin_Accueil.png

65 ms

Credit_Accueil.png

Credit_Accueil.png

41 ms

auto.png

auto.png

79 ms

Passager.png

Passager.png

92 ms

Paiement.png

Paiement.png

84 ms

lieu.png

lieu.png

80 ms

Credit_Accueil.png

Credit_Accueil.png

64 ms

musique.png

musique.png

79 ms

487814_193HWI3G3AUO0408.jpg

487814_193HWI3G3AUO0408.jpg

80 ms

276995_17LD0238323I0550.jpg

276995_17LD0238323I0550.jpg

88 ms

115_LF51DX3GGFKCRQ48.jpg

115_LF51DX3GGFKCRQ48.jpg

106 ms

524664_21VYSM8816WO0236.jpg

524664_21VYSM8816WO0236.jpg

97 ms

Longue_Publication.png

Longue_Publication.png

93 ms

Longue_Paiement.png

Longue_Paiement.png

115 ms

Longue_Covoiturage.png

Longue_Covoiturage.png

115 ms

Longue_Transfert.png

Longue_Transfert.png

104 ms

Local_Reservation.png

Local_Reservation.png

107 ms

Ban_Top.jpg

Ban_Top.jpg

138 ms

LosAngeles.jpg

LosAngeles.jpg

140 ms

Boston3.jpg

Boston3.jpg

148 ms

SanDiego.jpg

SanDiego.jpg

139 ms

Vegas.jpg

Vegas.jpg

149 ms

SanDiego2.jpg

SanDiego2.jpg

137 ms

StLouis.jpg

StLouis.jpg

155 ms

Windsor2.jpg

Windsor2.jpg

165 ms

Minneapolis2.jpg

Minneapolis2.jpg

163 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

46 ms

NewYork3.jpg

NewYork3.jpg

147 ms

NewYork2.jpg

NewYork2.jpg

146 ms

Toronto5.jpg

Toronto5.jpg

156 ms

Baltimore1.jpg

Baltimore1.jpg

158 ms

Lettre.png

Lettre.png

157 ms

twitter.png

twitter.png

153 ms

facebook.png

facebook.png

144 ms

medium.css

medium.css

15 ms

narrow.css

narrow.css

15 ms

Accessibility Review

ridesharing.com accessibility score

54

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

ridesharing.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ridesharing.com SEO score

93

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

Image elements do not have [alt] attributes

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ridesharing.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 Ridesharing.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

ridesharing.com

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