Tools & Wizards About Us

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

fareestimate.com

Uber Fare Estimate vs Lyft Estimate - Real Time Price Comparison

Page Load Speed

1.2 sec in total

First Response

113 ms

Resources Loaded

918 ms

Page Rendered

168 ms

About Website

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

Fare Estimate allows you to compare Uber vs Lyft prices for any route with real time prices allowing you to choose the cheaper fare and to avoid surges.

Visit fareestimate.com

Key Findings

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

Performance Metrics

fareestimate.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

fareestimate.com

113 ms

fareestimate.com

387 ms

style.min.css

19 ms

styles.css

46 ms

font-awesome.min.css

61 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 69% of them (33 requests) were addressed to the original Fareestimate.com, 13% (6 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (387 ms) belongs to the original domain Fareestimate.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.1 kB (3%)

Content Size

1.3 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fareestimate.com main page is 1.3 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 802.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 36.0 kB

  • Original 47.1 kB
  • After minification 47.0 kB
  • After compression 11.1 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 36.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 736 B

  • Original 802.0 kB
  • After minification 801.2 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. Fare Estimate images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 346 B

  • Original 314.0 kB
  • After minification 314.0 kB
  • After compression 313.7 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 110 B

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

Requests Breakdown

Number of requests can be reduced by 28 (74%)

Requests Now

38

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

fareestimate.com accessibility score

82

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fareestimate.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 Fareestimate.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 Fareestimate.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

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