3.4 sec in total
27 ms
2.9 sec
464 ms
Welcome to travelocity.mx homepage info - get ready to check Travelocity best content right away, or after learning these important things about travelocity.mx
Wander Wisely with the Price Match Guarantee, Free Changes & Cancellations. Book & Save on Packages, Hotels, Flights, Cars, Cruises & more Today!
Visit travelocity.mxWe analyzed Travelocity.mx page load time and found that the first response time was 27 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
travelocity.mx performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value3.0 s
78/100
25%
Value12.0 s
4/100
10%
Value14,120 ms
0/100
30%
Value0.005
100/100
15%
Value33.1 s
0/100
10%
27 ms
491 ms
25 ms
85 ms
113 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Travelocity.mx, 26% (30 requests) were made to Travelocity.com and 12% (14 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (949 ms) relates to the external source Collector-923.tvsquared.com.
Page size can be reduced by 1.6 MB (52%)
3.1 MB
1.5 MB
In fact, the total size of Travelocity.mx main page is 3.1 MB. 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. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 184.2 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 184.2 kB or 84% of the original size.
Potential reduce by 66.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. Travelocity images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 73% of the original size.
Number of requests can be reduced by 80 (72%)
111
31
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Travelocity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
travelocity.mx
27 ms
www.travelocity.com
491 ms
tvly_HP_Wizard.css-min-4015636475.css
25 ms
uitk-lib-bundle-min.js
85 ms
tvly-responsive.css
113 ms
core-wizard-bundle-min-673083659.css
24 ms
expads-min.js
84 ms
uitk-jquery-jstemplate-bundle-min.js
133 ms
uitk-core-bundle-min.js
135 ms
client-logger-bundle-min-1013242220.js
60 ms
dateTimeFormats.js
134 ms
uitk-localize-bundle-min.js
110 ms
client-logging-bundle-min.js
131 ms
global-header-bundle-min-498981318.css
61 ms
global-header-responsive-bundle-min-1999415234.css
68 ms
ebr-banner-less-0bfe1e2ff558295006d876e1b2b06f38-min.css
128 ms
header.css
181 ms
alert-menu-bundle-min-2757697783.css
60 ms
global-footer-bundles-min-1530752049.css
70 ms
exp.core.tvlyTracking-min-2487701102.js
123 ms
exp.core.channeltracking.v2.1-min-2004753691.js
122 ms
gnome-logo-84x84.png
170 ms
logo.svg
132 ms
sp-news-alert-bell.png
122 ms
hero-banner-secondary-vertical-gradient.png
93 ms
adx
441 ms
activityi;src=4260687;type=naust587;cat=naust031;ord=863277059979.7368
131 ms
rtb-check.svg
398 ms
flags.png
50 ms
dcfc.gif
29 ms
UITKIcons.svg
28 ms
corewizard.siteid_80001.langid_1033-min-2665665294.js
72 ms
homepage-modules.siteid_80001.langid-1033false0v2-min-3799364238.js
395 ms
tealeaf-bundle-min-1480062695.js
394 ms
exp.core.channeltracking.exp-min-511167340.js
395 ms
exitwindowConnector-min-398019400.js
372 ms
air-attach-bundle-min-1362355463.js
393 ms
uitk-only-header-bundle-min-461634651.js
393 ms
header-bundle-min-3163186069.js
453 ms
alert-menu-bundle-min-2323378708.js
437 ms
scratchpad-tray-bundle-min-2655943333.js
393 ms
inauth.js
524 ms
app_download.js
523 ms
utag.js
64 ms
analytics-core-bundle-min.js
20 ms
getairlines
392 ms
promobanners
275 ms
imgad
110 ms
imgad
121 ms
1x1.gif
218 ms
16553
196 ms
zzzzz
96 ms
intent_media_travelocityonexp.js
166 ms
cc.js
286 ms
gpt.js
217 ms
utag.4.js
116 ms
utag.12.js
147 ms
utag.26.js
147 ms
utag.64.js
166 ms
utag.29.js
166 ms
utag.39.js
164 ms
utag.65.js
164 ms
utag.87.js
181 ms
utag.107.js
181 ms
utag.113.js
179 ms
utag.116.js
180 ms
utag.123.js
179 ms
utag.129.js
179 ms
site_status
487 ms
loader-static-light.svg
112 ms
160307_4-Star-Hotels_532.jpg
83 ms
160308_20-anniversary_532.png
60 ms
20150730_24hour_532x299.png
393 ms
conversion_async.js
384 ms
rd
38 ms
kenshoo.js
410 ms
img;m=11042208140771;cache=
400 ms
analytics.js
376 ms
code.js
776 ms
pubads_impl_82.js
407 ms
lb
573 ms
oct.js
624 ms
tag.js
629 ms
activityi;src=5439637;type=natra00;cat=natra0;ord=6911241265479.476
567 ms
id
557 ms
tv2track.js
949 ms
et.js
299 ms
302 ms
config
37 ms
ec.js
212 ms
userTestGroup
222 ms
ads
381 ms
container.html
26 ms
collect
23 ms
s58372829339932
36 ms
77 ms
adsct
125 ms
adsct
127 ms
capture-apps-4.8.0.js
101 ms
ga-audiences
24 ms
js
74 ms
yieldify_1457450204.js
76 ms
iframeStorage.html
213 ms
i.js
111 ms
appsmanagerinit
148 ms
imgad
67 ms
imgad
49 ms
imgad
67 ms
imgad
74 ms
osd.js
72 ms
piwik.php
99 ms
iframeStorage.js
110 ms
1x1_Pixel.PNG
48 ms
s2
53 ms
js
79 ms
travelocity.mx accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
travelocity.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
travelocity.mx SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Travelocity.mx 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 Travelocity.mx 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.
travelocity.mx
Open Graph description is not detected on the main page of Travelocity. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: