Whcenter.org Site Title
MedStar Washington Hospital Center | 20010 | MedStar Health
Whcenter.org Meta Description
One of the top hospitals, MedStar Washington Hospital Center has been serving patients in D.C. Virginia and Maryland for over 50 years with research, education and care. Located at 110 Irving St. NW.
Whcenter.org Test Results
Whcenter.org Mobile Performance: 30/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint element
13,050 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 916 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 21 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Avoid multiple page redirects
Potential savings of 1,740 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused CSS
Potential savings of 185 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Avoid an excessive DOM size
1,114 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Properly size images
Potential savings of 335 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,110 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Minimize main-thread work
9.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Eliminate render-blocking resources
Potential savings of 1,750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce initial server response time
Root document took 1,040 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Reduce JavaScript execution time
4.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Serve images in next-gen formats
Potential savings of 214 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Enable text compression
Potential savings of 39 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Serve static assets with an efficient cache policy
63 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 3,374 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Defer offscreen images
Potential savings of 399 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Max Potential First Input Delay
830 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
21.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Whcenter.org Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
7 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Whcenter.org Mobile Best Practices: 31/100
Quick overview:
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Uses third-party cookies
3 cookies found
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Trust and Safety
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Requests the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
User Experience
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Whcenter.org Mobile Accessibility: 87/100
Quick overview:
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.
`button`, `link`, and `menuitem` elements do not have accessible names.
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Similar sites
Similar tests
www.whcenter.com
www.whcenter.net
www.whcenter.org
www.whcenter.info
www.whcenter.biz
www.whcenter.us
www.whcenter.mobi
www.hcenter.org
www.whcenter.org
www.qhcenter.org
www.wqhcenter.org
www.qwhcenter.org
www.ahcenter.org
www.wahcenter.org
www.awhcenter.org
www.shcenter.org
www.wshcenter.org
www.swhcenter.org
www.ehcenter.org
www.wehcenter.org
www.ewhcenter.org
www.wcenter.org
www.wbcenter.org
www.whbcenter.org
www.wbhcenter.org
www.wgcenter.org
www.whgcenter.org
www.wghcenter.org
www.wycenter.org
www.whycenter.org
www.wyhcenter.org
www.wucenter.org
www.whucenter.org
www.wuhcenter.org
www.wjcenter.org
www.whjcenter.org
www.wjhcenter.org
www.wncenter.org
www.whncenter.org
www.wnhcenter.org
www.whenter.org
www.whxenter.org
www.whcxenter.org
www.whxcenter.org
www.whdenter.org
www.whcdenter.org
www.whdcenter.org
www.whfenter.org
www.whcfenter.org
www.whfcenter.org
www.whventer.org
www.whcventer.org
www.whvcenter.org
www.whcnter.org
www.whcwnter.org
www.whcewnter.org
www.whcwenter.org
www.whcsnter.org
www.whcesnter.org
www.whcsenter.org
www.whcdnter.org
www.whcednter.org
www.whcrnter.org
www.whcernter.org
www.whcrenter.org
www.whceter.org
www.whcebter.org
www.whcenbter.org
www.whcebnter.org
www.whcehter.org
www.whcenhter.org
www.whcehnter.org
www.whcejter.org
www.whcenjter.org
www.whcejnter.org
www.whcemter.org
www.whcenmter.org
www.whcemnter.org
www.whcener.org
www.whcenrer.org
www.whcentrer.org
www.whcenrter.org
www.whcenfer.org
www.whcentfer.org
www.whcenfter.org
www.whcenger.org
www.whcentger.org
www.whcengter.org
www.whcenyer.org
www.whcentyer.org
www.whcenyter.org
www.whcentr.org
www.whcentwr.org
www.whcentewr.org
www.whcentwer.org
www.whcentsr.org
www.whcentesr.org
www.whcentser.org
www.whcentdr.org
www.whcentedr.org
www.whcentder.org
www.whcentrr.org
www.whcenterr.org
www.whcente.org
www.whcentee.org
www.whcentere.org
www.whcenteer.org
www.whcented.org
www.whcenterd.org
www.whcentef.org
www.whcenterf.org
www.whcentefr.org
www.whcentet.org
www.whcentert.org
www.whcentetr.org
www.whcenter.net
www.whcenter.org
www.whcenter.info
www.whcenter.biz
www.whcenter.us
www.whcenter.mobi
www.hcenter.org
www.whcenter.org
www.qhcenter.org
www.wqhcenter.org
www.qwhcenter.org
www.ahcenter.org
www.wahcenter.org
www.awhcenter.org
www.shcenter.org
www.wshcenter.org
www.swhcenter.org
www.ehcenter.org
www.wehcenter.org
www.ewhcenter.org
www.wcenter.org
www.wbcenter.org
www.whbcenter.org
www.wbhcenter.org
www.wgcenter.org
www.whgcenter.org
www.wghcenter.org
www.wycenter.org
www.whycenter.org
www.wyhcenter.org
www.wucenter.org
www.whucenter.org
www.wuhcenter.org
www.wjcenter.org
www.whjcenter.org
www.wjhcenter.org
www.wncenter.org
www.whncenter.org
www.wnhcenter.org
www.whenter.org
www.whxenter.org
www.whcxenter.org
www.whxcenter.org
www.whdenter.org
www.whcdenter.org
www.whdcenter.org
www.whfenter.org
www.whcfenter.org
www.whfcenter.org
www.whventer.org
www.whcventer.org
www.whvcenter.org
www.whcnter.org
www.whcwnter.org
www.whcewnter.org
www.whcwenter.org
www.whcsnter.org
www.whcesnter.org
www.whcsenter.org
www.whcdnter.org
www.whcednter.org
www.whcrnter.org
www.whcernter.org
www.whcrenter.org
www.whceter.org
www.whcebter.org
www.whcenbter.org
www.whcebnter.org
www.whcehter.org
www.whcenhter.org
www.whcehnter.org
www.whcejter.org
www.whcenjter.org
www.whcejnter.org
www.whcemter.org
www.whcenmter.org
www.whcemnter.org
www.whcener.org
www.whcenrer.org
www.whcentrer.org
www.whcenrter.org
www.whcenfer.org
www.whcentfer.org
www.whcenfter.org
www.whcenger.org
www.whcentger.org
www.whcengter.org
www.whcenyer.org
www.whcentyer.org
www.whcenyter.org
www.whcentr.org
www.whcentwr.org
www.whcentewr.org
www.whcentwer.org
www.whcentsr.org
www.whcentesr.org
www.whcentser.org
www.whcentdr.org
www.whcentedr.org
www.whcentder.org
www.whcentrr.org
www.whcenterr.org
www.whcente.org
www.whcentee.org
www.whcentere.org
www.whcenteer.org
www.whcented.org
www.whcenterd.org
www.whcentef.org
www.whcenterf.org
www.whcentefr.org
www.whcentet.org
www.whcentert.org
www.whcentetr.org