United Stated · New York Completed: Apr 22, 2026 00:46 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Strong security — your users are well protected.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
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.
'unsafe-eval' found in script source
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 <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No favicon or icon links detected
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
101 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/0c9b5359-d847-4d92-8c67-876751dfe64e)<a href="https://beavercheck.com/results/0c9b5359-d847-4d92-8c67-876751dfe64e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwikitravel.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwikitravel.orgThis 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 15.3s 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.
10 barrier(s) likely increasing bounce by ~39%.
Page takes 15.3s to load
+12% bounceUsers abandon at ~3s — you're 12.8s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 654ms
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
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
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
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
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$600 investment → $0.58/month returns + USD 157,500 risk avoided
$600
6h · 5 findings
$0.58 /mo
~$7.00 / 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.0 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,126 / month at risk
~$157,507 / year if left unfixed
$157,500
+5 more
$0.58 /mo
7286.9 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.
3.15 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
15.32 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
654 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.139
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.09 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.
15.60 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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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 |
|---|---|---|
| cdn.cookielaw.org/scripttemplates/otSDKStub.js | 8.8 KiB | 1.1 s |
| cdn.cookielaw.org/opt-out/otCCPAiab.js | 6.4 KiB | |
| ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js | 66.5 KiB | 300 ms |
| ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js | 32.9 KiB | 450 ms |
| wikitravel.org/customHP/js/hp.js | 2.0 KiB | 514 ms |
| wikitravel.org/customHP/css/responsive.css | 1.6 KiB | 514 ms |
| wikitravel.org/customHP/js/jquery.main.js | 10.4 KiB | 814 ms |
| ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css | 8.8 KiB | 930 ms |
| wikitravel.org/customHP/css/all.css | 6.6 KiB | 214 ms |
| wikitravel.org/tcf_consent_trigger.js | 1.0 KiB | 514 ms |
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 | |
|---|---|---|---|
Phrasebooks div#content > div.box3 > div.box-holder > img | wikitravel.org/customHP/uploads/lp/5_1573866424.jpg | 18.1 KiB | 7.7 KiB |
div#main > div#content > div > div#logo-holder div#main > div#content > div > div#logo-holder | wikitravel.org/wikitravel.png | 6.7 KiB | 5.6 KiB |
Facebook div.box > ul.social > li > a.twitter | wikitravel.org/customHP/images/icon-social.png | 4.9 KiB | 4.6 KiB |
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Performance issues directly impact user engagement and conversion rates.
head > meta head > meta |
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.
| URL | Time Spent |
|---|---|
| wikitravel.org/ | 831 ms |
| wikitravel.org/en/Main_Page | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
DESTINATION OF THE MONTH
Puerto Baquerizo Moreno
Capital of the Galapagos Isla… div.box > div.carousel2 > div.mask > div.slideset | 0.139 |
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.googletagmanager.com/gtag/js?id=G-QZS14P6J6N&cx=c>m=4e64h1 | 155.5 KiB | 110.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-5JFXBDP | 111.4 KiB | 70.0 KiB |
| cdn.cookielaw.org/scripttemplates/202510.2.0/otBannerSdk.js | 124.0 KiB | 67.4 KiB |
| www.googletagmanager.com/gtag/js?id=G-QZS14P6J6N | 155.5 KiB | 66.7 KiB |
| ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js | 66.4 KiB | 57.7 KiB |
| /f389d50a-32e0-478b-9d4b-2d4592528bea-web.js | 167.5 KiB | 23.4 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 |
|---|---|---|---|
| /f389d50a-32e0-478b-9d4b-2d4592528bea-web.js | 722 ms | 542 ms | 78 ms |
| Unattributable | 641 ms | 15 ms | 0.0 ms |
| wikitravel.org/en/Main_Page | 332 ms | 42 ms | 6.3 ms |
| wikitravel.org/cdn-cgi/challenge-platform/scripts/jsd/main.js | 312 ms | 304 ms | 3.5 ms |
| www.googletagmanager.com/gtag/js?id=G-QZS14P6J6N | 305 ms | 243 ms | 59 ms |
| cdn.cookielaw.org/scripttemplates/202510.2.0/otBannerSdk.js | 290 ms | 203 ms | 62 ms |
| ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js | 214 ms | 156 ms | 11 ms |
| cdn.cookielaw.org/scripttemplates/202510.2.0/otGPP.js | 159 ms | 140 ms | 18 ms |
| www.googletagmanager.com/gtm.js?id=GTM-5JFXBDP | 132 ms | 91 ms | 40 ms |
| cdn.cookielaw.org/scripttemplates/otSDKStub.js | 99 ms | 86 ms | 3.5 ms |
| www.googletagmanager.com/gtag/js?id=G-QZS14P6J6N&cx=c>m=4e64h1 | 90 ms | 32 ms | 57 ms |
| ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js | 72 ms | 42 ms | 30 ms |
| cl.qualaroo.com/ki.js/38969/7O6.js | 66 ms | 40 ms | 20 ms |
| cdn.cookielaw.org/opt-out/otCCPAiab.js | 62 ms | 55 ms | 3.3 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 | 2.0 s |
| Other | 755 ms |
| Script Parsing & Compilation | 396 ms |
| Style & Layout | 242 ms |
| Parse HTML & CSS | 61 ms |
| Garbage Collection | 31 ms |
| Rendering | 30 ms |
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 |
|---|---|---|
| cdn.cookielaw.org/opt-out/otCCPAiab.js | 5.8 KiB | 2.6 KiB |
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.
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 | |
|---|---|
Puerto Baquerizo Moreno div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/440_1776349177.jpg |
São Vicente div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/437_1773573749.jpg |
Cape Verde Cuisine div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/438_1773574681.jpg |
M'zab architecture div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/441_1776349536.jpg |
Italian div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/436_1770462654.jpg |
Cultural Capital 2026 div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/439_1773575057.jpg |
Alerts image div.conteiner > div#link2 > div.alerts > img | wikitravel.org/customHP/uploads/alerts.jpg |
Events image div.conteiner > div#link3 > div.alerts > img | wikitravel.org/customHP/uploads/events.png |
div.conteiner > div#tabs-ct1 > div.alerts > img div.conteiner > div#tabs-ct1 > div.alerts > img | wikitravel.org/customHP/uploads/1.jpg |
div.conteiner > div#tabs-ct2 > div.alerts > img div.conteiner > div#tabs-ct2 > div.alerts > img | wikitravel.org/customHP/uploads/2.jpg |
div#wrapper > div#footer > a.ib-your-choices > img div#wrapper > div#footer > a.ib-your-choices > img | icons.internetbrands.com/ccpa/privacyoptions29x14.png |
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 |
|---|
Take me to: div.box > form.search-form > fieldset > label |
126,120 Pages in English div.boxwrap > div.box > div.flags > h2 |
Travel Alerts ul.tabset > li > a.tab > span |
Current and upcoming events ul.tabset > li > a.tab > span |
Top Mountain Trails ul.tabset > li > a.tab > span |
Hidden Gems ul.tabset > li > a.tab > span |
Top Destinations 2026 ul.tabset > li > a.tab > span |
Read more div.box3 > div.box-holder > div.box-text > a.more |
Read more div.box3 > div.box-holder > div.box-text > a.more |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Learn how. div.boxwrap > div.box > strong.read-more > a |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.conteiner > div#tabs-ct1 > div.alerts > img div.conteiner > div#tabs-ct1 > div.alerts > img |
div.conteiner > div#tabs-ct2 > div.alerts > img div.conteiner > div#tabs-ct2 > div.alerts > img |
div#wrapper > div#footer > a.ib-your-choices > img div#wrapper > div#footer > a.ib-your-choices > img |
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.box > form.search-form > fieldset > input#searchsubmitbtn div.box > form.search-form > fieldset > input#searchsubmitbtn |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
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 |
|---|
About Wikitravel div.box-text > ul > li > a |
Tips for new contributors div.box-text > ul > li > a |
Make your first edit on Wikitravel div.box-text > ul > li > a |
Welcome, business owners div.box-text > ul > li > a |
Manual of style div.box-text > ul > li > a |
Ways to help Wikitravel div.box-text > ul > li > a |
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 html |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
Puerto Baquerizo Moreno div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/440_1776349177.jpg | 440 x 317 (1.39) | 947 x 317 (2.99) |
São Vicente div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/437_1773573749.jpg | 440 x 317 (1.39) | 947 x 317 (2.99) |
Cape Verde Cuisine div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/438_1773574681.jpg | 440 x 317 (1.39) | 947 x 317 (2.99) |
M'zab architecture div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/441_1776349536.jpg | 440 x 317 (1.39) | 947 x 317 (2.99) |
Italian div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/436_1770462654.jpg | 440 x 317 (1.39) | 947 x 317 (2.99) |
Cultural Capital 2026 div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/439_1773575057.jpg | 440 x 317 (1.39) | 947 x 317 (2.99) |
Gobi Desert, Mongolia div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/26_1552331930.jpg | 446 x 294 (1.52) | 925 x 295 (3.14) |
Lake Urnersee div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/28_1554237173.jpg | 446 x 294 (1.52) | 925 x 295 (3.14) |
Zanzibar div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/27_1552332139.jpg | 446 x 294 (1.52) | 925 x 295 (3.14) |
The Balkans div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/25_1552331784.jpg | 446 x 294 (1.52) | 925 x 295 (3.14) |
Puebla, Mexico div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/24_1552331570.jpg | 446 x 294 (1.52) | 925 x 295 (3.14) |
Georgia, USA div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/19_1483157768.jpg | 446 x 294 (1.52) | 925 x 295 (3.14) |
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 | |
|---|---|---|---|---|
São Vicente div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/437_1773573749.jpg | 440 x 317 | 947 x 317 | 660 x 476 |
Cultural Capital 2026 div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/439_1773575057.jpg | 440 x 317 | 947 x 317 | 660 x 476 |
Puerto Baquerizo Moreno div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/440_1776349177.jpg | 440 x 317 | 947 x 317 | 660 x 476 |
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 |
|---|---|
| SharedStorage | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
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.
| Link destination | Link Text |
|---|---|
| wikitravel.org/en/List_of_phrasebooks | Read more |
| wikitravel.org/en/Nepal | Read more |
| wikitravel.org/en/Don%27t_tout | Read more |
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.conteiner > div#tabs-ct1 > div.alerts > img div.conteiner > div#tabs-ct1 > div.alerts > img |
div.conteiner > div#tabs-ct2 > div.alerts > img div.conteiner > div#tabs-ct2 > div.alerts > img |
div#wrapper > div#footer > a.ib-your-choices > img div#wrapper > div#footer > a.ib-your-choices > img |
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 |
|---|
- Your Privacy Choices body > div#wrapper > div#footer > a.ib-your-choices |
To appear in search results, crawlers need access to your app.
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.
722 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.76 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.382
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.00 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.52 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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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 | |
|---|---|---|---|
Events image div.conteiner > div#link3 > div.alerts > img | wikitravel.org/customHP/uploads/events.png | 353.2 KiB | 308.9 KiB |
div.conteiner > div#tabs-ct1 > div.alerts > img div.conteiner > div#tabs-ct1 > div.alerts > img | wikitravel.org/customHP/uploads/1.jpg | 160.1 KiB | 115.8 KiB |
Cape Verde Cuisine ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/438_1773574681.jpg | 85.0 KiB | 83.3 KiB |
world map div.boxwrap > div.box > div.map > img | wikitravel.org/customHP/images/map.png | 88.8 KiB | 60.1 KiB |
São Vicente ul.pagination > li.active > a > img.resize | wikitravel.org/customHP/uploads/des_month/437_1773573749.jpg | 54.7 KiB | 53.0 KiB |
Italian ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/436_1770462654.jpg | 53.7 KiB | 52.1 KiB |
Cultural Capital 2026 ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/439_1773575057.jpg | 34.8 KiB | 33.6 KiB |
M'zab architecture ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/441_1776349536.jpg | 30.2 KiB | 29.2 KiB |
div.conteiner > div#tabs-ct2 > div.alerts > img div.conteiner > div#tabs-ct2 > div.alerts > img | wikitravel.org/customHP/uploads/2.jpg | 53.5 KiB | 9.4 KiB |
Phrasebooks div#content > div.box3 > div.box-holder > img | wikitravel.org/customHP/uploads/lp/5_1573866424.jpg | 18.1 KiB | 7.7 KiB |
div#main > div#sidebar > div#mw-panel > div#p-logo div#main > div#sidebar > div#mw-panel > div#p-logo | wikitravel.org/customHP/images/logo.png | 6.7 KiB | 5.6 KiB |
Facebook div.box > ul.social > li > a.twitter | wikitravel.org/customHP/images/icon-social.png | 4.9 KiB | 4.6 KiB |
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 |
|---|---|---|
| ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js | 66.5 KiB | 82 ms |
| cdn.cookielaw.org/opt-out/otCCPAiab.js | 6.1 KiB | |
| cdn.cookielaw.org/scripttemplates/otSDKStub.js | 9.1 KiB | 261 ms |
| ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js | 32.9 KiB | 82 ms |
| ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css | 8.8 KiB | 207 ms |
| wikitravel.org/customHP/js/jquery.main.js | 10.4 KiB | 188 ms |
| wikitravel.org/customHP/js/hp.js | 2.0 KiB | 148 ms |
| wikitravel.org/customHP/css/responsive.css | 1.6 KiB | 148 ms |
| wikitravel.org/customHP/css/all.css | 6.6 KiB | 67 ms |
| wikitravel.org/tcf_consent_trigger.js | 1.0 KiB | 148 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.
| URL | Time Spent |
|---|---|
| wikitravel.org/ | 245 ms |
| wikitravel.org/en/Main_Page | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
DESTINATION OF THE MONTH
Puerto Baquerizo Moreno
Capital of the Galapagos Isla… div.box > div.carousel2 > div.mask > div.slideset | 0.382 |
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.googletagmanager.com/gtag/js?id=G-QZS14P6J6N&cx=c>m=4e64h1 | 155.5 KiB | 110.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-5JFXBDP | 111.4 KiB | 70.0 KiB |
| cdn.cookielaw.org/scripttemplates/202510.2.0/otBannerSdk.js | 124.0 KiB | 67.4 KiB |
| www.googletagmanager.com/gtag/js?id=G-QZS14P6J6N | 155.5 KiB | 66.7 KiB |
| ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js | 66.4 KiB | 57.8 KiB |
| cl.qualaroo.com/ki.js/38969/7O6.js | 55.5 KiB | 29.0 KiB |
| /f389d50a-32e0-478b-9d4b-2d4592528bea-web.js | 167.5 KiB | 23.4 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 |
|---|---|---|
| cdn.cookielaw.org/opt-out/otCCPAiab.js | 5.8 KiB | 2.6 KiB |
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.
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 | |
|---|---|
Puerto Baquerizo Moreno div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/440_1776349177.jpg |
São Vicente div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/437_1773573749.jpg |
Cape Verde Cuisine div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/438_1773574681.jpg |
M'zab architecture div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/441_1776349536.jpg |
Italian div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/436_1770462654.jpg |
Cultural Capital 2026 div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_month/439_1773575057.jpg |
Puerto Baquerizo Moreno ul.pagination > li.active > a > img.resize | wikitravel.org/customHP/uploads/des_month/440_1776349177.jpg |
São Vicente ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/437_1773573749.jpg |
Cape Verde Cuisine ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/438_1773574681.jpg |
M'zab architecture ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/441_1776349536.jpg |
Italian ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/436_1770462654.jpg |
Cultural Capital 2026 ul.pagination > li > a > img.resize | wikitravel.org/customHP/uploads/des_month/439_1773575057.jpg |
Alerts image div.conteiner > div#link2 > div.alerts > img | wikitravel.org/customHP/uploads/alerts.jpg |
Events image div.conteiner > div#link3 > div.alerts > img | wikitravel.org/customHP/uploads/events.png |
div.conteiner > div#tabs-ct1 > div.alerts > img div.conteiner > div#tabs-ct1 > div.alerts > img | wikitravel.org/customHP/uploads/1.jpg |
div.conteiner > div#tabs-ct2 > div.alerts > img div.conteiner > div#tabs-ct2 > div.alerts > img | wikitravel.org/customHP/uploads/2.jpg |
div#wrapper > div#footer > a.ib-your-choices > img div#wrapper > div#footer > a.ib-your-choices > img | icons.internetbrands.com/ccpa/privacyoptions29x14.png |
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 |
|---|
Travel Alerts ul.tabset > li > a.tab > span |
Read more div.box3 > div.box-holder > div.box-text > a.more |
Read more div.box3 > div.box-holder > div.box-text > a.more |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.conteiner > div#tabs-ct1 > div.alerts > img div.conteiner > div#tabs-ct1 > div.alerts > img |
div.conteiner > div#tabs-ct2 > div.alerts > img div.conteiner > div#tabs-ct2 > div.alerts > img |
div#wrapper > div#footer > a.ib-your-choices > img div#wrapper > div#footer > a.ib-your-choices > img |
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.box > form.search-form > fieldset > input#searchsubmitbtn div.box > form.search-form > fieldset > input#searchsubmitbtn |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
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 |
|---|
About Wikitravel div.box-text > ul > li > a |
Tips for new contributors div.box-text > ul > li > a |
Make your first edit on Wikitravel div.box-text > ul > li > a |
Welcome, business owners div.box-text > ul > li > a |
Manual of style div.box-text > ul > li > a |
Ways to help Wikitravel div.box-text > ul > li > a |
Main Page div.body > ul > li#n-mainpage > a |
Project Home div.body > ul > li#n-projectpage > a |
Travellers' Pub div.body > ul > li#n-Travellers.27-Pub > a |
Recent changes div.body > ul > li#n-recentchanges > a |
Random page div.body > ul > li#n-randompage > a |
Report a problem div.body > ul > li#n-Report-a-problem > a |
Upload a picture div.body > ul > li#n-Upload-a-picture > a |
Printable version div.body > ul > li#t-print > a |
Permanent link div.body > ul > li#t-permalink > a |
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 html |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
Gobi Desert, Mongolia div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/26_1552331930.jpg | 911 x 294 (3.10) | 925 x 295 (3.14) |
Lake Urnersee div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/28_1554237173.jpg | 911 x 294 (3.10) | 925 x 295 (3.14) |
Zanzibar div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/27_1552332139.jpg | 911 x 294 (3.10) | 925 x 295 (3.14) |
The Balkans div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/25_1552331784.jpg | 911 x 294 (3.10) | 925 x 295 (3.14) |
Puebla, Mexico div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/24_1552331570.jpg | 911 x 294 (3.10) | 925 x 295 (3.14) |
Georgia, USA div.mask > div.slideset > div.slide > img | wikitravel.org/customHP/uploads/des_top/19_1483157768.jpg | 911 x 294 (3.10) | 925 x 295 (3.14) |
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 |
|---|---|
| SharedStorage | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
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.
| Link destination | Link Text |
|---|---|
| wikitravel.org/en/List_of_phrasebooks | Read more |
| wikitravel.org/en/Nepal | Read more |
| wikitravel.org/en/Don%27t_tout | Read more |
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.conteiner > div#tabs-ct1 > div.alerts > img div.conteiner > div#tabs-ct1 > div.alerts > img |
div.conteiner > div#tabs-ct2 > div.alerts > img div.conteiner > div#tabs-ct2 > div.alerts > img |
div#wrapper > div#footer > a.ib-your-choices > img div#wrapper > div#footer > a.ib-your-choices > img |
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 |
|---|
- Your Privacy Choices body > div#wrapper > div#footer > a.ib-your-choices |
To appear in search results, crawlers need access to your app.
Send Feedback