Ibm.com Site Title
IBM - United States
Ibm.com Meta Description
For more than a century IBM has been dedicated to every client's success and to creating innovations that matter for the world
Ibm.com Test Results
Ibm.com Mobile Performance: 15/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Defer offscreen images. Potential savings of 1,231 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Serve images in next-gen formats. Potential savings of 946 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.
Avoid multiple page redirects. Potential savings of 1,890 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused JavaScript. Potential savings of 237 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Minify JavaScript. Potential savings of 46 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Enable text compression. Potential savings of 55 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Remove unused CSS. Potential savings of 42 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
18.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 5,980 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 more.
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
93 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
10.8 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
1,712 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoid enormous network payloads
Total size was 3,643 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
User Timing marks and measures
85 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
2 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
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
180 requests • 3,643 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Ibm.com Mobile SEO: 99/100
Quick overview:
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
92% 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.
Ibm.com Mobile Best Practices: 69/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
3 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
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Ibm.com Mobile Progressive Web App: 21/100
Quick overview:
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.
Page load is not fast enough on mobile networks
Interactive at 28.4 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
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.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
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
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 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.
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.
Ibm.com Mobile Accessibility: 70/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.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. 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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like 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.
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.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
`[id]` attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
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.
Similar sites
Similar tests
www.ibm.com
www.ibm.net
www.ibm.org
www.ibm.info
www.ibm.biz
www.ibm.us
www.ibm.mobi
www.bm.com
www.ibm.com
www.ubm.com
www.iubm.com
www.uibm.com
www.jbm.com
www.ijbm.com
www.jibm.com
www.kbm.com
www.ikbm.com
www.kibm.com
www.obm.com
www.iobm.com
www.oibm.com
www.im.com
www.ivm.com
www.ibvm.com
www.ivbm.com
www.igm.com
www.ibgm.com
www.igbm.com
www.ihm.com
www.ibhm.com
www.ihbm.com
www.inm.com
www.ibnm.com
www.inbm.com
www.ib.com
www.ibn.com
www.ibmn.com
www.ibj.com
www.ibmj.com
www.ibjm.com
www.ibk.com
www.ibmk.com
www.ibkm.com
www.ibm.con
www.ibm.net
www.ibm.org
www.ibm.info
www.ibm.biz
www.ibm.us
www.ibm.mobi
www.bm.com
www.ibm.com
www.ubm.com
www.iubm.com
www.uibm.com
www.jbm.com
www.ijbm.com
www.jibm.com
www.kbm.com
www.ikbm.com
www.kibm.com
www.obm.com
www.iobm.com
www.oibm.com
www.im.com
www.ivm.com
www.ibvm.com
www.ivbm.com
www.igm.com
www.ibgm.com
www.igbm.com
www.ihm.com
www.ibhm.com
www.ihbm.com
www.inm.com
www.ibnm.com
www.inbm.com
www.ib.com
www.ibn.com
www.ibmn.com
www.ibj.com
www.ibmj.com
www.ibjm.com
www.ibk.com
www.ibmk.com
www.ibkm.com
www.ibm.con