5.3 sec in total
491 ms
4.7 sec
149 ms
Visit true.travel now to see the best up-to-date True content for Uganda and also check out these interesting facts you probably never knew about true.travel
True Travel offer tailor-made luxury tours and safaris across the world. A team of travel specialists with passion and market leading expertise are ready to start planning your holiday.
Visit true.travelWe analyzed True.travel page load time and found that the first response time was 491 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
true.travel performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value6.8 s
7/100
25%
Value12.4 s
3/100
10%
Value3,980 ms
1/100
30%
Value0.005
100/100
15%
Value28.9 s
0/100
10%
491 ms
2130 ms
22 ms
41 ms
41 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 79% of them (87 requests) were addressed to the original True.travel, 8% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Cookiehub.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain True.travel.
Page size can be reduced by 269.1 kB (6%)
4.3 MB
4.0 MB
In fact, the total size of True.travel main page is 4.3 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.7 MB which makes up the majority of the site volume.
Potential reduce by 252.5 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 252.5 kB or 87% of the original size.
Potential reduce by 15.0 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. True images are well optimized though.
Potential reduce by 385 B
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.
Potential reduce by 1.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. True.travel has all CSS files already compressed.
Number of requests can be reduced by 63 (67%)
94
31
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of True. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
true.travel
491 ms
www.true.travel
2130 ms
blocks.style.build.css
22 ms
wpp.css
41 ms
style.min.css
41 ms
theme.min.css
44 ms
header-footer.min.css
41 ms
frontend-lite.min.css
33 ms
post-5.css
458 ms
elementor-icons.min.css
45 ms
swiper.min.css
47 ms
frontend-lite.min.css
56 ms
global.css
466 ms
post-50538.css
46 ms
post-12.css
59 ms
post-19.css
52 ms
post-51195.css
53 ms
post-49345.css
61 ms
general.min.css
64 ms
css
55 ms
fontawesome.min.css
64 ms
solid.min.css
68 ms
brands.min.css
68 ms
regular.min.css
71 ms
jquery.min.js
72 ms
jquery-migrate.min.js
76 ms
wpp.min.js
76 ms
widget-mega-menu.min.css
79 ms
widget-nav-menu.min.css
78 ms
widget-call-to-action.min.css
83 ms
widget-loop-builder.min.css
82 ms
widget-icon-list.min.css
82 ms
email-decode.min.js
77 ms
widget-theme-elements.min.css
92 ms
loop-49348.css
86 ms
post-45231.css
89 ms
animations.min.css
89 ms
css
57 ms
mpp-frontend.js
94 ms
api.js
53 ms
dynamic-conditions-public.js
96 ms
hello-frontend.min.js
92 ms
general.min.js
99 ms
premium-wrapper-link.min.js
77 ms
jquery.smartmenus.min.js
88 ms
imagesloaded.min.js
79 ms
forms.js
82 ms
webpack-pro.runtime.min.js
84 ms
webpack.runtime.min.js
87 ms
frontend-modules.min.js
92 ms
wp-polyfill-inert.min.js
85 ms
regenerator-runtime.min.js
90 ms
wp-polyfill.min.js
91 ms
hooks.min.js
84 ms
i18n.min.js
88 ms
frontend.min.js
93 ms
waypoints.min.js
86 ms
core.min.js
88 ms
frontend.min.js
94 ms
elements-handlers.min.js
90 ms
gtm.js
241 ms
place
488 ms
logo
392 ms
Cream-Wordmark_120px.png
124 ms
circle.svg
526 ms
True-Australasia-Main.jpg
202 ms
True-Australasia-Main-819x1024.jpg
124 ms
Men.png
500 ms
atol_black.png
122 ms
MEMBER_STAMP_WALPOLE.png
522 ms
pieter-van-noorden-oQ_fU_sK5zA-unsplash-768x1152.jpg
201 ms
True-Asia-Inspiration-768x1152.jpg
199 ms
True-Europe-Feature-768x1152.jpg
287 ms
LA_LatAm_Header_AWL-768x512.jpg
758 ms
PO_Polar-Header-768x512.jpg
286 ms
Leaf_Emerald-e1704969825394-300x200.png
313 ms
TTF-Deep-Ocean-Teal-Marque-with-Tagline-No-Background.png
339 ms
B-Corp-Logo-Black-RGB_350.png
722 ms
seawilding-logo-transparent.png
854 ms
kenya-2-1.jpg
1114 ms
bckfwd-r4l_VwRHDY4-unsplash.jpg
1222 ms
Uyuni-27.jpg
534 ms
Mokoro-Excursion-Botswana-768x431.jpg
1052 ms
True-Travel-Asia-scaled.jpg
733 ms
True-Middle-East-Banner.jpg
745 ms
Asset-1.png
756 ms
Cream-Full-Logo-Large-Formats.png
764 ms
MEMBER_STAMP_WALPOLE-qhzynmhnxyto1y8pklvzjnuo2deciuaevu3c733i8y.png
765 ms
atol_white-qhzynmho4jn4sngrqg0nv2of7z13blrrrls44ao394.png
772 ms
B-Corp-Logo-White-RGB_150.png
773 ms
fa-solid-900.woff
1330 ms
fa-regular-400.woff
1148 ms
fa-brands-400.woff
1312 ms
pxiByp8kv8JHgFVrLDz8Z1xlEw.woff
138 ms
pxiByp8kv8JHgFVrLFj_Z1xlEw.woff
211 ms
pxiGyp8kv8JHgFVrLPTucHtG.woff
225 ms
pxiEyp8kv8JHgFVrJJfedA.woff
250 ms
font
250 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
250 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
250 ms
pxiByp8kv8JHgFVrLDD4Z1xlEw.woff
249 ms
pxiByp8kv8JHgFVrLBT5Z1xlEw.woff
250 ms
75aa83c6.js
339 ms
js
113 ms
destination
115 ms
fbevents.js
112 ms
js
57 ms
region
25 ms
region
29 ms
2.4.13.css
12 ms
true.travel accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
true.travel 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
Page has valid source maps
true.travel SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 True.travel 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 True.travel 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.
true.travel
Open Graph data is detected on the main page of True. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: