2.4 sec in total
213 ms
1.8 sec
400 ms
Visit traveller.uk now to see the best up-to-date Traveller content and also check out these interesting facts you probably never knew about traveller.uk
The website of Condé Nast Traveller magazine. Award-winning features, destination guides, and the most beautiful travel photography, for people who love travel
Visit traveller.ukWe analyzed Traveller.uk page load time and found that the first response time was 213 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
traveller.uk performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value17.4 s
0/100
25%
Value3.9 s
82/100
10%
Value1,110 ms
23/100
30%
Value0.015
100/100
15%
Value17.3 s
4/100
10%
213 ms
49 ms
121 ms
127 ms
46 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Traveller.uk, 51% (22 requests) were made to Cntraveller.com and 35% (15 requests) were made to Media.cntraveller.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Polyfill-fastly.io.
Page size can be reduced by 1.3 MB (19%)
6.9 MB
5.6 MB
In fact, the total size of Traveller.uk main page is 6.9 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. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 1.2 MB
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 1.2 MB or 89% of the original size.
Potential reduce by 0 B
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. Traveller images are well optimized though.
Potential reduce by 131.0 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 12 (40%)
30
18
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Traveller. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
traveller.uk
213 ms
www.cntraveller.com
49 ms
otSDKStub.js
121 ms
gpt.js
127 ms
v6.js
46 ms
polyfill.min.js
1536 ms
3404.a8585b5b0e2be9faedbd.js
30 ms
6292.5e4f8ec1186a2c31c48e.js
24 ms
6225.2c0c0816dc8d5442dc7e.js
24 ms
1990.5ae2278af091390d88df.js
22 ms
4196.e47a77a31c9c12e056de.js
43 ms
7035.087808ddbc0375d2f28c.js
19 ms
8230.b502a48006f066e28e0c.js
29 ms
1206.4186595ffeeeb4ce5171.js
31 ms
presenter-bundles.176bd378542fc6420481.js
31 ms
logo-uk-header.svg
56 ms
hotel%2520graphy%2520nezu-affordable%2520tokyo%2520hotel-aug24%2520-pr-global7.jpg
87 ms
logo-uk-reverse.svg
34 ms
Sandblu%2520Santorini-hotel%2520review-aug24-pr-global-22.jpg
88 ms
Monastery-Garden-Botanic-Sanctuary-antwerp-aug24-pr-global.jpg
90 ms
hotel%2520cafe%2520royal-hotel%2520review-aug24-pr-global-21.jpg
89 ms
hotel%2520balzac%2520paris-jul24-pr-global-Matthieu%2520Salvaing4.jpg
89 ms
The%2520Connaught%2520Patisserie%2520-donughts-aug23-pr-aug23-pr.jpeg
88 ms
Duck-and-Waffle-duck-and-waffles-may22-pr-global.jpg
94 ms
manchester.jpg
92 ms
coffee%2520london.jpg
90 ms
rahel%2520stephanie-ask%2520a%2520local-aug24-pr-global.jpg
91 ms
2AIRE%2520ANCIENT%2520BATHS_FRIGIDARIUM-dec22-pr-globaljpeg.jpeg
93 ms
Istanbul-jul19-global-pr-GettyImages-576377587.jpg
91 ms
kos-GettyImages-1436672557.jpg
93 ms
Pool_Indoor%2520Outdoor_External%2520View%2520(1)-Lefay%2520Resort%2520&%2520Spa%2520Lago%2520di%2520Garda-july24-pr-global.jpg
95 ms
Tanzania-GettyImages-1307560220.jpg
95 ms
pubads_impl.js
13 ms
farnhamdisplay-light-webfont.woff
4 ms
farnhamdisplay-medium.woff
25 ms
farnhamdisplay-medium-ital.woff
98 ms
farnhamdisplay-bold-webfont.woff
23 ms
worksans-regular.woff
23 ms
worksans-medium.woff
24 ms
WorkSans-Bold.woff
25 ms
FreightBig-SemiBold.woff
26 ms
FreightBig-Bold.woff
25 ms
FarnhamDisplay-LightItalic.woff
25 ms
traveller.uk accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
traveller.uk 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
Missing source maps for large first-party JavaScript
traveller.uk 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 Traveller.uk 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 Traveller.uk 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.
traveller.uk
Open Graph data is detected on the main page of Traveller. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: