4.3 sec in total
155 ms
3.3 sec
810 ms
Visit understandingmymedicare.com now to see the best up-to-date Understanding My Medicare content and also check out these interesting facts you probably never knew about understandingmymedicare.com
Understanding My Medicare - Helping Seniors find a Medicare program that meets their needs. Local to Portland, Oregon.
Visit understandingmymedicare.comWe analyzed Understandingmymedicare.com page load time and found that the first response time was 155 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.
understandingmymedicare.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value4.6 s
36/100
25%
Value7.1 s
31/100
10%
Value450 ms
63/100
30%
Value0.034
100/100
15%
Value11.2 s
20/100
10%
155 ms
1195 ms
138 ms
202 ms
218 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 97% of them (57 requests) were addressed to the original Understandingmymedicare.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Understandingmymedicare.com.
Page size can be reduced by 163.2 kB (9%)
1.8 MB
1.6 MB
In fact, the total size of Understandingmymedicare.com main page is 1.8 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 89.5 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 89.5 kB or 82% of the original size.
Potential reduce by 64.1 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. Understanding My Medicare images are well optimized though.
Potential reduce by 180 B
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.
Potential reduce by 9.4 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. Understandingmymedicare.com needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 13% of the original size.
Number of requests can be reduced by 42 (84%)
50
8
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Understanding My Medicare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
understandingmymedicare.com
155 ms
www.understandingmymedicare.com
1195 ms
style.min.css
138 ms
theme.min.css
202 ms
header-footer.min.css
218 ms
frontend-lite.min.css
269 ms
post-19.css
220 ms
elementor-icons.min.css
201 ms
swiper.min.css
205 ms
frontend-lite.min.css
298 ms
global.css
329 ms
post-134.css
323 ms
post-47.css
328 ms
post-40.css
335 ms
css
25 ms
fontawesome.min.css
395 ms
solid.min.css
369 ms
regular.min.css
392 ms
brands.min.css
406 ms
jquery.min.js
468 ms
jquery-migrate.min.js
417 ms
widget-nav-menu.min.css
433 ms
widget-icon-box.min.css
414 ms
widget-carousel.min.css
495 ms
widget-call-to-action.min.css
497 ms
widget-icon-list.min.css
497 ms
animations.min.css
500 ms
hello-frontend.min.js
497 ms
jquery.smartmenus.min.js
498 ms
imagesloaded.min.js
498 ms
webpack-pro.runtime.min.js
548 ms
webpack.runtime.min.js
547 ms
frontend-modules.min.js
552 ms
wp-polyfill-inert.min.js
562 ms
regenerator-runtime.min.js
566 ms
wp-polyfill.min.js
640 ms
hooks.min.js
572 ms
i18n.min.js
573 ms
frontend.min.js
629 ms
waypoints.min.js
582 ms
core.min.js
518 ms
frontend.min.js
515 ms
elements-handlers.min.js
524 ms
underscore.min.js
552 ms
wp-util.min.js
557 ms
frontend.min.js
503 ms
Understanding-my-medicare-logo.gif
295 ms
vibrant-beauty-romantic-flora-nature-scaled.jpg
138 ms
font
77 ms
fa-brands-400.woff
297 ms
fa-solid-900.woff
392 ms
fa-regular-400.woff
344 ms
casual-senior-man-home-scaled.jpg
147 ms
Beth-Moffett2.jpg
275 ms
DSC_3463-scaled.jpg
551 ms
closeup-support-hands-scaled.jpg
573 ms
eicons.woff
449 ms
vibrant-beauty-romantic-flora-nature-scaled.jpg
507 ms
casual-senior-man-home-scaled.jpg
458 ms
understandingmymedicare.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
understandingmymedicare.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
understandingmymedicare.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Understandingmymedicare.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 Understandingmymedicare.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.
understandingmymedicare.com
Open Graph data is detected on the main page of Understanding My Medicare. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: