2.3 sec in total
320 ms
1.7 sec
230 ms
Click here to check amazing Wander content for United States. Otherwise, check out these important facts you probably never knew about wander.am
Search flights & vacation packages by price, let us build your perfect vacation package so you won't have to · No Reservation Costs · Top Deals
Visit wander.amWe analyzed Wander.am page load time and found that the first response time was 320 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
wander.am performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value27.4 s
0/100
25%
Value46.0 s
0/100
10%
Value100,790 ms
0/100
30%
Value0.595
11/100
15%
Value133.1 s
0/100
10%
320 ms
207 ms
247 ms
282 ms
274 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wander.am, 65% (35 requests) were made to D19wm5yhteu8df.cloudfront.net and 6% (3 requests) were made to Widget.getyourguide.com. The less responsive or slowest element that took the longest time to load (431 ms) relates to the external source D19wm5yhteu8df.cloudfront.net.
Page size can be reduced by 119.3 kB (22%)
548.1 kB
428.8 kB
In fact, the total size of Wander.am main page is 548.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 264.5 kB which makes up the majority of the site volume.
Potential reduce by 74.1 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 74.1 kB or 76% of the original size.
Potential reduce by 6.9 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Wander images are well optimized though.
Potential reduce by 37.8 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 37.8 kB or 33% of the original size.
Potential reduce by 497 B
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Wander.am has all CSS files already compressed.
Number of requests can be reduced by 43 (83%)
52
9
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wander. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.wander.am
320 ms
200.c484d03d3330ea882bb5.css
207 ms
wander_app.c484d03d3330ea882bb5.css
247 ms
5.c484d03d3330ea882bb5.css
282 ms
30.c484d03d3330ea882bb5.css
274 ms
1.c484d03d3330ea882bb5.css
275 ms
6.c484d03d3330ea882bb5.css
263 ms
11.c484d03d3330ea882bb5.css
246 ms
18.c484d03d3330ea882bb5.css
233 ms
28.c484d03d3330ea882bb5.css
234 ms
32.c484d03d3330ea882bb5.css
249 ms
178.c484d03d3330ea882bb5.css
247 ms
application-237a634017c5a882fc64e15f7ffa10649937146212590210225969882092c4a8.js
358 ms
vendors~wander_app-6dc799513de0fe08d72f.js
363 ms
wander_app-3e220d0647eeb7f9e77d.js
356 ms
vendors~AirportPage~AreaPage~AttractionListPage~AttractionPage~DestinationListPage~DestinationMobile~af8f5afc-88b73f85f1687a6d2cbb.js
359 ms
vendors~AirportPage~AreaPage~DestinationListPage~DestinationMobileNavbar~FlightListPage~HomeApp~Hote~97f116b7-095074088ec2dce3f980.js
359 ms
vendors~AirportPage~AttractionListPage~AttractionPage~DestinationListPage~FlightListPage~HomeApp~Hot~97570b5f-f57958bce4c279799b6f.js
357 ms
vendors~AttractionPage~DestinationListPage~FlightListPage~HomeApp~HotelInfo~HotelInfoMobile~HotelInf~1bf5dfe5-1e25fe20d11f10cb32fb.js
365 ms
vendors~AirportPage~AreaPage~HomeApp~HotelInfo~HotelInfoMobile~HotelInfoMobileV2~HotelInfoV2~HotelListPage-2a79811a51d9ff4aa9f8.js
431 ms
vendors~DestinationListPage~FlightListPage~HomeApp~HotelListPage~PackageManager-7643b53075187c183b45.js
354 ms
vendors~AirportPage~AreaPage~HomeApp~HotelListPage-ab44149971368f713ca1.js
354 ms
vendors~AirportPage~DestinationListPage~HomeApp-cb309a4b2be12d8afe5c.js
355 ms
vendors~HomeApp-5b285e42305f461f04c0.js
356 ms
AirportPage~AreaPage~DestinationListPage~DestinationMobileNavbar~FlightListPage~HomeApp~HotelInfo~Ho~57c3bd92-bc85f80f301868436c9e.js
428 ms
DestinationListPage~DestinationMobileNavbar~FlightListPage~HomeApp~HotelListPage~HotelMobileNavbar~P~173fc05f-d54abbe9b93de1dd2cc6.js
431 ms
DestinationListPage~FlightListPage~HomeApp~HotelListPage~PackageManager-d68886893c76308999ea.js
355 ms
AirportPage~AreaPage~HomeApp~HotelListPage-221e4f66f7a90bd93580.js
426 ms
AirportPage~DestinationListPage~HomeApp-ba82c6fe1251bb972f26.js
431 ms
DestinationListPage~HomeApp-adfec5472dd8bc3a0c30.js
431 ms
HomeApp-35a4e92310e791316bec.js
428 ms
analytics.js
310 ms
mixpanel-2-latest.min.js
337 ms
hotjar-809389.js
415 ms
gtm.js
359 ms
no-profile-image-846acb97d272882a23b0645d674d9f4eb2d530f3bc73e3cf52bd1a824138fda8.png
214 ms
home-f345ee67fe7dd70350a9a72647c66de2.jpg
214 ms
package-banner-28b4b933c4bdca165cab41f29d2bc185.png
212 ms
logo_footer-deb005b6c7ec2d8d1b7e462cc25e4e09a7662bc8e8a72674c2c621f8e2876211.png
212 ms
fontawesome-webfont-ba0c59deb5450f5cb41b3f93609ee2d0d995415877ddfa223e8a8a7533474f07.woff
386 ms
conversion_async.js
92 ms
pa.umd.production.min.js
26 ms
modules.f0cd1ed70b545da08b60.js
27 ms
widget.js
414 ms
pa-main.1662116213033_fee6b4d815ffd351d556368a90c791191aff7f27.umd.production.min.js
66 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
23 ms
49 ms
visit-data
418 ms
18 ms
nr-1216.min.js
48 ms
shim.latest.js
64 ms
625e5e716f
151 ms
frame.73b21f0c.js
18 ms
vendor.2b3ec6d9.js
98 ms
wander.am accessibility score
Names and labels
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.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
wander.am best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
wander.am SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wander.am can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wander.am main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
wander.am
Open Graph data is detected on the main page of Wander. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: