Tools & Wizards About Us
funship.com screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

funship.com

Cruises | Carnival Cruise Deals: Caribbean, Bahamas, Alaska, Mexico

Page Load Speed

1.6 sec in total

First Response

159 ms

Resources Loaded

1.3 sec

Page Rendered

199 ms

funship.com screenshot

About Website

Visit funship.com now to see the best up-to-date Funship content and also check out these interesting facts you probably never knew about funship.com

Carnival cruise deals and cruise packages to the most popular destinations. Find great deals and specials on Caribbean, The Bahamas, Alaska, and Mexico cruises.

Visit funship.com

Key Findings

We analyzed Funship.com page load time and found that the first response time was 159 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

funship.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value44.8 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value11,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.599

11/100

15%

TTI (Time to Interactive)

Value42.4 s

0/100

10%

Network Requests Diagram

funship.com

159 ms

www.carnival.com

87 ms

css

43 ms

styles

83 ms

upgrade

59 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Funship.com, 77% (50 requests) were made to Carnival.com and 6% (4 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (451 ms) relates to the external source Carnival.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 953.1 kB (54%)

Content Size

1.8 MB

After Optimization

810.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Funship.com main page is 1.8 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. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.2 kB

  • Original 64.9 kB
  • After minification 56.3 kB
  • After compression 14.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 8.6 kB, which is 13% 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 50.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 192.8 kB
  • After minification 192.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. Funship images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 837.7 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 549.4 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 837.7 kB or 60% of the original size.

CSS Optimization

-55%

Potential reduce by 65.2 kB

  • Original 119.0 kB
  • After minification 119.0 kB
  • After compression 53.8 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. Funship.com needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (73%)

Requests Now

52

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funship. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

funship.com

funship.com

159 ms

www.carnival.com

www.carnival.com

87 ms

css

css

43 ms

styles

styles

83 ms

upgrade

upgrade

59 ms

index.min.js

index.min.js

48 ms

homepage_nbg_bg.js

homepage_nbg_bg.js

76 ms

urgency.min.css

urgency.min.css

48 ms

Carnival.AppResources.Core.en.axd

Carnival.AppResources.Core.en.axd

47 ms

main.css

main.css

57 ms

index.min.css

index.min.css

65 ms

styles

styles

75 ms

vendor.min.css

vendor.min.css

62 ms

widget.min.css

widget.min.css

146 ms

ccl-utilities.iife.js

ccl-utilities.iife.js

75 ms

carnival.tracking.js

carnival.tracking.js

78 ms

carnival.tracking.coreweb.js

carnival.tracking.coreweb.js

144 ms

svg4everybody.min.js

svg4everybody.min.js

158 ms

Carnival.ComponentResources.axd

Carnival.ComponentResources.axd

165 ms

vendor.min.js

vendor.min.js

167 ms

widget.min.js

widget.min.js

270 ms

jquery.devbridgeAutocomplete-custom.js

jquery.devbridgeAutocomplete-custom.js

182 ms

ccl-site-search.js

ccl-site-search.js

182 ms

header-utility.js

header-utility.js

183 ms

ccl.sso.js

ccl.sso.js

185 ms

ccl.userLogin.js

ccl.userLogin.js

184 ms

ccl.header2013.loginNavSection.js

ccl.header2013.loginNavSection.js

184 ms

ccl-navigation-asyncCalls.js

ccl-navigation-asyncCalls.js

186 ms

styleguide.css

styleguide.css

185 ms

react.production.min.js

react.production.min.js

38 ms

react-dom.production.min.js

react-dom.production.min.js

48 ms

bundle.js

bundle.js

188 ms

library

library

186 ms

urgency.min.js

urgency.min.js

190 ms

personalizer.js

personalizer.js

190 ms

homepage

homepage

193 ms

main.js

main.js

194 ms

seKEkMYnI

seKEkMYnI

193 ms

react.production.min.js

react.production.min.js

21 ms

react-dom.production.min.js

react-dom.production.min.js

12 ms

YYZC5-9SJ3E-WBPEW-9KUY8-9QZWF

YYZC5-9SJ3E-WBPEW-9KUY8-9QZWF

67 ms

aksb.min.js

aksb.min.js

59 ms

icon-ccl-card-tout.svg

icon-ccl-card-tout.svg

46 ms

australia-tout.png

australia-tout.png

45 ms

icon-calendar-tout.svg

icon-calendar-tout.svg

49 ms

0913-tout.jpg

0913-tout.jpg

47 ms

config.json

config.json

429 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

335 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

397 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

445 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

446 ms

getqualifierspersistent

getqualifierspersistent

135 ms

search

search

78 ms

tempostd-heavycondensed-webfont.woff

tempostd-heavycondensed-webfont.woff

131 ms

tempostd-heavycondensed-webfont.woff

tempostd-heavycondensed-webfont.woff

131 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

149 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

451 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

146 ms

homepage

homepage

176 ms

utag.js

utag.js

84 ms

couple-red-chair.jpg

couple-red-chair.jpg

45 ms

fun-ones-wavy-background-blue-b1.jpg

fun-ones-wavy-background-blue-b1.jpg

25 ms

fun-ones-wavy-background-blue-b2.jpg

fun-ones-wavy-background-blue-b2.jpg

23 ms

fun-ones-wavy-background-blue-b3.jpg

fun-ones-wavy-background-blue-b3.jpg

179 ms

homepage-main-banners-css-2.ashx

homepage-main-banners-css-2.ashx

21 ms

Accessibility Review

funship.com accessibility score

93

Accessibility Issues

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

High

[aria-*] attributes are not valid or misspelled

Best Practices

funship.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

funship.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funship.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 Funship.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.

Social Sharing Optimization

funship.com

Open Graph data is detected on the main page of Funship. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: