Tools & Wizards About Us
merchantaccounts.direct screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

merchantaccounts.direct

GenieCard | Easier. Faster. Secure Payments. - True Payments

Page Load Speed

8.1 sec in total

First Response

195 ms

Resources Loaded

7.6 sec

Page Rendered

333 ms

merchantaccounts.direct screenshot

About Website

Click here to check amazing Merchantaccounts content. Otherwise, check out these important facts you probably never knew about merchantaccounts.direct

A secure payment system for the cannabis industry, cash-only businesses, families who send money or those with bad or no credit.

Visit merchantaccounts.direct

Key Findings

We analyzed Merchantaccounts.direct page load time and found that the first response time was 195 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

merchantaccounts.direct performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value24.8 s

0/100

25%

SI (Speed Index)

Value22.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.462

19/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

merchantaccounts.direct

195 ms

www.merchantaccounts.direct

2793 ms

fbevents.js

24 ms

js

67 ms

et-core-unified-2.min.css

99 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 41% of them (24 requests) were addressed to the original Merchantaccounts.direct, 40% (23 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Merchantaccounts.direct.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.0 kB (10%)

Content Size

2.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Merchantaccounts.direct main page is 2.8 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 265.4 kB

  • Original 302.1 kB
  • After minification 298.5 kB
  • After compression 36.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 265.4 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 2.1 MB
  • After minification 2.1 MB

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. Merchantaccounts images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.4 kB

  • Original 364.6 kB
  • After minification 364.6 kB
  • After compression 361.2 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 60 B

  • Original 30.3 kB
  • After minification 30.3 kB
  • After compression 30.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. Merchantaccounts.direct has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (76%)

Requests Now

29

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

merchantaccounts.direct

merchantaccounts.direct

195 ms

www.merchantaccounts.direct

www.merchantaccounts.direct

2793 ms

fbevents.js

fbevents.js

24 ms

js

js

67 ms

et-core-unified-2.min.css

et-core-unified-2.min.css

99 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

197 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

293 ms

jquery.min.js

jquery.min.js

393 ms

jquery-migrate.min.js

jquery-migrate.min.js

316 ms

scripts.min.js

scripts.min.js

493 ms

jquery.fitvids.js

jquery.fitvids.js

325 ms

easypiechart.js

easypiechart.js

314 ms

salvattore.js

salvattore.js

383 ms

common.js

common.js

411 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

417 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

508 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

482 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

482 ms

api.js

api.js

91 ms

et-divi-dynamic-tb-318-tb-53-2-late.css

et-divi-dynamic-tb-318-tb-53-2-late.css

405 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

69 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

73 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

71 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

72 ms

modules.ttf

modules.ttf

540 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff

40 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

41 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff

42 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

43 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff

40 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

44 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff

41 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

42 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff

42 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

43 ms

truepayments-logo.svg

truepayments-logo.svg

194 ms

truepayments-geniecard-merchants-hero.jpg

truepayments-geniecard-merchants-hero.jpg

207 ms

recaptcha__en.js

recaptcha__en.js

56 ms

anchor

anchor

35 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

13 ms

IDLZ5bdCrEGdGR5FKKZfiIWvV7rMSlbAHUEzxUIOBQg.js

IDLZ5bdCrEGdGR5FKKZfiIWvV7rMSlbAHUEzxUIOBQg.js

35 ms

webworker.js

webworker.js

38 ms

logo_48.png

logo_48.png

22 ms

truepayments-logo.svg

truepayments-logo.svg

91 ms

truepayments-geniecard-merchants-hero.jpg

truepayments-geniecard-merchants-hero.jpg

540 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

6 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

22 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

22 ms

recaptcha__en.js

recaptcha__en.js

16 ms

truepayments-geniecard-mobile-money-send-P2P-hero.jpg

truepayments-geniecard-mobile-money-send-P2P-hero.jpg

82 ms

truepayments-geniecard-mobile-money-send-P2P-hero.jpg

truepayments-geniecard-mobile-money-send-P2P-hero.jpg

534 ms

Accessibility Review

merchantaccounts.direct accessibility score

75

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

Links do not have a discernible name

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

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

merchantaccounts.direct 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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

merchantaccounts.direct 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

Links do not have descriptive text

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 Merchantaccounts.direct 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 Merchantaccounts.direct 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

merchantaccounts.direct

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