Tools & Wizards About Us
researchers.mgh.harvard.edu screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

researchers.mgh.harvard.edu

Find A Researcher at Massachusetts General Hospital

Page Load Speed

4.3 sec in total

First Response

170 ms

Resources Loaded

3.6 sec

Page Rendered

487 ms

researchers.mgh.harvard.edu screenshot

About Website

Visit researchers.mgh.harvard.edu now to see the best up-to-date Researcher S Mgh Harvard content for United States and also check out these interesting facts you probably never knew about researchers.mgh.harvard.edu

Mass General is home to the largest hospital-based biomedical research program in the United States. Search this directory by name or keyword to find investigators in your area of interest.

Visit researchers.mgh.harvard.edu

Key Findings

We analyzed Researchers.mgh.harvard.edu page load time and found that the first response time was 170 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

researchers.mgh.harvard.edu performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.245

51/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

researchers.mgh.harvard.edu

170 ms

researchers.mgh.harvard.edu

2100 ms

jquery-1.10.2.js

25 ms

jquery-ui.js

44 ms

bootstrap.js

76 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 87% of them (62 requests) were addressed to the original Researchers.mgh.harvard.edu, 6% (4 requests) were made to Code.jquery.com and 4% (3 requests) were made to Massgeneral.org. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Researchers.mgh.harvard.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 975.1 kB (77%)

Content Size

1.3 MB

After Optimization

287.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Researchers.mgh.harvard.edu main page is 1.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. 70% of websites need less resources to load. Javascripts take 596.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 168.9 kB

  • Original 190.4 kB
  • After minification 163.9 kB
  • After compression 21.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. This page needs HTML code to be minified as it can gain 26.5 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 168.9 kB or 89% of the original size.

Image Optimization

-26%

Potential reduce by 7.9 kB

  • Original 30.5 kB
  • After minification 22.5 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. Obviously, Researcher S Mgh Harvard needs image optimization as it can save up to 7.9 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 405.0 kB

  • Original 596.1 kB
  • After minification 574.3 kB
  • After compression 191.1 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 405.0 kB or 68% of the original size.

CSS Optimization

-88%

Potential reduce by 393.3 kB

  • Original 445.5 kB
  • After minification 350.4 kB
  • After compression 52.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. Researchers.mgh.harvard.edu needs all CSS files to be minified and compressed as it can save up to 393.3 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (74%)

Requests Now

31

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

researchers.mgh.harvard.edu

researchers.mgh.harvard.edu

170 ms

researchers.mgh.harvard.edu

researchers.mgh.harvard.edu

2100 ms

jquery-1.10.2.js

jquery-1.10.2.js

25 ms

jquery-ui.js

jquery-ui.js

44 ms

bootstrap.js

bootstrap.js

76 ms

jquery-ui.css

jquery-ui.css

82 ms

grid.css

grid.css

152 ms

main.css

main.css

201 ms

main.min.js

main.min.js

192 ms

matomo.js

matomo.js

279 ms

fontloader.min.js

fontloader.min.js

17 ms

logo-mgh--cmyk.svg

logo-mgh--cmyk.svg

140 ms

ajax-loader.gif

ajax-loader.gif

56 ms

thumbnail

thumbnail

57 ms

default-profile.png

default-profile.png

58 ms

thumbnail

thumbnail

67 ms

thumbnail

thumbnail

95 ms

thumbnail

thumbnail

95 ms

thumbnail

thumbnail

95 ms

river-shield-400x225.jpg

river-shield-400x225.jpg

127 ms

res-inno-megamenu400x225.jpg

res-inno-megamenu400x225.jpg

126 ms

thumbnail

thumbnail

15 ms

thumbnail

thumbnail

30 ms

thumbnail

thumbnail

62 ms

thumbnail

thumbnail

60 ms

thumbnail

thumbnail

170 ms

thumbnail

thumbnail

36 ms

thumbnail

thumbnail

36 ms

thumbnail

thumbnail

35 ms

thumbnail

thumbnail

137 ms

thumbnail

thumbnail

139 ms

thumbnail

thumbnail

137 ms

thumbnail

thumbnail

135 ms

spectral-regular.woff

spectral-regular.woff

278 ms

spectral-medium.woff

spectral-medium.woff

277 ms

spectral-light.woff

spectral-light.woff

279 ms

spectral-extralight.woff

spectral-extralight.woff

278 ms

spectral-semibold.woff

spectral-semibold.woff

282 ms

spectral-bold.woff

spectral-bold.woff

285 ms

spectral-extrabold.woff

spectral-extrabold.woff

278 ms

neue-helvetica-roman.woff

neue-helvetica-roman.woff

277 ms

neue-helvetica-medium.woff

neue-helvetica-medium.woff

279 ms

neue-helvetica-light.woff

neue-helvetica-light.woff

280 ms

neue-helvetica-thin.woff

neue-helvetica-thin.woff

279 ms

neue-helvetica-bold.woff

neue-helvetica-bold.woff

280 ms

matomo.php

matomo.php

914 ms

0.bundle.js

0.bundle.js

212 ms

1.bundle.js

1.bundle.js

212 ms

3.bundle.js

3.bundle.js

212 ms

35.bundle.js

35.bundle.js

212 ms

2.bundle.js

2.bundle.js

213 ms

22.bundle.js

22.bundle.js

213 ms

29.bundle.js

29.bundle.js

214 ms

4.bundle.js

4.bundle.js

213 ms

25.bundle.js

25.bundle.js

214 ms

28.bundle.js

28.bundle.js

215 ms

21.bundle.js

21.bundle.js

214 ms

27.bundle.js

27.bundle.js

215 ms

12.bundle.js

12.bundle.js

215 ms

5.bundle.js

5.bundle.js

214 ms

9.bundle.js

9.bundle.js

215 ms

17.bundle.js

17.bundle.js

214 ms

16.bundle.js

16.bundle.js

215 ms

13.bundle.js

13.bundle.js

214 ms

ui-bg_inset-hard_100_fcfdfd_1x100.png

ui-bg_inset-hard_100_fcfdfd_1x100.png

128 ms

mgh-icons.woff

mgh-icons.woff

27 ms

neue-helvetica-light-italic.woff

neue-helvetica-light-italic.woff

27 ms

neue-helvetica-thin-italic.woff

neue-helvetica-thin-italic.woff

101 ms

neue-helvetica-italic.woff

neue-helvetica-italic.woff

101 ms

neue-helvetica-medium-italic.woff

neue-helvetica-medium-italic.woff

101 ms

neue-helvetica-bold-italic.woff

neue-helvetica-bold-italic.woff

100 ms

Accessibility Review

researchers.mgh.harvard.edu accessibility score

70

Accessibility Issues

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.

Impact

Issue

High

[aria-*] attributes are not valid or misspelled

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

researchers.mgh.harvard.edu best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

researchers.mgh.harvard.edu SEO score

77

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

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Researchers.mgh.harvard.edu 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 Researchers.mgh.harvard.edu 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

researchers.mgh.harvard.edu

Open Graph data is detected on the main page of Researcher S Mgh Harvard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: