Tools & Wizards About Us
merchantgeo.force.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

merchantgeo.force.com

Amex Offers | Explore Offers & Benefits with American Express®

Page Load Speed

3.4 sec in total

First Response

111 ms

Resources Loaded

2.6 sec

Page Rendered

697 ms

merchantgeo.force.com screenshot

About Website

Welcome to merchantgeo.force.com homepage info - get ready to check Merchantgeo Force best content for United States right away, or after learning these important things about merchantgeo.force.com

Amex Offers Helps Eligible American Express® Card Members Earn Rewards On Qualifying Purchases for Things You Love. Explore & Add Card Offers Today!

Visit merchantgeo.force.com

Key Findings

We analyzed Merchantgeo.force.com page load time and found that the first response time was 111 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

merchantgeo.force.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value3,890 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

111 ms

dls.min.css

115 ms

enterprise.min.62e485da9610c83265d1dc2dbf8bfaa4.css

47 ms

clientlibs.min.86dbb33c40d57dfb3fcb6ac39c588103.css

86 ms

codesnippet.min.149f1b4583ecf1df45db55c77e3b00e7.css

94 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Merchantgeo.force.com, 44% (17 requests) were made to Americanexpress.com and 5% (2 requests) were made to Icm.aexp-static.com. The less responsive or slowest element that took the longest time to load (805 ms) relates to the external source Americanexpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (72%)

Content Size

1.8 MB

After Optimization

514.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Merchantgeo.force.com main page is 1.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. 40% of websites need less resources to load. Javascripts take 788.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 551.7 kB

  • Original 614.8 kB
  • After minification 577.6 kB
  • After compression 63.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 551.7 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 33.2 kB
  • After minification 33.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. Merchantgeo Force images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 425.6 kB

  • Original 788.6 kB
  • After minification 788.5 kB
  • After compression 363.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 425.6 kB or 54% of the original size.

CSS Optimization

-86%

Potential reduce by 346.3 kB

  • Original 401.8 kB
  • After minification 400.7 kB
  • After compression 55.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. Merchantgeo.force.com needs all CSS files to be minified and compressed as it can save up to 346.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (61%)

Requests Now

28

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

111 ms

dls.min.css

dls.min.css

115 ms

enterprise.min.62e485da9610c83265d1dc2dbf8bfaa4.css

enterprise.min.62e485da9610c83265d1dc2dbf8bfaa4.css

47 ms

clientlibs.min.86dbb33c40d57dfb3fcb6ac39c588103.css

clientlibs.min.86dbb33c40d57dfb3fcb6ac39c588103.css

86 ms

codesnippet.min.149f1b4583ecf1df45db55c77e3b00e7.css

codesnippet.min.149f1b4583ecf1df45db55c77e3b00e7.css

94 ms

editablegird.min.b7d82f85fc41036dac496478f5d69865.css

editablegird.min.b7d82f85fc41036dac496478f5d69865.css

73 ms

navScript.js

navScript.js

205 ms

content.min.5f7d2128e1069cfa3ac6e63135bf0998.css

content.min.5f7d2128e1069cfa3ac6e63135bf0998.css

54 ms

footerScript.js

footerScript.js

198 ms

navscript.js

navscript.js

58 ms

service-worker-client.js

service-worker-client.js

133 ms

OneTaglibrary.min.js

OneTaglibrary.min.js

54 ms

script-supplier.js

script-supplier.js

54 ms

dls.min.js

dls.min.js

73 ms

enterprise.min.28ccc67af1912c68518f9c6d8975768f.js

enterprise.min.28ccc67af1912c68518f9c6d8975768f.js

103 ms

login.min.06e906c2e44e9038348f5eb38045e549.js

login.min.06e906c2e44e9038348f5eb38045e549.js

63 ms

clientlibs.min.2c2e5b5190523d80db6ad67d3c197c0b.js

clientlibs.min.2c2e5b5190523d80db6ad67d3c197c0b.js

66 ms

codesnippet.min.2cbccba84f1aa1778738683f6bf77d69.js

codesnippet.min.2cbccba84f1aa1778738683f6bf77d69.js

68 ms

67 ms

dls-icons.min.js

dls-icons.min.js

400 ms

dls-logo-bluebox-solid.svg

dls-logo-bluebox-solid.svg

100 ms

dls-logo-stack.svg

dls-logo-stack.svg

62 ms

dls-logo-stack-white.svg

dls-logo-stack-white.svg

151 ms

dls-flag-us.svg

dls-flag-us.svg

107 ms

dls-logo-line.svg

dls-logo-line.svg

105 ms

dls-flag-us.svg

dls-flag-us.svg

134 ms

grid.less

grid.less

214 ms

satelliteLib-bea3c9697c6240996731438f72200c4b82ae0d40.js

satelliteLib-bea3c9697c6240996731438f72200c4b82ae0d40.js

38 ms

error.html

error.html

565 ms

amex-offers-app-1800x360_revised.png

amex-offers-app-1800x360_revised.png

634 ms

325e6ad0-38fb-4bad-861c-d965eab101d5-3.woff

325e6ad0-38fb-4bad-861c-d965eab101d5-3.woff

16 ms

325e6ad0-38fb-4bad-861c-d965eab101d5-3.woff

325e6ad0-38fb-4bad-861c-d965eab101d5-3.woff

122 ms

3be50273-0b2e-4aef-ae68-882eacd611f9-3.woff

3be50273-0b2e-4aef-ae68-882eacd611f9-3.woff

123 ms

3be50273-0b2e-4aef-ae68-882eacd611f9-3.woff

3be50273-0b2e-4aef-ae68-882eacd611f9-3.woff

122 ms

0fababca-4914-46dd-9b0f-efbd51f67ae8-3.woff

0fababca-4914-46dd-9b0f-efbd51f67ae8-3.woff

16 ms

0fababca-4914-46dd-9b0f-efbd51f67ae8-3.woff

0fababca-4914-46dd-9b0f-efbd51f67ae8-3.woff

122 ms

dls-icons.woff

dls-icons.woff

123 ms

raybanls.jpg

raybanls.jpg

473 ms

raybanlogo.png

raybanlogo.png

805 ms

Accessibility Review

merchantgeo.force.com accessibility score

94

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Best Practices

merchantgeo.force.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

merchantgeo.force.com SEO score

91

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

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 Merchantgeo.force.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 Merchantgeo.force.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

merchantgeo.force.com

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