mcdonalds.com
The link scan could not be completed.
We could not confirm permission to crawl this site. Its robots policy may be unavailable or disallow this scan. Automatic retries have stopped.
Own it? Check your access rules and server logs for CrashedLinkBot, then retry.
Mobile page report
www.mcdonalds.com
https://www.mcdonalds.com/
Measured · 9/6/2026, 10:39:27 PM UTC
Redirected to: https://www.mcdonalds.com/us/en-us.html
- Speed
- 53
- Accessibility
- 100
- SEO basics
- 100
- Main content (LCP)
- 12.5 s
- Layout shifts (CLS)
- 0.077
- Blocking time (TBT)
- 320 ms
Measurement notes (1)
- The page may not be loading as expected because your test URL (https://www.mcdonalds.com/) was redirected to https://www.mcdonalds.com/us/en-us.html. Try testing the second URL directly.
Your next improvements
Measured findings to investigate, ordered by audit score.
1. Forced reflow
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](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.
2. Largest Contentful Paint
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn more about the Largest Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/)
3. Network dependency tree
[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
4. Time to Interactive
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](https://developer.chrome.com/docs/lighthouse/performance/interactive/).
5. First Contentful Paint
First Contentful Paint marks the time at which the first text or image is painted. [Learn more about the First Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/first-contentful-paint/).
6. Speed Index
Speed Index shows how quickly the contents of a page are visibly populated. [Learn more about the Speed Index metric](https://developer.chrome.com/docs/lighthouse/performance/speed-index/).
7. Max Potential First Input Delay
The maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more about the Maximum Potential First Input Delay metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-max-potential-fid/).
8. Total Blocking Time
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more about the Total Blocking Time metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-total-blocking-time/).
Fix with your coding assistant
Copy a ready-to-use prompt with the issues and affected URLs.
Battle scoring rules
The arena compares five stages: link health, performance, accessibility, SEO, and structure & sharing. Only stages measured with the same method on both sites count. Accessibility and SEO use browser measurements when both have compatible results; otherwise both use the standard checklist. Structure & sharing combines earned and possible checklist points. Most stages won decides the fight, followed by the sum of shared scores and stage order. Identical scores use a deterministic game coin toss. Performance differences up to five points draw. Missing measurements never count as zero. Browser audits do not certify accessibility. The standard scan independently updates ranking when eligible.