Tools & Wizards About Us
factualdata.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

factualdata.com

Mortgage Lending Credit & Verification Services | Factual Data

Page Load Speed

557 ms in total

First Response

13 ms

Resources Loaded

255 ms

Page Rendered

289 ms

factualdata.com screenshot

About Website

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

Factual Data is a trusted provider of consumer credit and verification services vital to the mortgage lending community and its consumers.

Visit factualdata.com

Key Findings

We analyzed Factualdata.com page load time and found that the first response time was 13 ms and then it took 544 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

factualdata.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

factualdata.com

13 ms

factualdata.com

18 ms

www.factualdata.com

23 ms

jquery.min.js

24 ms

c5bf70b5ee.js

76 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 75% of them (24 requests) were addressed to the original Factualdata.com, 13% (4 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (102 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.1 kB (4%)

Content Size

897.4 kB

After Optimization

862.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Factualdata.com main page is 897.4 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. 25% of websites need less resources to load. Images take 842.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 16.0 kB

  • Original 19.9 kB
  • After minification 13.9 kB
  • After compression 4.0 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 6.1 kB, which is 30% 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 16.0 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 19.2 kB

  • Original 842.1 kB
  • After minification 822.9 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. Factual Data images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 6 B

  • Original 35.4 kB
  • After minification 35.4 kB
  • After compression 35.4 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.

Requests Breakdown

Number of requests can be reduced by 4 (16%)

Requests Now

25

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

factualdata.com

factualdata.com

13 ms

factualdata.com

factualdata.com

18 ms

www.factualdata.com

www.factualdata.com

23 ms

jquery.min.js

jquery.min.js

24 ms

c5bf70b5ee.js

c5bf70b5ee.js

76 ms

responsiveslides.min.js

responsiveslides.min.js

9 ms

css

css

37 ms

style.css

style.css

18 ms

main.js

main.js

21 ms

gtm.js

gtm.js

102 ms

logo.png

logo.png

67 ms

icon-diamond-mark-white.png

icon-diamond-mark-white.png

61 ms

undisclosed-debt-monitoring-banner.jpg

undisclosed-debt-monitoring-banner.jpg

81 ms

bg-diamond.jpg

bg-diamond.jpg

68 ms

tri-merge-credit-report-product.jpg

tri-merge-credit-report-product.jpg

71 ms

undisclosed-debt-monitoring-product.jpg

undisclosed-debt-monitoring-product.jpg

72 ms

workflow-solutions-product.jpg

workflow-solutions-product.jpg

74 ms

all-products.jpg

all-products.jpg

72 ms

icon-quote.png

icon-quote.png

71 ms

icon-lending-cycle.png

icon-lending-cycle.png

73 ms

icon-pre-qual.png

icon-pre-qual.png

74 ms

icon-arrows-cycle.png

icon-arrows-cycle.png

73 ms

icon-application.png

icon-application.png

74 ms

icon-processing.png

icon-processing.png

75 ms

icon-underwriting.png

icon-underwriting.png

75 ms

icon-pre-close.png

icon-pre-close.png

76 ms

icon-post-closing.png

icon-post-closing.png

75 ms

linkedin.png

linkedin.png

76 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

19 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

23 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

27 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

29 ms

Accessibility Review

factualdata.com accessibility score

81

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

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

factualdata.com SEO score

85

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Factualdata.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Factualdata.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

factualdata.com

Open Graph description is not detected on the main page of Factual Data. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: