Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

getrewards.fedex.com

My FedEx Rewards | US

Page Load Speed

1.5 sec in total

First Response

168 ms

Resources Loaded

1 sec

Page Rendered

265 ms

getrewards.fedex.com screenshot

About Website

Click here to check amazing Get Rewards Fed Ex content for United States. Otherwise, check out these important facts you probably never knew about getrewards.fedex.com

My FedEx Rewards allows businesses in the US to earn rewards for their loyalty in shipping and printing with FedEx. Join the program or login to redeem rewards.

Visit getrewards.fedex.com

Key Findings

We analyzed Getrewards.fedex.com page load time and found that the first response time was 168 ms and then it took 1.3 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

getrewards.fedex.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

getrewards.fedex.com

168 ms

clientlib-dependencies.css

72 ms

clientlib-dependencies.js

218 ms

clientlib-base-redesign.css

160 ms

all.min.css

42 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 64% of them (25 requests) were addressed to the original Getrewards.fedex.com, 8% (3 requests) were made to Assets.adobedtm.com and 8% (3 requests) were made to Dpm.demdex.net. The less responsive or slowest element that took the longest time to load (440 ms) relates to the external source Fedex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 243.2 kB (12%)

Content Size

2.0 MB

After Optimization

1.7 MB

In fact, the total size of Getrewards.fedex.com 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. 35% of websites need less resources to load. Images take 958.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 72.9 kB

  • Original 83.8 kB
  • After minification 77.3 kB
  • After compression 10.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 72.9 kB or 87% of the original size.

Image Optimization

-8%

Potential reduce by 78.5 kB

  • Original 958.7 kB
  • After minification 880.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. Get Rewards Fed Ex images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 72.7 kB

  • Original 724.0 kB
  • After minification 723.8 kB
  • After compression 651.3 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

-10%

Potential reduce by 19.1 kB

  • Original 186.3 kB
  • After minification 186.3 kB
  • After compression 167.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. Getrewards.fedex.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (21%)

Requests Now

33

After Optimization

26

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

Accessibility Review

getrewards.fedex.com accessibility score

88

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

getrewards.fedex.com best practices score

58

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

getrewards.fedex.com SEO score

93

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

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 Getrewards.fedex.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 Getrewards.fedex.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

Open Graph description is not detected on the main page of Get Rewards Fed Ex. 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: