MCKINSEY.COM McKinsey & Company | Global management consulting


mckinsey.com website information.

mckinsey.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 mckinsey.com domain:

  • a9-64.akam.net
  • a22-66.akam.net
  • a12-64.akam.net
  • a18-65.akam.net
  • a3-67.akam.net
  • a1-89.akam.net

and probably website mckinsey.com is hosted by AKAMAI-AS - Akamai Technologies, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AKAMAI-AS - Akamai Technologies, Inc., US hosting company.

According to Alexa traffic rank the highest website mckinsey.com position was 249 (in the world). The lowest Alexa rank position was 290. Now website mckinsey.com ranked in Alexa database as number 253 (in the world).

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

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

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

Weekly Rank Report

DateRankChange
Oct-31-2024 253-2
Oct-30-2024 2512
Oct-29-2024 2530
Oct-28-2024 2531
Oct-27-2024 254-1
Oct-26-2024 2530
Oct-25-2024 2530

Advertisement

mckinsey.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.



mckinsey.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: MCKINSEY.COM
Registry Domain ID: 1926232_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.corporatedomains.com
Registrar URL: http://cscdbs.com
Updated Date: 2024-05-19T05:05:22Z
Creation Date: 1990-05-22T04:00:00Z
Registry Expiry Date: 2026-05-23T04:00:00Z
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: A1-89.AKAM.NET
Name Server: A12-64.AKAM.NET
Name Server: A18-65.AKAM.NET
Name Server: A22-66.AKAM.NET
Name Server: A3-67.AKAM.NET
Name Server: A9-64.AKAM.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-09-09T12:35:21Z

mckinsey.com server information

Servers Location

IP Address
157.191.4.253
Region
New York
City
New York City

mckinsey.com desktop page speed rank

Last tested: 2019-12-02


Desktop Speed Bad
63/100

mckinsey.com Desktop Speed Test Quick Summary


priority - 30 Optimize images

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

Optimize the following images to reduce their size by 293.2KiB (31% reduction).

Compressing https://www.mckinsey.com/~/media/McKinsey/About%20…mit-hero-1536x864.ashx could save 114.9KiB (44% reduction).
Compressing https://www.mckinsey.com/~/media/McKinsey/About%20…ne-pooja-1536x864.ashx could save 114.7KiB (46% reduction).
Compressing https://www.mckinsey.com/~/media/McKinsey/Home%20p…40_bright.ashx?mw=1536 could save 32KiB (15% reduction).
Compressing https://www.mckinsey.com/~/media/McKinsey/About%20…-hero-sm-1536x864.ashx could save 31.6KiB (15% reduction).

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

Your page has 2 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://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…a1d1bc70a3454e64e75.js
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…2d078e046d375c196e8.js

Optimize CSS Delivery of the following:

https://www.mckinsey.com/redesign/resources/css/styles-31feb0.css

priority - 7 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://static.hotjar.com/c/hotjar-416998.js?sv=6 (60 seconds)
https://cdn.dynamicyield.com/api/8768498/api_dynamic.js (5 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-819789980 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/115836…8389?v=2.9.14&r=stable (20 minutes)
https://connect.facebook.net/signals/config/124437…4419?v=2.9.14&r=stable (20 minutes)
https://connect.facebook.net/signals/config/422555…8981?v=2.9.14&r=stable (20 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…2d078e046d375c196e8.js (60 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…c29390226b09e58fc23.js (60 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…a1d1bc70a3454e64e75.js (60 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…99064746d352400401f.js (60 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…f2464746d762f00f0b3.js (60 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…5ec64746d24d50011d4.js (60 minutes)
https://cdn.dynamicyield.com/api/8768498/api_static.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)

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://mckinsey.com/
http://www.mckinsey.com/
https://www.mckinsey.com/

priority - 2 Reduce server response time

In our test, your server responded in 0.40 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 - 1 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 9.1KiB (19% reduction).

Minifying https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…c29390226b09e58fc23.js could save 9.1KiB (19% 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 2.6KiB (16% reduction).

Minifying https://www.mckinsey.com/ could save 2.6KiB (16% reduction) after compression.

mckinsey.com Desktop Resources

Total Resources75
Number of Hosts27
Static Resources28
JavaScript Resources35
CSS Resources1

mckinsey.com Desktop Resource Breakdown

mckinsey.com mobile page speed rank

Last tested: 2018-10-07


Mobile Speed Bad
49/100

mckinsey.com Mobile Speed Test Quick Summary


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

Your page has 3 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://cdn.optimizely.com/js/537950227.js
https://www.mckinsey.com/redesign/resources/js/shared-13ae8d.js
https://www.mckinsey.com/redesign/resources/js/app-13ae8d.js

Optimize CSS Delivery of the following:

https://www.mckinsey.com/redesign/resources/css/styles-10ec7f.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://mckinsey.com/
http://www.mckinsey.com/
https://www.mckinsey.com/

priority - 15 Reduce server response time

In our test, your server responded in 0.82 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 - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

None of the final above-the-fold content could be rendered even with the full HTML response.

priority - 5 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://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/124437…4419?v=2.8.30&r=stable (20 minutes)
https://connect.facebook.net/signals/config/422555…8981?v=2.8.30&r=stable (20 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…c29390226b09e58fc23.js (60 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…a1d1bc70a3454e64e75.js (60 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…99064746d352400401f.js (60 minutes)
https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…f2464746d762f00f0b3.js (60 minutes)
https://snap.licdn.com/li.lms-analytics/insight.min.js (5.4 hours)

priority - 3 Optimize images

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

Optimize the following images to reduce their size by 31.1KiB (41% reduction).

Compressing https://www.mckinsey.com/~/media/Images/Global/Mod….ashx?mw=480&car=42:25 could save 27.6KiB (67% reduction).
Compressing https://www.mckinsey.com/~/media/McKinsey/Home%20p…9&cpx=Right&cpy=Center could save 3.5KiB (11% reduction).

priority - 1 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 9KiB (20% reduction).

Minifying https://assets.adobedtm.com/31d0cc0e4278bee6dc9b35…c29390226b09e58fc23.js could save 9KiB (20% 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 2.7KiB (17% reduction).

Minifying https://www.mckinsey.com/ could save 2.7KiB (17% reduction) after compression.

mckinsey.com Mobile Resources

Total Resources39
Number of Hosts15
Static Resources13
JavaScript Resources16
CSS Resources1

mckinsey.com Mobile Resource Breakdown

mckinsey.com mobile page usability

Last tested: 2018-10-07


Mobile Usability Good
99/100

mckinsey.com Mobile Usability Test Quick Summary


priority - 0 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="#0" class="skip-main">Skip to main content</a> is close to 1 other tap targets.

The tap target <button type="button" class="menu-toggle">Toggle Menu</button> is close to 1 other tap targets.

The tap target <form id="subscribeForm" class="form-content subscribe-form">Email address</form> and 1 others are close to other tap targets.

mckinsey.com similar domains

Similar domains:
www.mckinsey.com
www.mckinsey.net
www.mckinsey.org
www.mckinsey.info
www.mckinsey.biz
www.mckinsey.us
www.mckinsey.mobi
www.ckinsey.com
www.mckinsey.com
www.nckinsey.com
www.mnckinsey.com
www.nmckinsey.com
www.jckinsey.com
www.mjckinsey.com
www.jmckinsey.com
www.kckinsey.com
www.mkckinsey.com
www.kmckinsey.com
www.mkinsey.com
www.mxkinsey.com
www.mcxkinsey.com
www.mxckinsey.com
www.mdkinsey.com
www.mcdkinsey.com
www.mdckinsey.com
www.mfkinsey.com
www.mcfkinsey.com
www.mfckinsey.com
www.mvkinsey.com
www.mcvkinsey.com
www.mvckinsey.com
www.mcinsey.com
www.mcjinsey.com
www.mckjinsey.com
www.mcjkinsey.com
www.mciinsey.com
www.mckiinsey.com
www.mcikinsey.com
www.mcminsey.com
www.mckminsey.com
www.mcmkinsey.com
www.mclinsey.com
www.mcklinsey.com
www.mclkinsey.com
www.mcoinsey.com
www.mckoinsey.com
www.mcokinsey.com
www.mcknsey.com
www.mckunsey.com
www.mckiunsey.com
www.mckuinsey.com
www.mckjnsey.com
www.mckijnsey.com
www.mckknsey.com
www.mckiknsey.com
www.mckkinsey.com
www.mckonsey.com
www.mckionsey.com
www.mckisey.com
www.mckibsey.com
www.mckinbsey.com
www.mckibnsey.com
www.mckihsey.com
www.mckinhsey.com
www.mckihnsey.com
www.mckijsey.com
www.mckinjsey.com
www.mckimsey.com
www.mckinmsey.com
www.mckimnsey.com
www.mckiney.com
www.mckinwey.com
www.mckinswey.com
www.mckinwsey.com
www.mckineey.com
www.mckinseey.com
www.mckinesey.com
www.mckindey.com
www.mckinsdey.com
www.mckindsey.com
www.mckinzey.com
www.mckinszey.com
www.mckinzsey.com
www.mckinxey.com
www.mckinsxey.com
www.mckinxsey.com
www.mckinaey.com
www.mckinsaey.com
www.mckinasey.com
www.mckinsy.com
www.mckinswy.com
www.mckinsewy.com
www.mckinssy.com
www.mckinsesy.com
www.mckinssey.com
www.mckinsdy.com
www.mckinsedy.com
www.mckinsry.com
www.mckinsery.com
www.mckinsrey.com
www.mckinse.com
www.mckinset.com
www.mckinseyt.com
www.mckinsety.com
www.mckinseg.com
www.mckinseyg.com
www.mckinsegy.com
www.mckinseh.com
www.mckinseyh.com
www.mckinsehy.com
www.mckinseu.com
www.mckinseyu.com
www.mckinseuy.com
www.mckinsey.con

mckinsey.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.


mckinsey.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.