82.8 sec in total
1.3 sec
66.2 sec
15.2 sec
Click here to check amazing Princess content for United States. Otherwise, check out these important facts you probably never knew about princess.com
Let Princess take you on a cruise vacation to the Caribbean, Alaska, Europe & many more destinations. View our best cruise deals and offers.
Visit princess.comWe analyzed Princess.com page load time and found that the first response time was 1.3 sec and then it took 81.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
princess.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value12.9 s
0/100
25%
Value9.7 s
11/100
10%
Value8,260 ms
0/100
30%
Value0.037
100/100
15%
Value17.7 s
4/100
10%
1337 ms
849 ms
684 ms
799 ms
1644 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 31% of them (44 requests) were addressed to the original Princess.com, 8% (11 requests) were made to Dpm.demdex.net and 5% (7 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (21.6 sec) belongs to the original domain Princess.com.
Page size can be reduced by 3.6 MB (48%)
7.5 MB
3.9 MB
In fact, the total size of Princess.com main page is 7.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. 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. Javascripts take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 136.7 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 136.7 kB or 83% of the original size.
Potential reduce by 69.8 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. Princess images are well optimized though.
Potential reduce by 2.4 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 2.4 MB or 70% of the original size.
Potential reduce by 984.7 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. Princess.com needs all CSS files to be minified and compressed as it can save up to 984.7 kB or 58% of the original size.
Number of requests can be reduced by 91 (74%)
123
32
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Princess. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.princess.com
1337 ms
princess.combined.css
849 ms
responsive_header_footer.css
684 ms
promo-block.css
799 ms
home_page.css
1644 ms
fnc.searchwidget.css
1646 ms
cms.css
1727 ms
princess-libs.combined.js
2174 ms
perc_p13n_delivery.js
1726 ms
satelliteLib-775514a2e3a100a5e76454e9a31fc6c16eacedd4.js
3359 ms
princess-plugins.combined.js
2075 ms
jquery.jsonp-2.1.4.min.js
1624 ms
jquery.sprintf.js
1742 ms
fnc.searchwidget.js
3061 ms
promo-block.js
3333 ms
home.js
3061 ms
responsive_header_footer.js
3059 ms
jquery.cycle2.min.js
3370 ms
jquery.cycle2.carousel.min.js
3303 ms
jquery.cycle2.swipe.min.js
3304 ms
cms.js
3303 ms
getLocale.do
3129 ms
adrum.js
395 ms
mbox-contents-db927befec8644cbaa815a51079f555f612e235b.js
1189 ms
CtjSgFbzIK0s3AAJ
1585 ms
target.js
1841 ms
rd
432 ms
ajax
2060 ms
id
2185 ms
core.js
8269 ms
8282 ms
princess-logo_header.svg
3486 ms
ocean-hp-640x480.jpg
1175 ms
5-reasons-to-cruise-640.jpg
1175 ms
dest5.html
7867 ms
gtm.js
7964 ms
sprite_pc-icons.svg
2773 ms
ajax_loader.gif
2772 ms
f3a02463-b43f-48da-9dcb-90e7d2f103b1.js
8108 ms
mm6f8BfWASug=
769 ms
BHzTJ9MLlN8CLJpODA==
352 ms
kx0JCz0AWvdw1JV8i8p+miNH4AMV7eePol4Js+Hl+g7CeU4U3o
189 ms
6468 ms
activityi;src=6203862;type=princ0;cat=globa00;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=7729661606717.8545
12020 ms
3710 ms
3771 ms
3770 ms
analytics.js
9271 ms
footer-horizontal-divider.png
697 ms
sprite_header-nav-footer.png
1491 ms
10416 ms
pixel
6773 ms
wtsyxuhuynEBbpajna-R.js
12942 ms
jquery.validate.min.js
5959 ms
make-request.js
5890 ms
deliver
15573 ms
deliver
18946 ms
deliver
18944 ms
deliver
15533 ms
deliver
19025 ms
site-search-form.js
9650 ms
deliver
16774 ms
deletePersistentCookies.do
7634 ms
addthis_widget.js
12957 ms
searchWidget.do
21557 ms
f.js
11855 ms
satellite-5873400a64746d6ecb003e40.html
4888 ms
satellite-58733ec164746d2b58002eed.html
7769 ms
s-code-contents-b47972305f2cab538c31d3b96c8ef0282d799b40.js
9088 ms
satellite-586cc23664746d16db004679.html
8128 ms
visa-cc.jpg
5309 ms
onesource_logo.png
5261 ms
ibs:dpid=21&dpuuid=163861302439001092580
4272 ms
ibs:dpid=420&dpuuid=59aebe98f46d0dc2
7208 ms
generic
10280 ms
ibs:dpid=601&dpuuid=243332072760&random=1504624286
6334 ms
AkGRUrs
29 ms
collect
3281 ms
collect
11028 ms
validate-settings.js
3214 ms
fbevents.js
12356 ms
ibs:dpid=771&dpuuid=CAESEOPcq4M_hDJkY_aUsrDMxZk&google_cver=1
3055 ms
cc
14953 ms
activityi;src=5879493;type=remar0;cat=princ0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=398709077853.7095
10710 ms
iframe_api
13085 ms
json
12821 ms
generic
4847 ms
picturefill.min.js
2628 ms
NAM-SDD2017-360x360.jpg
2595 ms
transparent-pixel.gif
2488 ms
ibs:dpid=903&dpuuid=1688b7d2-7eeb-4586-bf1f-d8a6b6ab9110
3074 ms
ibs:dpid=30646
6902 ms
ec.js
5820 ms
ibs:dpid=782&dpuuid=Wa6_qAAAAHhAt0X5&_test=Wa6_qAAAAITcYXxO
5372 ms
pixel
5372 ms
ibs:dpid=640&dpuuid=xvxcfmbe0yfih&ev=xvxcfmbe0yfih&pid=534889&do=add
5371 ms
502940306572289
4454 ms
ibs:dpid=30064&dpuuid=2yVzaPSNhgOZiaIFEPjAPXVLCXHun5a3TwR38TBlASM8
4453 ms
996079500421447
6978 ms
lb
8233 ms
Mnum=1516
8319 ms
8233 ms
8231 ms
ibs:dpid=6835&dpuuid=UP82b81014-924c-11e7-a719-06589fd1ac7a
6612 ms
arrows.png
4280 ms
nam-Holiday2017-360x360.jpg
2208 ms
nam-ocean-v2-360x360.jpg
2208 ms
NAM-SDD2017-1600.jpg
4539 ms
ocean-ada-1600.jpg
4539 ms
NAM-Holiday17-v2-1600.jpg
5412 ms
b.php
4265 ms
Pug
4598 ms
4283 ms
collect
1815 ms
www-widgetapi.js
2974 ms
s78861019834876
915 ms
collect
1115 ms
collect
1706 ms
rum
1093 ms
502940306572289
1089 ms
2069 ms
2417 ms
collect
947 ms
tap.php
925 ms
Mnum=1516
884 ms
sd
883 ms
1248 ms
754 ms
pixel.gif
628 ms
tr
310 ms
appnexus
87 ms
rum
121 ms
pixel.gif
3045 ms
sync.html
3880 ms
_ate.track.config_resp
4893 ms
300lo.json
4702 ms
collect
102 ms
adrum-ext.206c403a1a532b310b15ea4509f4902b.js
4332 ms
sh.886bb8b2fb82aeab6a228151.html
1560 ms
pixel.gif
1326 ms
event
1784 ms
1728 ms
sync.js
2102 ms
princess.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.
princess.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
Page has valid source maps
princess.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Princess.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 Princess.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.
princess.com
Open Graph description is not detected on the main page of Princess. 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: