2.6 sec in total
535 ms
1.7 sec
361 ms
Visit queenelizabethnationalpark.com now to see the best up-to-date Queen Elizabeth National Park content for Uganda and also check out these interesting facts you probably never knew about queenelizabethnationalpark.com
Welcome to Queen Elizabeth National Park guide, covering the top things to do, the destinations to visit, Uganda safari companies and more.
Visit queenelizabethnationalpark.comWe analyzed Queenelizabethnationalpark.com page load time and found that the first response time was 535 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.
queenelizabethnationalpark.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value13.5 s
0/100
25%
Value9.3 s
12/100
10%
Value890 ms
32/100
30%
Value0.226
55/100
15%
Value11.1 s
20/100
10%
535 ms
43 ms
46 ms
48 ms
119 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 72% of them (46 requests) were addressed to the original Queenelizabethnationalpark.com, 14% (9 requests) were made to Fonts.gstatic.com and 11% (7 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (535 ms) belongs to the original domain Queenelizabethnationalpark.com.
Page size can be reduced by 567.6 kB (36%)
1.6 MB
1.0 MB
In fact, the total size of Queenelizabethnationalpark.com main page is 1.6 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. 55% of websites need less resources to load. Images take 879.6 kB which makes up the majority of the site volume.
Potential reduce by 36.4 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. This page needs HTML code to be minified as it can gain 5.2 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 36.4 kB or 84% of the original size.
Potential reduce by 15.5 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. Queen Elizabeth National Park images are well optimized though.
Potential reduce by 272.6 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 272.6 kB or 69% of the original size.
Potential reduce by 243.0 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. Queenelizabethnationalpark.com needs all CSS files to be minified and compressed as it can save up to 243.0 kB or 87% of the original size.
Number of requests can be reduced by 40 (75%)
53
13
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Queen Elizabeth National Park. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
www.queenelizabethnationalpark.com
535 ms
style.css
43 ms
reset.css
46 ms
framework.css
48 ms
layout.css
119 ms
print.css
47 ms
www.queenelizabethnationalpark.com
345 ms
styles.css
56 ms
default.css
58 ms
font-awesome.min.css
75 ms
otw-blog-manager.css
95 ms
otw-grid.css
112 ms
custom.css
363 ms
jquery.js
154 ms
jquery-migrate.min.js
124 ms
jquery.easing.1.3.js
130 ms
thb.lib.js
130 ms
swfobject.js
131 ms
froogaloop.min.js
149 ms
jquery.mobilemenu.js
150 ms
script.js
151 ms
jquery.fancybox.min.js
168 ms
jquery.flexslider.min.js
169 ms
jquery.infinitescroll.min.js
170 ms
jquery.isotope.min.js
176 ms
pixastic.custom.min.js
193 ms
jquery.fitvids.js
192 ms
otw-bm-list-3-custom.css
173 ms
css
26 ms
otw-bm-list-2-custom.css
178 ms
otw-bm-list-1-custom.css
195 ms
comment-reply.min.js
196 ms
jquery.form.min.js
197 ms
scripts.js
201 ms
script.js
220 ms
wp-embed.min.js
218 ms
css
16 ms
css
26 ms
css
26 ms
css
25 ms
wp-emoji-release.min.js
129 ms
css
14 ms
css
15 ms
qu.jpg
51 ms
1.jpg
319 ms
gettingthere1_1409927830_220X120_c_c_1_FFFFFF.jpg
51 ms
wheretostay_1409928352_220X120_c_c_1_FFFFFF.jpg
52 ms
whattosee_1409928302_220X120_c_c_1_FFFFFF.jpg
51 ms
uganda_1447088103_220X120_c_c_1_FFFFFF.jpg
52 ms
Queen-birdwatching_1310062606_220X120_c_c_1_FFFFFF.jpg
63 ms
Queen-chimpanzee-tracking_1310062606_220X120_c_c_1_FFFFFF.jpg
63 ms
ishasha_1447088209_220X120_c_c_1_FFFFFF.jpg
63 ms
Queen-Katwe-woprks_1310062606_220X120_c_c_1_FFFFFF.jpg
64 ms
K6ngFdK5haaaRGBV8waDwA.ttf
11 ms
nHiQo1BypvYzt95zlPq1TvesZW2xOQ-xsNqO47m55DA.ttf
24 ms
yAXhog6uK3bd3OwBILv_SKCWcynf_cDxXwCLxiixG1c.ttf
24 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
23 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
24 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
24 ms
mmk6ioesnTrEky_Zb92E5gd8ZphFIbDoTMp_nPGYQR4.ttf
171 ms
Et-v_QIck3adV65yIaqlhg.ttf
172 ms
Ww23LQNlhn4dAm9uegPaXy3USBnSvpkopQaUR-2r7iU.ttf
171 ms
counter.js
19 ms
t.php
156 ms
queenelizabethnationalpark.com accessibility score
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
queenelizabethnationalpark.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
queenelizabethnationalpark.com 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 Queenelizabethnationalpark.com 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 Queenelizabethnationalpark.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.
queenelizabethnationalpark.com
Open Graph data is detected on the main page of Queen Elizabeth National Park. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: