4.1 sec in total
1 sec
2.8 sec
235 ms
Click here to check amazing Developer Travelport content for India. Otherwise, check out these important facts you probably never knew about developer.travelport.com
Developer experience application for Travelport
Visit developer.travelport.comWe analyzed Developer.travelport.com page load time and found that the first response time was 1 sec and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
developer.travelport.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value5.5 s
18/100
25%
Value6.6 s
37/100
10%
Value180 ms
91/100
30%
Value0.079
94/100
15%
Value9.0 s
34/100
10%
1014 ms
188 ms
231 ms
322 ms
246 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 91% of them (60 requests) were addressed to the original Developer.travelport.com, 5% (3 requests) were made to Rnengage.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Developer.travelport.com.
Page size can be reduced by 474.7 kB (31%)
1.5 MB
1.0 MB
In fact, the total size of Developer.travelport.com main page is 1.5 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. 30% of websites need less resources to load. Images take 970.5 kB which makes up the majority of the site volume.
Potential reduce by 27.0 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 27.0 kB or 77% of the original size.
Potential reduce by 84.1 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. Developer Travelport images are well optimized though.
Potential reduce by 282.3 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 282.3 kB or 68% of the original size.
Potential reduce by 81.3 kB
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. Developer.travelport.com needs all CSS files to be minified and compressed as it can save up to 81.3 kB or 85% of the original size.
Number of requests can be reduced by 23 (38%)
60
37
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Developer Travelport. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
developer.travelport.com
1014 ms
screen.css
188 ms
coda-slider-2.0-new.css
231 ms
superfish.css
322 ms
shadowbox.css
246 ms
css
51 ms
modernizr.custom.53303.js
312 ms
html5.js
243 ms
jquery-1.2.6.min.js
265 ms
jquery.pngFix.js
379 ms
shadowbox.js
556 ms
hoverIntent.js
398 ms
superfish.js
415 ms
jquery.easing.1.3.js
465 ms
jquery.coda-slider-2.0-new.js
401 ms
supersizer.js
455 ms
jquery.screwdefaultbuttons.js
548 ms
login_and_search.js
472 ms
main_navigation2.js
487 ms
footer.js
428 ms
RightNow.js
609 ms
index.js
482 ms
autoload.js
483 ms
analytics.js
52 ms
tp-devlogs.png
186 ms
hero-text-1-home.gif
86 ms
Slider-Universal-Logo.jpg
185 ms
Slider-DesktopSDK-Logo.jpg
83 ms
Slider-BookingFeed-Logo.jpg
80 ms
Slider-DevNet-Logo.jpg
182 ms
codemaster-placeholder.jpg
182 ms
dev-network-placeholder.jpg
239 ms
marketplace-thumbnail.jpg
285 ms
travelport-logo.jpg
238 ms
button-blue-small.jpg
323 ms
search-box2.jpg
323 ms
nav-home-2.jpg
232 ms
nav-uapi-2.jpg
295 ms
nav-ud-2.jpg
300 ms
nav-portfolio-2.jpg
308 ms
nav-datafeeds-2.jpg
349 ms
nav-dev-network-2.jpg
372 ms
hero-image-1-home.png
612 ms
hero-image-2-API.png
687 ms
hero-image-3-desktop-sdk.png
617 ms
hero-image-5-booking-feed.png
546 ms
hero-image-6-dev-network.png
585 ms
travelport-3col-gridbox.png
521 ms
button-blue-medium.jpg
598 ms
travelport-feature-box.jpg
625 ms
webinar-icon.png
739 ms
video-container.jpg
673 ms
travelport-3col-gridbox-long.jpg
689 ms
travelport-home-arrow.png
770 ms
footer-colour-bar.jpg
779 ms
icon-twitter.jpg
805 ms
icon-youtube.jpg
814 ms
Stag%20Sans%20Round-Light.otf
823 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
26 ms
travesanreg-webfont.woff
800 ms
travesanbol-webfont.woff
795 ms
acs.js
38 ms
e.js
69 ms
ajax-loader.gif
760 ms
home-sub-nav-bullet.jpg
814 ms
r
37 ms
developer.travelport.com accessibility score
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
developer.travelport.com 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
Browser errors were logged to the console
developer.travelport.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Developer.travelport.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Developer.travelport.com 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.
developer.travelport.com
Open Graph description is not detected on the main page of Developer Travelport. 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: