Netherlands · Amsterdam Completed: Apr 7, 2026 20:43 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 74 / 100
Based on 8 categories, 0 sections
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
HSTS header is missing
No Content-Security-Policy header found
2 image(s) missing alt attribute
No <main> landmark found
[](https://beavercheck.com/results/95c21398-93bd-d7bf-0b5c-bcab808d470c)<a href="https://beavercheck.com/results/95c21398-93bd-d7bf-0b5c-bcab808d470c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.ryanair.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.ryanair.comThis badge auto-updates with your latest scan result.
Thanks for your feedback!
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.
5.71 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
9.04 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.39 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.002
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.71 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.
10.03 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| polyfill.ryanair.com/?features=intersectionObserver,smoothscroll | 86400.0 s | 17.2 KiB |
| www.facebook.com/tr?id=776134079199579&ev=PageView&cd[market]=nl-nl | 0.0 ms | 19 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| URL | Time Spent |
|---|---|
| www.ryanair.com/ | 772 ms |
| www.ryanair.com/nl/nl | 0.0 ms |
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.
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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.ryanair.com/homepage_dist/mobile/main.faf5dba9c7a67dab.js | 557.8 KiB | 239.1 KiB |
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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| polyfill.ryanair.com/?features=intersectionObserver,smoothscroll | 3.7 s | 3.2 s | 9.9 ms |
| Unattributable | 731 ms | 22 ms | 0.0 ms |
| www.ryanair.com/nl/nl | 584 ms | 12 ms | 3.2 ms |
| www.ryanair.com/homepage_dist/mobile/main.faf5dba9c7a67dab.js | 163 ms | 93 ms | 15 ms |
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
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.3 s |
| Other | 1.2 s |
| Style & Layout | 494 ms |
| Rendering | 67 ms |
| Parse HTML & CSS | 62 ms |
| Script Parsing & Compilation | 29 ms |
| Garbage Collection | 22 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
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.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
| Failing Elements |
|---|
Algemene Vervoersvoorwaarden footer.legal-footer > div.legal-footer__row > div.legal-footer__processing-fee > a |
These are opportunities to improve the legibility of your content.
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.
| Failing Elements |
|---|
Algemene vervoersvoorwaarden footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item |
Gebruiksvoorwaarden footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item |
Privacybeleid footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item |
Cookies footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item |
Contact footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item |
These items highlight common accessibility best practices.
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.57 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.90 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
548 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.045
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.13 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.
2.91 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| polyfill.ryanair.com/?features=intersectionObserver,cssVars,objectFit | 86400.0 s | 14.1 KiB |
| www.ryanair.com/content/dam/ryanair/cta%27s/google-play-60H_NL.png | 0.0 ms | 4.7 KiB |
| www.ryanair.com/content/dam/ryanair/cta%27s/Apple-60H_NL.png | 0.0 ms | 3.3 KiB |
| www.facebook.com/tr?id=776134079199579&ev=PageView&cd[market]=nl-nl | 0.0 ms | 19 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| URL | Time Spent |
|---|---|
| www.ryanair.com/ | 236 ms |
| www.ryanair.com/nl/nl | 0.0 ms |
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.
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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.ryanair.com/homepage_dist/desktop/main.da34040018a53c11.js | 729.9 KiB | 252.8 KiB |
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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| polyfill.ryanair.com/?features=intersectionObserver,cssVars,objectFit | 1.1 s | 953 ms | 2.0 ms |
| www.ryanair.com/homepage_dist/desktop/main.da34040018a53c11.js | 434 ms | 392 ms | 5.6 ms |
| www.ryanair.com/nl/nl | 332 ms | 2.6 ms | 0.7 ms |
| Unattributable | 285 ms | 4.6 ms | 0.0 ms |
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
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.4 s |
| Other | 453 ms |
| Style & Layout | 288 ms |
| Garbage Collection | 32 ms |
| Rendering | 29 ms |
| Parse HTML & CSS | 28 ms |
| Script Parsing & Compilation | 8.9 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
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.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
| Failing Elements |
|---|
Algemene Vervoersvoorwaarden footer.legal-footer > div.legal-footer__row > div.legal-footer__processing-fee > a |
These are opportunities to improve the legibility of your content.
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.
| Failing Elements |
|---|
Je avontuur wacht
Vliegen naar Jordanië div.carousel__wrapper > div.carousel__animation-container > hp-discover-destination-promo-card.ng-star-inserted > a.card |
Ontdek Bergamo's Citi Alta
Plan uw bezoek nu div.carousel__wrapper > div.carousel__animation-container > hp-discover-destination-promo-card.ng-star-inserted > a.card |
Ontdek Bergamo en meer
Meer informatie div.carousel__wrapper > div.carousel__animation-container > hp-discover-destination-promo-card.ng-star-inserted > a.card |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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.
Send Feedback