Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

assets.mckinsey.com

Global management consulting | McKinsey & Company

Page Load Speed

1.8 sec in total

First Response

185 ms

Resources Loaded

1.2 sec

Page Rendered

343 ms

About Website

Welcome to assets.mckinsey.com homepage info - get ready to check Assets Mc Kinsey best content for United States right away, or after learning these important things about assets.mckinsey.com

McKinsey partners with leaders on strategy, innovating to net zero, leading with tech, and building capabilities for a sustainable, inclusive, growing future.

Visit assets.mckinsey.com

Key Findings

We analyzed Assets.mckinsey.com page load time and found that the first response time was 185 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

assets.mckinsey.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

www.mckinsey.com

185 ms

styles-rc.css

168 ms

0c302eb292dcb413.css

434 ms

ad8a85ef00ccfadb.css

83 ms

polyfills-5cd94c89d3acac5f.js

94 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Assets.mckinsey.com, 10% (2 requests) were made to and 5% (1 request) were made to S.go-mpulse.net. The less responsive or slowest element that took the longest time to load (434 ms) relates to the external source Mckinsey.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (64%)

Content Size

2.3 MB

After Optimization

809.4 kB

In fact, the total size of Assets.mckinsey.com main page is 2.3 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. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 77.9 kB

  • Original 105.6 kB
  • After minification 105.6 kB
  • After compression 27.6 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 77.9 kB or 74% of the original size.

JavaScript Optimization

-67%

Potential reduce by 1.4 MB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 663.4 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 1.4 MB or 67% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 118.3 kB
  • After minification 118.3 kB
  • After compression 118.3 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. Assets.mckinsey.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (78%)

Requests Now

18

After Optimization

4

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

Accessibility Review

assets.mckinsey.com accessibility score

100

Accessibility Issues

Best Practices

assets.mckinsey.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

assets.mckinsey.com SEO score

100

Search Engine Optimization Advices

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 Assets.mckinsey.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 Assets.mckinsey.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 data is detected on the main page of Assets Mc Kinsey. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: