FEDEX.COM FedEx Global Home - Select Your Location


fedex.com website information.

fedex.com website servers are located in United States and are responding from following IP address 204.135.8.50. Check the full list of most visited websites located in United States.

fedex.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for fedex.com domain:

  • use5.akam.net
  • c.service.afiliasdns.net
  • ns1-244.akam.net
  • a.service.afiliasdns.info
  • kate.fedex.com
  • land.fedex.com
  • grace.fedex.com
  • b.service.afiliasdns.org
  • ns1-193.akam.net
  • spdns3.cscdns.net

and probably website fedex.com is hosted by akam.net web hosting company. Check the complete list of other most popular websites hosted by akam.net hosting company.

According to Alexa traffic rank the highest website fedex.com position was 200 (in the world). The lowest Alexa rank position was 1366. Now website fedex.com ranked in Alexa database as number 255 (in the world).

Website fedex.com Desktop speed measurement score (72/100) is better than the results of 56.22% of other sites shows that the page desktop performance can be improved.

fedex.com Mobile usability score (96/100) is better than the results of 60.6% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of fedex.com (51/100) is better than the results of 33.56% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Oct-16-2019 255430
Oct-15-2019 685-200
Oct-14-2019 485-203
Oct-13-2019 282-5
Oct-12-2019 277-27
Oct-11-2019 250-36
Oct-10-2019 21440

Advertisement

fedex.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


fedex.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: FEDEX.COM
Registry Domain ID: 1938576_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.corporatedomains.com
Registrar URL: http://www.cscglobal.com/global/web/csc/digital-brand-services.html
Updated Date: 2019-05-23T10:24:44Z
Creation Date: 1991-02-26T05:00:00Z
Registry Expiry Date: 2019-11-29T18:27:45Z
Registrar: CSC Corporate Domains, Inc.
Registrar IANA ID: 299
Registrar Abuse Contact Email: domainabuse@cscglobal.com
Registrar Abuse Contact Phone: 8887802723
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
Name Server: A.SERVICE.AFILIASDNS.INFO
Name Server: B.SERVICE.AFILIASDNS.ORG
Name Server: C.SERVICE.AFILIASDNS.NET
Name Server: GRACE.FEDEX.COM
Name Server: KATE.FEDEX.COM
Name Server: LAND.FEDEX.COM
Name Server: NS1-193.AKAM.NET
Name Server: NS1-244.AKAM.NET
Name Server: SPDNS3.CSCDNS.NET
Name Server: USE5.AKAM.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2019-08-26T23:36:11Z

fedex.com server information

Servers Location

fedex.com desktop page speed rank

Last tested: 2019-08-26


Desktop Speed Medium
72/100

fedex.com Desktop Speed Test Quick Summary


priority - 14 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://www.fedex.com/etc.clientlibs/clientlibs/gr…6dfb06c17e789ad4dbd.js
https://www.fedex.com/etc.clientlibs/clientlibs/fe…469fb833efab6642c04.js
https://www.fedex.com/etc.clientlibs/clientlibs/fe…945b3eb5019935e2c7e.js
https://assets.adobedtm.com/7d22d70439461d29ed62de…cead05e17462ad161ac.js
https://assets.adobedtm.com/7d22d70439461d29ed62de…faee455cca08c786d12.js

Optimize CSS Delivery of the following:

https://www.fedex.com/etc.clientlibs/clientlibs/fe…67063c8d3ff337d862.css

priority - 11 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.fedex.com/etc/services/getalerts.false…se-location.html.jsonp (expiration not specified)
https://www.fedex.com/etc/services/getapigconfigs.jsonp (expiration not specified)
https://www.googletagmanager.com/gtag/js?id=DC-4191263 (15 minutes)
https://maps.googleapis.com/maps/api/js?key=AIzaSy…PUT.gmInitAutoComplete (30 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…faee455cca08c786d12.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…21104ca42cc1f30a2f4.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…cead05e17462ad161ac.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…a3264746d3fce00d53a.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…84d64746d57b6001018.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…78f64746d6831001a2b.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…945b3eb5019935e2c7e.js (6.3 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/gr…6dfb06c17e789ad4dbd.js (6.4 hours)
https://www.fedex.com/etc/clientlibs/fedex/common/…js4.14.0/lodash.min.js (10.3 hours)
https://www.fedex.com/content/dam/fedex-com/logos/logo.png (11.7 hours)
https://www.fedex.com/content/dam/fedex-com/common/sprite-placeholder.png (13 hours)
https://www.fedex.com/etc/clientlibs/fedex/common/…fonts/Roboto-Light.ttf (14.2 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…67063c8d3ff337d862.css (14.4 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…469fb833efab6642c04.js (16 hours)
https://www.fedex.com/etc/clientlibs/fedex/common/…nts/Roboto-Regular.ttf (19.3 hours)
https://www.fedex.com/etc/clientlibs/fedex/common/…/fonts/Roboto-Bold.ttf (20.3 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…rces/footer-sprite.png (22.7 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…675ce7b80af5ac35ce5.js (22.9 hours)

priority - 7 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://fedex.com/
http://www.fedex.com/
https://www.fedex.com/global/choose-location.html

priority - 5 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 44KiB (54% reduction).

Compressing https://www.fedex.com/etc.clientlibs/clientlibs/fe…rces/footer-sprite.png could save 20KiB (37% reduction).
Compressing and resizing https://www.fedex.com/content/dam/fedex-com/logos/logo.png could save 16.4KiB (93% reduction).
Compressing https://www.fedex.com/content/dam/fedex-com/common/sprite-placeholder.png could save 7.6KiB (99% reduction).

priority - 2 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 17.7KiB (29% reduction).

Minifying https://assets.adobedtm.com/7d22d70439461d29ed62de…21104ca42cc1f30a2f4.js could save 17.7KiB (29% reduction) after compression.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1KiB (13% reduction).

Minifying https://www.fedex.com/global/choose-location.html could save 1KiB (13% reduction) after compression.

priority - 0 Reduce server response time

In our test, your server responded in 0.20 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 213B (46% reduction).

Compressing https://smetrics.fedex.com/b/ss/fedexglbl,fedexus/…Y&bw=1366&bh=768&AQE=1 could save 213B (46% reduction).

fedex.com Desktop Resources

Total Resources37
Number of Hosts13
Static Resources23
JavaScript Resources23
CSS Resources1

fedex.com Desktop Resource Breakdown

fedex.com mobile page speed rank

Last tested: 2019-08-26


Mobile Speed Bad
51/100

fedex.com Mobile Speed Test Quick Summary


priority - 56 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://www.fedex.com/etc.clientlibs/clientlibs/gr…6dfb06c17e789ad4dbd.js
https://www.fedex.com/etc.clientlibs/clientlibs/fe…469fb833efab6642c04.js
https://www.fedex.com/etc.clientlibs/clientlibs/fe…945b3eb5019935e2c7e.js
https://assets.adobedtm.com/7d22d70439461d29ed62de…cead05e17462ad161ac.js
https://assets.adobedtm.com/7d22d70439461d29ed62de…faee455cca08c786d12.js

Optimize CSS Delivery of the following:

https://www.fedex.com/etc.clientlibs/clientlibs/fe…67063c8d3ff337d862.css

priority - 26 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://fedex.com/
http://www.fedex.com/
https://www.fedex.com/global/choose-location.html

priority - 16 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.fedex.com/etc/services/getalerts.false…se-location.html.jsonp (expiration not specified)
https://www.fedex.com/etc/services/getapigconfigs.jsonp (expiration not specified)
https://www.googletagmanager.com/gtag/js?id=DC-4191263 (15 minutes)
https://maps.googleapis.com/maps/api/js?key=AIzaSy…PUT.gmInitAutoComplete (30 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…faee455cca08c786d12.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…21104ca42cc1f30a2f4.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…cead05e17462ad161ac.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…a3264746d3fce00d53a.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…84d64746d57b6001018.js (60 minutes)
https://assets.adobedtm.com/7d22d70439461d29ed62de…78f64746d6831001a2b.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…945b3eb5019935e2c7e.js (6.3 hours)
https://www.fedex.com/etc/clientlibs/fedex/common/…js4.14.0/lodash.min.js (9.4 hours)
https://www.fedex.com/content/dam/fedex-com/logos/logo.png (11.7 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/gr…6dfb06c17e789ad4dbd.js (11.7 hours)
https://www.fedex.com/content/dam/fedex-com/common/sprite-placeholder.png (13 hours)
https://www.fedex.com/etc/clientlibs/fedex/common/…fonts/Roboto-Light.ttf (14.3 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…675ce7b80af5ac35ce5.js (14.3 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…469fb833efab6642c04.js (16 hours)
https://www.fedex.com/etc/clientlibs/fedex/common/…/fonts/Roboto-Bold.ttf (20.4 hours)
https://www.fedex.com/etc/clientlibs/fedex/common/…nts/Roboto-Regular.ttf (22.7 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…rces/footer-sprite.png (22.8 hours)
https://www.fedex.com/etc.clientlibs/clientlibs/fe…67063c8d3ff337d862.css (22.8 hours)

priority - 4 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 42.3KiB (52% reduction).

Compressing https://www.fedex.com/etc.clientlibs/clientlibs/fe…rces/footer-sprite.png could save 20KiB (37% reduction).
Compressing https://www.fedex.com/content/dam/fedex-com/logos/logo.png could save 14.6KiB (83% reduction).
Compressing https://www.fedex.com/content/dam/fedex-com/common/sprite-placeholder.png could save 7.6KiB (99% reduction).

priority - 2 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 17.7KiB (29% reduction).

Minifying https://assets.adobedtm.com/7d22d70439461d29ed62de…21104ca42cc1f30a2f4.js could save 17.7KiB (29% reduction) after compression.

priority - 0 Reduce server response time

In our test, your server responded in 0.20 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1KiB (13% reduction).

Minifying https://www.fedex.com/global/choose-location.html could save 1KiB (13% reduction) after compression.

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 214B (46% reduction).

Compressing https://smetrics.fedex.com/b/ss/fedexglbl,fedexus/…=Y&bw=412&bh=732&AQE=1 could save 214B (46% reduction).

fedex.com Mobile Resources

Total Resources37
Number of Hosts13
Static Resources23
JavaScript Resources23
CSS Resources1

fedex.com Mobile Resource Breakdown

fedex.com mobile page usability

Last tested: 2019-08-26


Mobile Usability Good
96/100

fedex.com Mobile Usability Test Quick Summary


priority - 3 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 427 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <div class="fxg-col fxg-c…-mb20 col-sm-2"></div> falls outside the viewport.
The element <div class="fxg-col fxg-c…-mb20 col-sm-2">North America…s Virgin Gorda</div> falls outside the viewport.
The element <div class="fxg-col fxg-c…-mb20 col-sm-2">Europe Alb…can City State</div> falls outside the viewport.
The element <div class="fxg-col fxg-c…-mb20 col-sm-2">Ocean &amp; Pacifi…Emirates Yemen</div> falls outside the viewport.
The element <div class="fxg-col fxg-c…-mb20 col-sm-2">Africa Alg…ambia Zimbabwe</div> falls outside the viewport.

fedex.com Mobile Resources

Total Resources37
Number of Hosts13
Static Resources23
JavaScript Resources23
CSS Resources1

fedex.com Mobile Resource Breakdown

fedex.com similar domains

Similar domains:
www.fedex.com
www.fedex.net
www.fedex.org
www.fedex.info
www.fedex.biz
www.fedex.us
www.fedex.mobi
www.edex.com
www.fedex.com
www.cedex.com
www.fcedex.com
www.cfedex.com
www.dedex.com
www.fdedex.com
www.dfedex.com
www.redex.com
www.fredex.com
www.rfedex.com
www.tedex.com
www.ftedex.com
www.tfedex.com
www.gedex.com
www.fgedex.com
www.gfedex.com
www.vedex.com
www.fvedex.com
www.vfedex.com
www.fdex.com
www.fwdex.com
www.fewdex.com
www.fwedex.com
www.fsdex.com
www.fesdex.com
www.fsedex.com
www.fddex.com
www.feddex.com
www.frdex.com
www.ferdex.com
www.feex.com
www.fexex.com
www.fedxex.com
www.fexdex.com
www.feeex.com
www.fedeex.com
www.feedex.com
www.ferex.com
www.fedrex.com
www.fefex.com
www.fedfex.com
www.fefdex.com
www.fecex.com
www.fedcex.com
www.fecdex.com
www.fedx.com
www.fedwx.com
www.fedewx.com
www.fedwex.com
www.fedsx.com
www.fedesx.com
www.feddx.com
www.fededx.com
www.fedrx.com
www.federx.com
www.fede.com
www.fedez.com
www.fedexz.com
www.fedezx.com
www.fedes.com
www.fedexs.com
www.feded.com
www.fedexd.com
www.fedec.com
www.fedexc.com
www.fedecx.com
www.fedex.con

fedex.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


fedex.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.