Spain · Madrid Completed: Apr 16, 2026 17:05 UTCMobile 375 × 812
Score: 73 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
is missing width/height — may cause layout shift
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/2dcdbce9-212c-4312-a3d7-73b21925337c)<a href="https://beavercheck.com/results/2dcdbce9-212c-4312-a3d7-73b21925337c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Foutlook.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Foutlook.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 7.5s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
9 barrier(s) likely increasing bounce by ~29%.
Page takes 7.5s to load
+12% bounceUsers abandon at ~3s — you're 5.0s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Viewport disables user zoom
+2% bounceVisitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
Fix: Remove user-scalable=no; drop maximum-scale if it's below 2
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
1 broken link(s) on the page
+2% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$500 investment → $5,629/month returns + USD 157,500 risk avoided
$500
5h · 5 findings
$5,629 /mo
~$67,550 / year
USD 157,500
if kept compliant
$150 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.0 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,125 / month at risk
~$157,504 / year if left unfixed
$157,500
+5 more
$0.31 /mo
3874.2 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
6.19 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
7.47 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
8 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.19 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
7.47 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.section-master > div.section-master__image > div.ocr-img > img div.section-master > div.section-master__image > div.ocr-img > img | /is/image/microsoftcorp/M365_FY26_Evergreen_ProductPage_O... | 318.2 KiB | 284.8 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Lists the toplevel main thread tasks that executed during page load.
Performance issues directly impact user engagement and conversion rates.
Collection of useful page vitals.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| outlook.com/ | 1.1 s |
| outlook.com/mail/ | 803 ms |
| outlook.live.com/mail/ | 2.0 s |
| /en-us/microsoft-365/outlook/email-and-calendar-software-... | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /golf/etc.clientlibs/onecloud/clientlibs/clientlib-reimag... | 99.3 KiB | 81.4 KiB |
| /golf/etc.clientlibs/onecloud/clientlibs/clientlib-mwf-ne... | 39.6 KiB | 38.5 KiB |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| res.public.onecdn.static.microsoft/owamini/20260306.04/scripts/owa.13939.js | 7.2 KiB | 3.7 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js | 231.8 KiB | 33.5 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div.theme-light > div.c-uhfh-gcontainer-st > a#uhfLogo > img.c-image div.theme-light > div.c-uhfh-gcontainer-st > a#uhfLogo > img.c-image | uhf.microsoft.com/images/microsoft/RE1Mu3b.png |
A computer screen with a mail div#reimagine-grid-oc3cb4 > div.media > div.ocr-img > img#image-oc77da |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Search Expanded div.c-uhfh-gcontainer-st > div.c-uhfh-actions > form#searchForm > input#cli_shellHeaderSearchInput |
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Outlook for Windows
Outlook for Mac
Outlook for Web
Outlook for Mobile ul.js-paddle-items > li.nested-menu > div.c-uhf-menu > ul |
For home
For business ul.js-paddle-items > li.nested-menu > div.c-uhf-menu > ul |
AI email assistant
AI email generator
Email account
Shared calendar
Copilot lea… ul.js-paddle-items > li.nested-menu > div.c-uhf-menu > ul |
Global
Microsoft 365
Azure
Copilot
Windows
Surface
Xbox
Deals
Small Business
Su… ul.js-paddle-items > li > div.c-uhf-menu > ul.f-multi-column |
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.
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 about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Apps with subscription value div.card-plan-detail > div.card-plan-detail__badges > div.card-plan-detail__badge-text > h6.text |
Apps with subscription value div.card-plan-detail > div.card-plan-detail__badges > div.card-plan-detail__badge-text > h6.text |
Apps with subscription value div.card-plan-detail > div.card-plan-detail__badges > div.card-plan-detail__badge-text > h6.text |
These are opportunities to improve keyboard navigation in your application.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
All Microsoft expand to see list of Microsoft products and services header.c-uhfh > div.theme-light > div.c-uhfh-gcontainer-st > button.c-action-trigger |
Close search header.c-uhfh > div.theme-light > div.c-uhfh-gcontainer-st > button.c-action-trigger |
Microsoft 365 div.theme-light > div.c-uhfh-gcontainer-st > div.c-show-pipe > a#uhfCatLogo |
Home nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a.c-uhf-nav-link |
Outlook nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_subsitename |
For business nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_6 |
Support nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_16 |
Buy now nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_custom_button_outline_newtab_buynow_bhvr92 |
Sign in nav#uhf-g-nav > ul.js-paddle-items > li.single-link > a#c-shellmenu_custom_outline_signin_bhvr100 |
Surface Pro div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Surface Laptop div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Surface Laptop Studio 2 div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Copilot for organizations div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Copilot for personal use div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
AI in Windows div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Explore Microsoft products div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Windows 11 apps div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Account profile div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Download Center div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Store support div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Returns div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Order tracking div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Certified Refurbished div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Store Promise div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Flexible Payments div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft in education div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Devices for education div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Teams for Education div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft 365 Education div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
How to buy for your school div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Educator training and development div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Deals for students and parents div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
AI for education div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft AI div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Security div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Dynamics 365 div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft 365 div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Power Platform div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Teams div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft 365 Copilot div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Small Business div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Azure div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Developer div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Learn div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Support for AI marketplace apps div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Tech Community div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Microsoft Marketplace div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Marketplace Rewards div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Visual Studio div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Careers div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
About Microsoft div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Company news div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Privacy at Microsoft div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Investors div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Diversity and inclusion div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Accessibility div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Sustainability div.c-uhff-nav-group > ul.c-list > li > a.c-uhff-link |
Sitemap nav > ul.c-list > li#c-uhff-footer_sitemap > a.c-uhff-link |
Contact Microsoft nav > ul.c-list > li#c-uhff-footer_contactus > a.c-uhff-link |
Privacy nav > ul.c-list > li#c-uhff-footer_privacyandcookies > a.c-uhff-link |
Manage cookies nav > ul.c-list > li#c-uhff-footer_managecookies > a.c-uhff-link |
Terms of use nav > ul.c-list > li#c-uhff-footer_termsofuse > a.c-uhff-link |
Trademarks nav > ul.c-list > li#c-uhff-footer_trademarks > a.c-uhff-link |
Safety & eco nav > ul.c-list > li#c-uhff-footer_safetyandeco > a.c-uhff-link |
Recycling nav > ul.c-list > li#c-uhff-recycling > a.c-uhff-link |
About our ads nav > ul.c-list > li#c-uhff-footer_aboutourads > a.c-uhff-link |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Search Search Microsoft 365 div.c-uhfh-gcontainer-st > div.c-uhfh-actions > form#searchForm > button#search |
See plans and pricing div.secondary-nav > nav#sticky-nav > div.action > a#action-ocf626 |
Create a free account div.sku > div.sku__buttons > div.button-group > a#action-oc5959 |
View all apps div.row > div.col > div.button-group > a#action-oc45c2 |
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
div.theme-light > div.c-uhfh-gcontainer-st > a#uhfLogo > img.c-image div.theme-light > div.c-uhfh-gcontainer-st > a#uhfLogo > img.c-image | uhf.microsoft.com/images/microsoft/RE1Mu3b.png | 216 x 46 | 216 x 46 | 324 x 69 |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
/en-us/microsoft-365/outlook/email-and-calendar-software-... line 598, col 8 | ReferenceError: CrossSellInstances is not defined
at HTMLDocument.<anonymous> (https://www.microsoft.com/en-us/microsoft-365/outlook/email-and-calendar-software-microsoft-outlook?redirectTo=%2Fmail%2F&sdf=0:599:9) |
/en-us/microsoft-365/outlook/email-and-calendar-software-... line 2, col 4656 | ReferenceError: oc is not defined
at https://www.microsoft.com/en-us/microsoft-365/outlook/email-and-calendar-software-microsoft-outlook?redirectTo=%2Fmail%2F&sdf=0:3:4657 |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
Skip to main content div#headerArea > div#headerRegion > div#headerUniversalHeader > a#uhfSkipToMain |
Back to carousel navigation controls div.carousel > div#carousel-oc67da > section.carousel__section > a.carousel__back-to-controls |
Back to MICROSOFT 365 APPS carousel section div.carousel > div#carousel-oc2f35 > section.carousel__section > a.carousel__back-to-controls |
Back to NEWS AND TIPS-What's new tab section div.carousel > div#carousel-oc4574 > section.carousel__section > a.carousel__back-to-controls |
Back to NEWS AND TIPS-Personal tab section div.carousel > div#carousel-ocb7a0 > section.carousel__section > a.carousel__back-to-controls |
Back to NEWS AND TIPS-For Work tab section div.carousel > div#carousel-oc479a > section.carousel__section > a.carousel__back-to-controls |
Back to NEWS AND TIPS-Tips & tricks tab section div.carousel > div#carousel-oc9161 > section.carousel__section > a.carousel__back-to-controls |
To appear in search results, crawlers need access to your app.
Desktop audit not available for this result.
Send Feedback