Live.com Site Title

Sign in to your Microsoft account

Live.com Test Results

Live.com Mobile Performance: 46/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Reduce unused CSS. Potential savings of 619 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 466 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.
Properly size images. Potential savings of 437 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Eliminate render-blocking resources. Potential savings of 1,780 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. 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.
Minimize main-thread work
3.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Avoid non-composited animations
2 animated elements found
Animations which are not composited can be janky and increase CLS. 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
Keep request counts low and transfer sizes small
48 requests • 2,027 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
9 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.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More

Live.com 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.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn more.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
99 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.

Live.com Mobile Best Practices: 73/100
Quick overview:
General
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn more
Trust and Safety
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 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.
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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Live.com Mobile Progressive Web App: 42/100
Quick overview:
PWA Optimized
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.
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
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.
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.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Live.com Mobile Accessibility: 98/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-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn more.
Similar sites
Similar tests
www.live.com
www.live.net
www.live.org
www.live.info
www.live.biz
www.live.us
www.live.mobi
www.ive.com
www.live.com
www.pive.com
www.lpive.com
www.plive.com
www.oive.com
www.loive.com
www.olive.com
www.kive.com
www.lkive.com
www.klive.com
www.lve.com
www.luve.com
www.liuve.com
www.luive.com
www.ljve.com
www.lijve.com
www.ljive.com
www.lkve.com
www.likve.com
www.love.com
www.liove.com
www.lie.com
www.lice.com
www.livce.com
www.licve.com
www.life.com
www.livfe.com
www.lifve.com
www.lige.com
www.livge.com
www.ligve.com
www.libe.com
www.livbe.com
www.libve.com
www.liv.com
www.livw.com
www.livew.com
www.livwe.com
www.livs.com
www.lives.com
www.livse.com
www.livd.com
www.lived.com
www.livde.com
www.livr.com
www.liver.com
www.livre.com
www.live.con
Last Tested: