Tools & Wizards About Us
faraday.io screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    52% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

faraday.io

Faraday prediction platform - Faraday

Page Load Speed

1.5 sec in total

First Response

77 ms

Resources Loaded

1.1 sec

Page Rendered

247 ms

faraday.io screenshot

About Website

Welcome to faraday.io homepage info - get ready to check Faraday best content for United States right away, or after learning these important things about faraday.io

Meet Faraday, the customer prediction platform that helps your business grow faster with the power of AI. Start free today. No coding or data science skills needed.

Visit faraday.io

Key Findings

We analyzed Faraday.io page load time and found that the first response time was 77 ms and then it took 1.4 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

faraday.io performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value1,990 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

www.faraday.io

77 ms

css

119 ms

normalize.css

85 ms

fonts.css

524 ms

style-cf.css

90 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Faraday.io, 15% (8 requests) were made to Cdn2.hubspot.net and 12% (6 requests) were made to . The less responsive or slowest element that took the longest time to load (524 ms) relates to the external source Cloud.typography.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 478.3 kB (54%)

Content Size

886.9 kB

After Optimization

408.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Faraday.io main page is 886.9 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. 45% of websites need less resources to load. Javascripts take 440.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 26.5 kB

  • Original 34.2 kB
  • After minification 32.0 kB
  • After compression 7.7 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 26.5 kB or 77% of the original size.

Image Optimization

-21%

Potential reduce by 2.0 kB

  • Original 9.4 kB
  • After minification 7.4 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. Obviously, Faraday needs image optimization as it can save up to 2.0 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 292.1 kB

  • Original 440.1 kB
  • After minification 432.8 kB
  • After compression 148.0 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 292.1 kB or 66% of the original size.

CSS Optimization

-39%

Potential reduce by 157.8 kB

  • Original 403.3 kB
  • After minification 383.0 kB
  • After compression 245.5 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. Faraday.io needs all CSS files to be minified and compressed as it can save up to 157.8 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (50%)

Requests Now

40

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.faraday.io

www.faraday.io

77 ms

css

css

119 ms

normalize.css

normalize.css

85 ms

fonts.css

fonts.css

524 ms

style-cf.css

style-cf.css

90 ms

index.css

index.css

111 ms

jquery-1.11.2.js

jquery-1.11.2.js

128 ms

public_common.css

public_common.css

94 ms

mapbox.css

mapbox.css

92 ms

current.js

current.js

192 ms

loader.min.js

loader.min.js

93 ms

public_common.js

public_common.js

103 ms

mapbox.js

mapbox.js

103 ms

F2E9F32780DBB2983.css

F2E9F32780DBB2983.css

133 ms

analytics.min.js

analytics.min.js

175 ms

logo.svg

logo.svg

116 ms

078f8416-e565-4f73-82af-bbafab4048ec.png

078f8416-e565-4f73-82af-bbafab4048ec.png

155 ms

anthropomorphic_clipboard.svg

anthropomorphic_clipboard.svg

113 ms

map_with_marker.svg

map_with_marker.svg

202 ms

house.svg

house.svg

214 ms

robot.svg

robot.svg

166 ms

a20d95c5-7614-41c8-8c22-e5e5ef8cb018.png

a20d95c5-7614-41c8-8c22-e5e5ef8cb018.png

203 ms

14c3fddd-b69b-4e28-9c14-26f54a503e4d.png

14c3fddd-b69b-4e28-9c14-26f54a503e4d.png

168 ms

07e99f4b-d998-4ad2-aa37-1dadaa75d2bc.png

07e99f4b-d998-4ad2-aa37-1dadaa75d2bc.png

238 ms

982a71b2-0b55-418b-802d-b9aace0b1765.png

982a71b2-0b55-418b-802d-b9aace0b1765.png

212 ms

gtm.js

gtm.js

44 ms

uWNHDXjZGHE+rxu4ngOAs+NU5H+Gb6yEOi5k3ao8XVkXkfmiZE5nZRi6PUoe7k+3uDd+j3ky+VsAhSfX8j8XwpF+ohXBMcEKuZ+lN9qGTT2cMtJXn1LtjA0lMHDk4tDOYGultSVQf8dgsM99YR2M615DZxmmdF51zrpheQDHZ8U6WPW42LG57c8bfH0+G8pfwEW10LJ

uWNHDXjZGHE+rxu4ngOAs+NU5H+Gb6yEOi5k3ao8XVkXkfmiZE5nZRi6PUoe7k+3uDd+j3ky+VsAhSfX8j8XwpF+ohXBMcEKuZ+lN9qGTT2cMtJXn1LtjA0lMHDk4tDOYGultSVQf8dgsM99YR2M615DZxmmdF51zrpheQDHZ8U6WPW42LG57c8bfH0+G8pfwEW10LJ

9 ms

NbnrZ4evy3lL8ApE9CrQ==

NbnrZ4evy3lL8ApE9CrQ==

8 ms

EL5btCvQ==

EL5btCvQ==

8 ms

ARbXQsk=

ARbXQsk=

6 ms

NbnrZ4evy3lL8ApE9CrQ==

NbnrZ4evy3lL8ApE9CrQ==

5 ms

nsEiwfqCe1mWvMKSpplRudda4XjohzouDhPHrOeFjM+v+Vpiyenf0vxC+W7Qr0=

nsEiwfqCe1mWvMKSpplRudda4XjohzouDhPHrOeFjM+v+Vpiyenf0vxC+W7Qr0=

5 ms

city_pattern.svg

city_pattern.svg

114 ms

page_with_folded_corner.svg

page_with_folded_corner.svg

114 ms

Glitz.ttf

Glitz.ttf

10 ms

515497.js

515497.js

170 ms

conversion_async.js

conversion_async.js

46 ms

icons-ffffff@2x.png

icons-ffffff@2x.png

17 ms

97 ms

34 ms

analytics.js

analytics.js

7 ms

collect

collect

8 ms

collect

collect

52 ms

34 ms

53 ms

ga-audiences

ga-audiences

17 ms

loader-v2.js

loader-v2.js

29 ms

loader-v2.js

loader-v2.js

26 ms

loader-v2.js

loader-v2.js

32 ms

loader-v2.js

loader-v2.js

32 ms

loader-v2.js

loader-v2.js

41 ms

__ptq.gif

__ptq.gif

10 ms

Accessibility Review

faraday.io accessibility score

90

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

Image elements do not have [alt] attributes

Best Practices

faraday.io 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

faraday.io SEO score

71

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 Faraday.io 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 Faraday.io 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

faraday.io

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