Hbr.org Harvard Business Review - Ideas and Advice for Leaders
Find new ideas and classic advice on strategy, innovation and leadership, for global leaders from the world's best business and management experts.
hbr.org Desktop Performance
43/100
These metrics represent real-world Chrome users experience viewing hbr.org web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Cumulative Layout Shift
First Input Delay
First Contentful Paint
Largest Contentful Paint
Metrics
Total Blocking Time23/100 570 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint25/100 3.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Speed Index47/100 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First Contentful Paint59/100 1.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive65/100 3.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Cumulative Layout Shift97/100 0.065
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (17)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Preload key requests
Potential savings of 1,490 ms
1,490 ms
Eliminate render-blocking resources
Potential savings of 940 ms
943 ms
Remove unused JavaScript
Potential savings of 858 KiB
840 ms
Serve images in next-gen formats
Potential savings of 629 KiB
440 ms
Remove unused CSS
Potential savings of 75 KiB
120 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
49 resources found
Avoid `document.write()`
Ensure text remains visible during webfont load
Minimize main-thread work
4.1 s
Avoid enormous network payloads
Total size was 3,587 KiB
Avoid an excessive DOM size
1,109 elements
Reduce JavaScript execution time
1.8 s
Largest Contentful Paint element
1 element found
Avoid long main-thread tasks
9 long tasks found
Keep request counts low and transfer sizes small
117 requests • 3,587 KiB
Avoid chaining critical requests
16 chains found
Avoid large layout shifts
5 elements found
Passed Audits (12)
Avoid multiple page redirects
Potential savings of 190 ms
Minify CSS
Defer offscreen images
Use video formats for animated content
Minimize third-party usage
Third-party code blocked the main thread for 230 ms
Preconnect to required origins
Properly size images
Potential savings of 121 KiB
Uses passive listeners to improve scrolling performance
Minify JavaScript
Efficiently encode images
Potential savings of 29 KiB
Enable text compression
Potential savings of 8 KiB
Initial server response time was short
Root document took 190 ms
hbr.org Desktop SEO
100/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Passed Audits (11)
Image elements have `[alt]` attributes
Links have descriptive text
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a meta description
Page isn’t blocked from indexing
Page has successful HTTP status code
Document has a `<title>` element
Document avoids plugins
Document has a valid `hreflang`
robots.txt is valid
Links are crawlable
hbr.org Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of hbr.org page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Does not use HTTPS
1 insecure request found
Links to cross-origin destinations are unsafe
General
Browser errors were logged to the console
Passed Audits (10)
Serves images with appropriate resolution
Avoids deprecated APIs
Avoids requesting the notification permission on page load
Avoids Application Cache
Allows users to paste into password fields
Avoids requesting the geolocation permission on page load
Page has the HTML doctype
Displays images with correct aspect ratio
Properly defines charset
Detected JavaScript libraries
hbr.org Desktop Progressive Web App
19/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (10)
PWA Optimized
Does not set a theme color for the address bar.
Is not configured for a custom splash screen
Does not provide a valid `apple-touch-icon`
Manifest doesn't have a maskable icon
Fast and reliable
`start_url` does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 20.4 s
Current page does not respond with a 200 when offline
Installable
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
Does not use HTTPS
1 insecure request found
Passed Audits (3)
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
hbr.org Desktop Accessibility
79/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (6)
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.
`[aria-*]` attributes do not have valid values
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (16)
Image elements have `[alt]` attributes
The page contains a heading, skip link, or landmark region
`[role]` values are valid
`[aria-*]` attributes match their roles
Buttons have an accessible name
`[id]` attributes on active, focusable elements are unique
`<frame>` or `<iframe>` elements have a title
`[aria-hidden="true"]` is not present on the document `<body>`
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s have all required `[aria-*]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[aria-*]` attributes are valid and not misspelled
`[role]`s are contained by their required parent element
Desktop Speed
49/100
These checks analyze the performance of hbr.org on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (5)
Optimize images
Leverage browser caching
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Minify HTML
Minify JavaScript
Passed Audits (5)
Avoid landing page redirects
Enable compression
Reduce server response time
Minify CSS
Prioritize visible content
www.hbr.com
www.hbr.net
www.hbr.org
www.hbr.info
www.hbr.biz
www.hbr.us
www.hbr.mobi
www.br.org
www.hbr.org
www.bbr.org
www.hbbr.org
www.bhbr.org
www.gbr.org
www.hgbr.org
www.ghbr.org
www.ybr.org
www.hybr.org
www.yhbr.org
www.ubr.org
www.hubr.org
www.uhbr.org
www.jbr.org
www.hjbr.org
www.jhbr.org
www.nbr.org
www.hnbr.org
www.nhbr.org
www.hr.org
www.hvr.org
www.hbvr.org
www.hvbr.org
www.hgr.org
www.hbgr.org
www.hhr.org
www.hbhr.org
www.hhbr.org
www.hnr.org
www.hbnr.org
www.hb.org
www.hbe.org
www.hbre.org
www.hber.org
www.hbd.org
www.hbrd.org
www.hbdr.org
www.hbf.org
www.hbrf.org
www.hbfr.org
www.hbt.org
www.hbrt.org
www.hbtr.org
www.hbr.net
www.hbr.org
www.hbr.info
www.hbr.biz
www.hbr.us
www.hbr.mobi
www.br.org
www.hbr.org
www.bbr.org
www.hbbr.org
www.bhbr.org
www.gbr.org
www.hgbr.org
www.ghbr.org
www.ybr.org
www.hybr.org
www.yhbr.org
www.ubr.org
www.hubr.org
www.uhbr.org
www.jbr.org
www.hjbr.org
www.jhbr.org
www.nbr.org
www.hnbr.org
www.nhbr.org
www.hr.org
www.hvr.org
www.hbvr.org
www.hvbr.org
www.hgr.org
www.hbgr.org
www.hhr.org
www.hbhr.org
www.hhbr.org
www.hnr.org
www.hbnr.org
www.hb.org
www.hbe.org
www.hbre.org
www.hber.org
www.hbd.org
www.hbrd.org
www.hbdr.org
www.hbf.org
www.hbrf.org
www.hbfr.org
www.hbt.org
www.hbrt.org
www.hbtr.org