6.9 sec in total
684 ms
5 sec
1.2 sec
Visit uniworld.com now to see the best up-to-date Uniworld content for United States and also check out these interesting facts you probably never knew about uniworld.com
From the rivers of Europe to exotic India, Vietnam, Cambodia, Peru & Egypt, Uniworld provides an intimate view of some of the world's oldest civilizations and their enduring treasures.
Visit uniworld.comWe analyzed Uniworld.com page load time and found that the first response time was 684 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
uniworld.com performance score
684 ms
5 ms
482 ms
31 ms
129 ms
Our browser made a total of 199 requests to load all elements on the main page. We found that 22% of them (43 requests) were addressed to the original Uniworld.com, 15% (30 requests) were made to Services.uniworld.com and 8% (15 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Uniworld.com.
Page size can be reduced by 2.9 MB (51%)
5.7 MB
2.8 MB
In fact, the total size of Uniworld.com main page is 5.7 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. 80% 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 212.8 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 65.3 kB, which is 26% 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 212.8 kB or 84% of the original size.
Potential reduce by 55.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. Uniworld images are well optimized though.
Potential reduce by 1.6 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.6 MB or 77% of the original size.
Potential reduce by 1.0 MB
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. Uniworld.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 82% of the original size.
Number of requests can be reduced by 87 (54%)
162
75
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uniworld. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
684 ms
font-awesome.min.css
5 ms
main.css
482 ms
jquery.min.js
31 ms
nky4zvk.js
129 ms
buttons.js
7 ms
affiliate.js
473 ms
javascript
580 ms
rrssb.min.js
184 ms
uniworld.com
125 ms
uni-logo.png
108 ms
uni.png
162 ms
uw_hero_ssmt_lobby.ashx
897 ms
feefo_logo_home.png
214 ms
question_tooltip_home.png
217 ms
uw_hallmarks_sc_unique_2.ashx
674 ms
uw_hallmarks_expertise.ashx
674 ms
uw_hallmarks_service.ashx
675 ms
uw_hallmarks_culinary.ashx
675 ms
choice_4_1_14_2.ashx
675 ms
uw_hallmarks_sustainability.ashx
816 ms
uw_homepage_video_branding2.ashx
1392 ms
uw_rivercruising_the_rivers_sa_350x350.ashx
815 ms
uw_rivercruising_effortless_travel_rr_350x350.ashx
816 ms
uw_rivercruising_health_wellness_rr_350x350.ashx
815 ms
uw_rivercruising_uniworld_cares_ssc_350x350.ashx
934 ms
img-overlay-close.png
891 ms
gtm.js
34 ms
QOmjMPb4r2KtctHy84EN64R8fuMGLtBkQACLQDUUI9SffVRrMUMdeMJ6Mk6f5Mb.woff
105 ms
2TNR2MbmJJ54IBQJy-NlYejQMFor-Y1ojXMVMmMz9jXffV1rMUMdeMJ6Mk6f5Mt.woff
562 ms
8ZTf7UMFjTdf161Cj0zb0flPTuVErMEj27aA_dRRuz6ffVWrMUMdeMJ6Mk6f5gI.woff
568 ms
9YNLL0bmRhcAAfTIrgAAAA=
49 ms
fontello.svg
784 ms
jNCXjSKoDFMhTJg8rcXbGgZbKMIgc_b4QeQf7uKoC0jffHQ3gsMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
567 ms
oNZ69EhOwKv4JlOw83vuuMa8AHujlCU6FvXIkov4K29ffHn3gsMdeMJ6Mk6g5gBfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
565 ms
K8T569KiNxpn5hHIyjrEjJUS26GTG8jQ7rTWxDB96pGffHV3gsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
701 ms
analytics.js
66 ms
conversion_async.js
66 ms
bat.js
58 ms
fbevents.js
516 ms
CivitaMed-webfont.woff
911 ms
fluid-embed.js
478 ms
CivitaMedIta-webfont.woff
794 ms
CivitaLig-webfont.woff
887 ms
580 ms
collect
401 ms
510 ms
Sitecore.js
717 ms
getAllAppDefault.esi
180 ms
collect
292 ms
170 ms
emoji.min.gz.css
71 ms
webfont.js
70 ms
588 ms
CivitaReg-webfont.woff
315 ms
europemap.ashx
386 ms
asia.ashx
312 ms
india.ashx
375 ms
russia.ashx
378 ms
holiday-europemap.ashx
468 ms
uw_offers_rr_family.ashx
558 ms
uw_offers_deck.ashx
558 ms
preair_euro_427x292.ashx
666 ms
uw_offers_ssmt_lobby.ashx
548 ms
ttc_white_01.ashx
578 ms
logotollman.ashx
582 ms
logotreadright.ashx
577 ms
img4.ashx
663 ms
flourish-center.png
668 ms
134 ms
158 ms
css
86 ms
getSegment.php
197 ms
checkOAuth.esi
75 ms
p.gif
184 ms
ga-audiences
51 ms
138 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
46 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
66 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
107 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
111 ms
ApplicationLog.js
101 ms
Sitecore.Analytics.Affiliate.js
159 ms
Sitecore.Content.Trigger.js
232 ms
Sitecore.Content.Injection.js
234 ms
t.dhj
46 ms
t.dhj
40 ms
cm
29 ms
15 ms
s-3271.xgi
12 ms
349 ms
hbpix
37 ms
7 ms
xrefid.xgi
5 ms
pixel
24 ms
2981
20 ms
integration.js
68 ms
newsletter-signup
187 ms
fancybox_overlay.png
135 ms
fluid.min.gz.1456439085.css
22 ms
uikit-widget.min.gz.1456439085.css
21 ms
https-rules.1456439085.min.gz.js
20 ms
fluid.1456439085.min.gz.js
30 ms
impressions.combine.8fc15d44.js
85 ms
piwik.js
65 ms
pins
328 ms
api
554 ms
jquery-2.1.3.min.js
166 ms
SiteCore.js
130 ms
p.gif
36 ms
fancybox_sprite.png
190 ms
nr-885.min.js
19 ms
3b3d1112a8
152 ms
94 ms
iframeResizer.min.js
92 ms
ajax_loader_blue.gif
450 ms
182 ms
Sitecore.Content.Modal.Styling.js
86 ms
bootstrap-theme.min.css
41 ms
bootstrap.min.js
43 ms
parsley.min.js
275 ms
iframeResizer.contentWindow.min.js
279 ms
main.css
701 ms
Sitecore.js
345 ms
Analytics.js
281 ms
Application.js
356 ms
Application.Context.QueryString.js
362 ms
Application.Services.js
361 ms
Controls.js
361 ms
Common.css
422 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
19 ms
buttons.ab966a004186897711de4a5ed256c924.css
11 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
12 ms
affiliate.js
182 ms
12519182_479000382302239_661307221_n.jpg
164 ms
avatar-mask.png
128 ms
12545520_1726714217548000_1629031542_a.jpg
212 ms
1610093_10153688316726005_4969029220502258914_n.jpg
212 ms
10576967_10152577473241005_6616644722675608017_n.jpg
214 ms
10375784_649257781829733_742641181_a.jpg
191 ms
12277620_467624736742551_1065344677_a.jpg
173 ms
12063160_808389309283193_2055391267_a.jpg
187 ms
12277620_467624736742551_1065344677_a.jpg
136 ms
12063160_808389309283193_2055391267_a.jpg
163 ms
10576967_10152577473241005_6616644722675608017_n.jpg
145 ms
tile-sprite.20150615.png
80 ms
image-loader.gif
64 ms
12545520_1726714217548000_1629031542_a.jpg
135 ms
10375784_649257781829733_742641181_a.jpg
132 ms
12519182_479000382302239_661307221_n.jpg
96 ms
12523746_451279181740121_1505230024_n.jpg
96 ms
12523746_451279181740121_1505230024_n.jpg
107 ms
12534170_981132248639758_1257029394_n.jpg
94 ms
12534170_981132248639758_1257029394_n.jpg
94 ms
12407572_471595386358095_1128814451_n.jpg
94 ms
12407572_471595386358095_1128814451_n.jpg
118 ms
917951_446873095501885_1077221197_n.jpg
120 ms
917951_446873095501885_1077221197_n.jpg
116 ms
10413156_1215438681817427_879484392_n.jpg
117 ms
10413156_1215438681817427_879484392_n.jpg
116 ms
10570181_965549236813863_1868297448_n.jpg
125 ms
10570181_965549236813863_1868297448_n.jpg
131 ms
1610093_10153688316726005_4969029220502258914_n.jpg
134 ms
services.uniworld.com
66 ms
fbds.js
42 ms
93 ms
collect
11 ms
collect
13 ms
QOmjMPb4r2KtctHy84EN64R8fuMGLtBkQACLQDUUI9SffVRrMUMdeMJ6Mk6f5Mb.woff
33 ms
jNCXjSKoDFMhTJg8rcXbGgZbKMIgc_b4QeQf7uKoC0jffHQ3gsMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
41 ms
oNZ69EhOwKv4JlOw83vuuMa8AHujlCU6FvXIkov4K29ffHn3gsMdeMJ6Mk6g5gBfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
54 ms
K8T569KiNxpn5hHIyjrEjJUS26GTG8jQ7rTWxDB96pGffHV3gsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
32 ms
2TNR2MbmJJ54IBQJy-NlYejQMFor-Y1ojXMVMmMz9jXffV1rMUMdeMJ6Mk6f5Mt.woff
56 ms
8ZTf7UMFjTdf161Cj0zb0flPTuVErMEj27aA_dRRuz6ffVWrMUMdeMJ6Mk6f5gI.woff
29 ms
2 ms
ga-audiences
16 ms
p.gif
30 ms
76 ms
92 ms
map_number
277 ms
map_number
33 ms
roundtrip.js
7 ms
OHJVH3KFJVDVRIIBO5KUWL.js
31 ms
out
11 ms
tr
10 ms
out
8 ms
out
10 ms
out
10 ms
out
15 ms
out
14 ms
out
14 ms
u.php
37 ms
adsct
83 ms
377928.gif
22 ms
pixel
50 ms
sync
19 ms
sd
13 ms
24 ms
in
5 ms
uniworld.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uniworld.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 Uniworld.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.
uniworld.com
Open Graph description is not detected on the main page of Uniworld. 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: