ihmc.us - IHMC

Ihmc.us Site Title

IHMC

Ihmc.us Meta Description

The Institute for Human & Machine Cognition (IHMC) pioneers technologies aimed at leveraging and extending human capabilities.

Ihmc.us Test Results

Ihmc.us Mobile Performance: 45/100

Quick overview:

Opportunities

These suggestions can help your page load faster. They don't directly affect the Performance score.

Eliminate render-blocking resources. Potential savings of 2,800 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Avoid multiple page redirects. Potential savings of 1,110 ms

Redirects introduce additional delays before the page can be loaded. Learn more.

Serve images in next-gen formats. Potential savings of 113 KiB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Remove unused CSS. Potential savings of 40 KiB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Remove unused JavaScript. Potential savings of 62 KiB

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Minify JavaScript. Potential savings of 5 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Reduce initial server response time. Root document took 630 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more.

Diagnostics

More information about the performance of your application. These numbers don't directly affect the Performance score.

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.

Serve static assets with an efficient cache policy

6 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more.

Minimize main-thread work

2.4 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

Avoid an excessive DOM size

924 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

Keep request counts low and transfer sizes small

56 requests • 1,124 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Avoid chaining critical requests

22 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Avoid long main-thread tasks

9 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Largest Contentful Paint element

1 element found

This is the largest contentful element painted within the viewport. Learn More

Ihmc.us Mobile SEO: 85/100

Quick overview:

Content Best Practices

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

Image elements do not have `[alt]` attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Links do not have descriptive text

3 links found

Descriptive link text helps search engines understand your content. Learn more.

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.

Tap targets are not sized appropriately

93% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Ihmc.us Mobile Best Practices: 62/100

Quick overview:

Trust and Safety

Includes front-end JavaScript libraries with known security vulnerabilities

9 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.

Links to cross-origin destinations are unsafe

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.

Does not use HTTPS

1 insecure request 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 servedover 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.

User Experience

Serves images with low resolution

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.

Displays images with incorrect aspect ratio

Image display dimensions should match natural aspect ratio. Learn more.

Ihmc.us Mobile Progressive Web App: 46/100

Quick overview:

PWA Optimized

Is not configured for a custom splash screen

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.

Content is not sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 744px does not match the window size of 360px.

Does not set a theme color for the address bar.

The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

Manifest doesn't have a maskable icon

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched

Installable

Does not register a service worker that controls page and `start_url`

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.

Web app manifest does not meet the installability requirements

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.

Does not use HTTPS

1 insecure request found

Fast and reliable

`start_url` does not respond with a 200 when offline

A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.

Current page does not respond with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

Ihmc.us Mobile Accessibility: 65/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.

`[role]`s are not contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.

`[aria-*]` attributes do not have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.

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.

Buttons do not have an accessible name

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.

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 more.

Image elements do not have `[alt]` attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Form elements do not have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

Navigation

These are opportunities to improve keyboard navigation in your application.

Heading elements are not in a sequentially-descending order

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.

Contrast

These are opportunities to improve the legibility of your content.

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

Low-contrast text is difficult or impossible for many users to read. Learn more.

Similar tests

www.ihmc.com
www.ihmc.net
www.ihmc.org
www.ihmc.info
www.ihmc.biz
www.ihmc.us
www.ihmc.mobi
www.hmc.us
www.ihmc.us
www.uhmc.us
www.iuhmc.us
www.uihmc.us
www.jhmc.us
www.ijhmc.us
www.jihmc.us
www.khmc.us
www.ikhmc.us
www.kihmc.us
www.ohmc.us
www.iohmc.us
www.oihmc.us
www.imc.us
www.ibmc.us
www.ihbmc.us
www.ibhmc.us
www.igmc.us
www.ihgmc.us
www.ighmc.us
www.iymc.us
www.ihymc.us
www.iyhmc.us
www.iumc.us
www.ihumc.us
www.ijmc.us
www.ihjmc.us
www.inmc.us
www.ihnmc.us
www.inhmc.us
www.ihc.us
www.ihnc.us
www.ihmnc.us
www.ihjc.us
www.ihmjc.us
www.ihkc.us
www.ihmkc.us
www.ihkmc.us
www.ihm.us
www.ihmx.us
www.ihmcx.us
www.ihmxc.us
www.ihmd.us
www.ihmcd.us
www.ihmdc.us
www.ihmf.us
www.ihmcf.us
www.ihmfc.us
www.ihmv.us
www.ihmcv.us
www.ihmvc.us