Tools & Wizards About Us
datatrue.net screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

datatrue.net

Merchant Tools Verify Identity | Check Banking and Credit Card Information | DATATrue, LLC

Page Load Speed

4.6 sec in total

First Response

863 ms

Resources Loaded

3.2 sec

Page Rendered

522 ms

datatrue.net screenshot

About Website

Welcome to datatrue.net homepage info - get ready to check DATATrue best content right away, or after learning these important things about datatrue.net

DataTrue, LLC offers a full range of merchants tools to verify identity and banking information and to check background and credit card information.

Visit datatrue.net

Key Findings

We analyzed Datatrue.net page load time and found that the first response time was 863 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

datatrue.net performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

www.datatrue.net

863 ms

wp-emoji-release.min.js

40 ms

styles.css

77 ms

settings.css

127 ms

tmm_custom_style.min.css

160 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 72% of them (50 requests) were addressed to the original Datatrue.net, 7% (5 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (863 ms) belongs to the original domain Datatrue.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (50%)

Content Size

2.0 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Datatrue.net main page is 2.0 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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 131.4 kB

  • Original 167.3 kB
  • After minification 161.3 kB
  • After compression 35.9 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 131.4 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 1.8 kB

  • Original 308.0 kB
  • After minification 306.1 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. DATATrue images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 524.2 kB

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

CSS Optimization

-85%

Potential reduce by 367.5 kB

  • Original 431.7 kB
  • After minification 395.0 kB
  • After compression 64.2 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. Datatrue.net needs all CSS files to be minified and compressed as it can save up to 367.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (63%)

Requests Now

65

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.datatrue.net

www.datatrue.net

863 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

40 ms

styles.css

styles.css

77 ms

settings.css

settings.css

127 ms

tmm_custom_style.min.css

tmm_custom_style.min.css

160 ms

sfsi-style.css

sfsi-style.css

144 ms

font-awesome.min.css

font-awesome.min.css

171 ms

field_social_profiles_frontend.css

field_social_profiles_frontend.css

141 ms

front_end.css

front_end.css

153 ms

style.css

style.css

286 ms

jquery.js

jquery.js

255 ms

jquery-migrate.min.js

jquery-migrate.min.js

185 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

274 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

255 ms

modernizr.custom.min.js

modernizr.custom.min.js

217 ms

jquery.slideshow.js

jquery.slideshow.js

218 ms

jquery.stripslashes.js

jquery.stripslashes.js

254 ms

wthvideo5.js

wthvideo5.js

266 ms

in.js

in.js

25 ms

cvg-styles.css

cvg-styles.css

293 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

304 ms

scripts.js

scripts.js

301 ms

core.min.js

core.min.js

306 ms

modernizr.custom.min.js

modernizr.custom.min.js

311 ms

jquery.shuffle.min.js

jquery.shuffle.min.js

320 ms

random-shuffle-min.js

random-shuffle-min.js

324 ms

custom.js

custom.js

354 ms

scrollReveal.js

scrollReveal.js

348 ms

stellar.js

stellar.js

351 ms

scripts.min.js

scripts.min.js

363 ms

wp-embed.min.js

wp-embed.min.js

357 ms

jwplayer.js

jwplayer.js

475 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

391 ms

frontend.js

frontend.js

397 ms

api.js

api.js

39 ms

jsn-fonticomoon.css

jsn-fonticomoon.css

263 ms

icomoon.css

icomoon.css

257 ms

gplay.png

gplay.png

70 ms

DATATrue_sm.png

DATATrue_sm.png

70 ms

blast.jpg

blast.jpg

71 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

56 ms

blast2.jpg

blast2.jpg

235 ms

11_DATATrue2.png

11_DATATrue2.png

55 ms

transparent_facebook.png

transparent_facebook.png

157 ms

transparent_twitter.png

transparent_twitter.png

157 ms

twitter.png

twitter.png

157 ms

transparent_linkedin.png

transparent_linkedin.png

157 ms

bot_tip_icn.png

bot_tip_icn.png

136 ms

sdk.js

sdk.js

90 ms

widgets.js

widgets.js

134 ms

recaptcha__en.js

recaptcha__en.js

81 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

135 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

137 ms

revolution.extension.parallax.min.js

revolution.extension.parallax.min.js

134 ms

ajax-loader.gif

ajax-loader.gif

89 ms

sdk.js

sdk.js

13 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

75 ms

fallback

fallback

37 ms

settings

settings

101 ms

fallback__ltr.css

fallback__ltr.css

55 ms

css

css

31 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

4 ms

logo_48.png

logo_48.png

12 ms

embeds

embeds

39 ms

embeds

embeds

49 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

16 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

22 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

28 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

33 ms

Accessibility Review

datatrue.net accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

[id] attributes on active, focusable elements are not unique

Best Practices

datatrue.net 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

datatrue.net SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Datatrue.net 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 Datatrue.net 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

datatrue.net

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