Tools & Wizards About Us
win.niddk.nih.gov screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

win.niddk.nih.gov

Clearinghouses & Health Information Center - NIDDK

Page Load Speed

8.6 sec in total

First Response

219 ms

Resources Loaded

8 sec

Page Rendered

378 ms

win.niddk.nih.gov screenshot

About Website

Click here to check amazing Win NIDDK Nih content for China. Otherwise, check out these important facts you probably never knew about win.niddk.nih.gov

Get health information in English and Spanish on NIDDK-related diseases and conditions from the NIDDK Clearinghouses, and learn about past education programs.

Visit win.niddk.nih.gov

Key Findings

We analyzed Win.niddk.nih.gov page load time and found that the first response time was 219 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

win.niddk.nih.gov performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

information-clearinghouses

219 ms

niddk-web.css

42 ms

social-share.js

509 ms

jquery-3.6.0.min.js

508 ms

blankshield.min.js

505 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Win.niddk.nih.gov, 9% (3 requests) were made to Google-analytics.com and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Niddk.nih.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.6 kB (39%)

Content Size

111.0 kB

After Optimization

67.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Win.niddk.nih.gov main page is 111.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. HTML takes 53.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 43.5 kB

  • Original 53.9 kB
  • After minification 42.5 kB
  • After compression 10.4 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 11.4 kB, which is 21% 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 43.5 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 29.2 kB
  • After minification 29.2 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. Win NIDDK Nih images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 123 B

  • Original 27.8 kB
  • After minification 27.8 kB
  • After compression 27.7 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 16 (67%)

Requests Now

24

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

information-clearinghouses

information-clearinghouses

219 ms

niddk-web.css

niddk-web.css

42 ms

social-share.js

social-share.js

509 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

508 ms

blankshield.min.js

blankshield.min.js

505 ms

slick.min.js

slick.min.js

527 ms

jquery.scrolltabs.min.js

jquery.scrolltabs.min.js

531 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

531 ms

tablesaw.jquery.min.js

tablesaw.jquery.min.js

524 ms

niddk-main.js

niddk-main.js

517 ms

gtm.js

gtm.js

683 ms

information-clearinghouses

information-clearinghouses

480 ms

site-logo-full.svg

site-logo-full.svg

457 ms

site-logo-abbrev.svg

site-logo-abbrev.svg

465 ms

hm-banner.jpg

hm-banner.jpg

697 ms

open-sans-v29-latin-regular.woff

open-sans-v29-latin-regular.woff

390 ms

open-sans-v29-latin-600.woff

open-sans-v29-latin-600.woff

387 ms

open-sans-v29-latin-700.woff

open-sans-v29-latin-700.woff

486 ms

montserrat-v24-latin-regular.woff

montserrat-v24-latin-regular.woff

485 ms

montserrat-v24-latin-700.woff

montserrat-v24-latin-700.woff

485 ms

dki.ttf

dki.ttf

288 ms

merriweather-v30-latin-regular.woff

merriweather-v30-latin-regular.woff

283 ms

merriweather-v30-latin-300.woff

merriweather-v30-latin-300.woff

288 ms

merriweather-v30-latin-700.woff

merriweather-v30-latin-700.woff

284 ms

VisitorIdentification.js

VisitorIdentification.js

110 ms

js

js

119 ms

analytics.js

analytics.js

998 ms

Universal-Federated-Analytics-Min.js

Universal-Federated-Analytics-Min.js

1218 ms

slick.min.css

slick.min.css

976 ms

collect

collect

111 ms

scrolltabs.min.css

scrolltabs.min.css

101 ms

collect

collect

233 ms

magnific-popup.min.css

magnific-popup.min.css

1260 ms

tablesaw.min.css

tablesaw.min.css

931 ms

Accessibility Review

win.niddk.nih.gov accessibility score

97

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

win.niddk.nih.gov 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

Page has valid source maps

SEO Factors

win.niddk.nih.gov SEO score

99

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

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 Win.niddk.nih.gov 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 Win.niddk.nih.gov 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

win.niddk.nih.gov

Open Graph data is detected on the main page of Win NIDDK Nih. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: