Spain · Madrid Completed: Apr 15, 2026 22:56 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 72 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Good foundation, but a few gaps could be exploited.
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.
Mostly compliant — a few items need attention.
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.
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.
113 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
114 HTTP requests — consider bundling or reducing
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/090468f8-7b92-4ae1-b680-93fe063cb940)<a href="https://beavercheck.com/results/090468f8-7b92-4ae1-b680-93fe063cb940"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fskyscanner.net" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fskyscanner.netThis 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 12.0s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.
$650 investment → $2,753/month returns + USD 157,500 risk avoided
$650
6h · 5 findings
$2,753 /mo
~$33,034 / year
USD 157,500
if kept compliant
$100 — 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.
6.5 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,505 / year if left unfixed
$157,500
+5 more
$0.45 /mo
5601.4 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 3 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.41 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
12.04 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
901 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.087
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.41 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.
16.48 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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| /rf8vapwA/captcha.js?a=captcha&m=0&u=539ce7b0-391e-11f1-b... | 600.0 s | 263.6 KiB |
| client.px-cloud.net/PXrf8vapwA/main.min.js | 600.0 s | 91.8 KiB |
| www.skyscanner.fr/sttc/px/captcha-v2/static/js/main.80db1e99.js | 86400.0 s | 83.5 KiB |
| crcldu.com/bd/auditor.js?v=1776293760000 | 120.0 s | 29.1 KiB |
| js.skyscnr.com/sttc/px/captcha-v2/captcha-01.svg | 86400.0 s | 14.3 KiB |
| www.skyscanner.fr/sttc/px/captcha-v2/static/css/main.23768613.css | 86400.0 s | 4.3 KiB |
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.
| URL | Transfer Size | Duration |
|---|---|---|
| www.skyscanner.fr/sttc/px/captcha-v2/static/css/main.23768613.css | 4.3 KiB | 172 ms |
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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 |
|---|---|---|
| www.skyscanner.fr/g/tagging/gtm.js?id=GTM-W8ZST32 | 163.4 KiB | 80.7 KiB |
| /rf8vapwA/captcha.js?a=captcha&m=0&u=539ce7b0-391e-11f1-b... | 260.6 KiB | 44.2 KiB |
| js.skyscnr.com/sttc/banana/static/js/463.a4089d5f.chunk.js | 106.1 KiB | 43.4 KiB |
| www.skyscanner.fr/sttc/px/captcha-v2/static/js/main.80db1e99.js | 83.1 KiB | 34.6 KiB |
| www.skyscanner.fr/rf8vapwA/init.js | 100.8 KiB | 34.0 KiB |
| client.px-cloud.net/PXrf8vapwA/main.min.js | 91.5 KiB | 26.5 KiB |
| js.skyscnr.com/sttc/trackolding/client-tracking-sync.a1e741da6ea36448051c.js | 30.7 KiB | 24.1 KiB |
| js.skyscnr.com/sttc/banana/static/js/Bootstrap.8999441e.chunk.js | 70.6 KiB | 22.2 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| client.px-cloud.net/PXrf8vapwA/main.min.js | 2.3 s | 1.4 s | 16 ms |
| js.skyscnr.com/sttc/banana/static/js/463.a4089d5f.chunk.js | 1.7 s | 1.4 s | 30 ms |
| /rf8vapwA/captcha.js?a=captcha&m=0&u=539ce7b0-391e-11f1-b... | 1.4 s | 1.3 s | 50 ms |
| Unattributable | 756 ms | 19 ms | 0.0 ms |
| /?previousCultureSource=GEO_LOCATION&redirectedFrom=www.s... | 663 ms | 474 ms | 22 ms |
| /sttc/px/captcha-v2/index.html?url=Lw==&uuid=539ce7b0-391... | 250 ms | 2.9 ms | 1.0 ms |
| www.skyscanner.fr/g/tagging/gtm.js?id=GTM-W8ZST32 | 211 ms | 170 ms | 39 ms |
| www.skyscanner.fr/sttc/px/captcha-v2/static/js/main.80db1e99.js | 154 ms | 123 ms | 27 ms |
| js-agent.newrelic.com/nr-spa-1.302.0.min.js | 152 ms | 110 ms | 8.8 ms |
| js.skyscnr.com/sttc/banana/static/js/Bootstrap.8999441e.chunk.js | 123 ms | 104 ms | 19 ms |
| www.skyscanner.fr/rf8vapwA/init.js | 119 ms | 93 ms | 16 ms |
| js.skyscnr.com/sttc/banana/static/js/1694.5a9c0802.chunk.js | 105 ms | 94 ms | 11 ms |
| js.skyscnr.com/sttc/banana/static/js/main.6169c976.js | 92 ms | 82 ms | 1.0 ms |
| js.skyscnr.com/sttc/banana/static/js/5840.8f0b0746.chunk.js | 51 ms | 5.0 ms | 8.2 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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 5.6 s |
| Style & Layout | 1.2 s |
| Other | 974 ms |
| Script Parsing & Compilation | 330 ms |
| Garbage Collection | 272 ms |
| Rendering | 58 ms |
| Parse HTML & CSS | 55 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | 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. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
539ce7b0-391e-11f1-be72-ab517878f7de body > div#root > div#app_main > section.App_App__identifier__M2ZkO |
These are opportunities to improve the legibility of your content.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.bpk-touch-support html.bpk-touch-support |
These items highlight common accessibility best practices.
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. | /rf8vapwA/captcha.js?a=captcha&m=0&u=539ce7b0-391e-11f1-b... line 1, col 206600 |
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 () |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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.
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.64 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.92 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
6 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.006
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.64 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.
3.71 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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| /rf8vapwA/captcha.js?a=captcha&m=0&u=5d8a1a90-391e-11f1-a... | 600.0 s | 263.6 KiB |
| client.px-cloud.net/PXrf8vapwA/main.min.js | 600.0 s | 91.8 KiB |
| www.skyscanner.fr/sttc/px/captcha-v2/static/js/main.80db1e99.js | 86400.0 s | 83.5 KiB |
| crcldu.com/bd/auditor.js?v=1776293760000 | 120.0 s | 29.1 KiB |
| js.skyscnr.com/sttc/px/captcha-v2/captcha-01.svg | 86400.0 s | 14.3 KiB |
| www.skyscanner.fr/sttc/px/captcha-v2/static/css/main.23768613.css | 86400.0 s | 4.3 KiB |
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.
| URL | Transfer Size | Duration |
|---|---|---|
| www.skyscanner.fr/sttc/px/captcha-v2/static/css/main.23768613.css | 4.3 KiB | 60 ms |
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.
Performance issues directly impact user engagement and conversion rates.
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.
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 |
|---|---|---|
| www.skyscanner.fr/g/tagging/gtm.js?id=GTM-W8ZST32 | 163.4 KiB | 80.5 KiB |
| /rf8vapwA/captcha.js?a=captcha&m=0&u=5d8a1a90-391e-11f1-a... | 260.6 KiB | 44.2 KiB |
| js.skyscnr.com/sttc/banana/static/js/463.a4089d5f.chunk.js | 106.1 KiB | 43.2 KiB |
| www.skyscanner.fr/sttc/px/captcha-v2/static/js/main.80db1e99.js | 83.1 KiB | 34.6 KiB |
| www.skyscanner.fr/rf8vapwA/init.js | 100.8 KiB | 34.0 KiB |
| client.px-cloud.net/PXrf8vapwA/main.min.js | 91.5 KiB | 26.5 KiB |
| js.skyscnr.com/sttc/trackolding/client-tracking-sync.a1e741da6ea36448051c.js | 30.7 KiB | 24.1 KiB |
| js.skyscnr.com/sttc/banana/static/js/Bootstrap.8999441e.chunk.js | 70.6 KiB | 22.2 KiB |
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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
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.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.4 s |
| Style & Layout | 277 ms |
| Other | 256 ms |
| Script Parsing & Compilation | 86 ms |
| Garbage Collection | 55 ms |
| Parse HTML & CSS | 17 ms |
| Rendering | 13 ms |
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. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
5d8a1a90-391e-11f1-a80e-51c92a9da7d9 body > div#root > div#app_main > section.App_App__identifier__M2ZkO |
These are opportunities to improve the legibility of your content.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.bpk-no-touch-support html.bpk-no-touch-support |
These items highlight common accessibility best practices.
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. | /rf8vapwA/captcha.js?a=captcha&m=0&u=5d8a1a90-391e-11f1-a... line 1, col 206600 |
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 () |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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.
Send Feedback