Tools & Wizards About Us
disneycruiselineblog.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

disneycruiselineblog.com

The Disney Cruise Line Blog • an unofficial Disney Cruise Line news, information, weather, and photo blog.

Page Load Speed

4 sec in total

First Response

1.1 sec

Resources Loaded

2.2 sec

Page Rendered

708 ms

disneycruiselineblog.com screenshot

About Website

Welcome to disneycruiselineblog.com homepage info - get ready to check Disney Cruise Line Blog best content for United States right away, or after learning these important things about disneycruiselineblog.com

Disney Cruise Line, Blog, News, Information, Photos, Photography, Dream, Fantasy, Magic, Wonder, Wish, Treasure, Castaway Cay, Lighthouse Point, Port Canaveral, DCL, reviews, planning, food, excursion...

Visit disneycruiselineblog.com

Key Findings

We analyzed Disneycruiselineblog.com page load time and found that the first response time was 1.1 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

disneycruiselineblog.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value2,900 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.119

85/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

disneycruiselineblog.com

1110 ms

wp-emoji-release.min.js

16 ms

style.css

12 ms

genericons.css

9 ms

responsive.css

10 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 30% of them (33 requests) were addressed to the original Disneycruiselineblog.com, 15% (16 requests) were made to Pixel.wp.com and 5% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Disneycruiselineblog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 545.2 kB (26%)

Content Size

2.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 121.4 kB

  • Original 143.1 kB
  • After minification 133.2 kB
  • After compression 21.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 121.4 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 18.6 kB

  • Original 1.4 MB
  • After minification 1.3 MB

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. Disney Cruise Line Blog images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 223.2 kB

  • Original 393.8 kB
  • After minification 363.7 kB
  • After compression 170.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 223.2 kB or 57% of the original size.

CSS Optimization

-80%

Potential reduce by 182.0 kB

  • Original 227.8 kB
  • After minification 197.9 kB
  • After compression 45.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. Disneycruiselineblog.com needs all CSS files to be minified and compressed as it can save up to 182.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (67%)

Requests Now

106

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

disneycruiselineblog.com

disneycruiselineblog.com

1110 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

16 ms

style.css

style.css

12 ms

genericons.css

genericons.css

9 ms

responsive.css

responsive.css

10 ms

dark.css

dark.css

8 ms

jetpack.css

jetpack.css

18 ms

lightbox.min.css

lightbox.min.css

15 ms

jquery.js

jquery.js

23 ms

jquery-migrate.min.js

jquery-migrate.min.js

15 ms

jquery.sidr.min.js

jquery.sidr.min.js

15 ms

tabs.js

tabs.js

22 ms

analytics.js

analytics.js

17 ms

social-profiles.png

social-profiles.png

56 ms

DCLBlog-Website-Header-Magic.jpg

DCLBlog-Website-Header-Magic.jpg

56 ms

TCM-Classic-Cruise-Itinerary-Fantasy-2016.jpg

TCM-Classic-Cruise-Itinerary-Fantasy-2016.jpg

59 ms

DCLBlog_SpecialOffers.png

DCLBlog_SpecialOffers.png

59 ms

Mazatlan-Returns-Wonder-Tweet-20160211.jpg

Mazatlan-Returns-Wonder-Tweet-20160211.jpg

60 ms

DCL-Voluntears-Supply-Zone-for-Teachers-Feb-2016.jpg

DCL-Voluntears-Supply-Zone-for-Teachers-Feb-2016.jpg

62 ms

DCL-Disney-Magic-Villefranche-France.jpg

DCL-Disney-Magic-Villefranche-France.jpg

67 ms

adsbygoogle.js

adsbygoogle.js

52 ms

ads.js

ads.js

54 ms

jquery.cycle.js

jquery.cycle.js

55 ms

slideshow-shortcode.js

slideshow-shortcode.js

57 ms

devicepx-jetpack.js

devicepx-jetpack.js

77 ms

gprofiles.js

gprofiles.js

77 ms

wpgroho.js

wpgroho.js

55 ms

fitvids.min.js

fitvids.min.js

55 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

57 ms

catchflames-custom.min.js

catchflames-custom.min.js

57 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

56 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

58 ms

wp-embed.min.js

wp-embed.min.js

57 ms

sharing.js

sharing.js

58 ms

e-201609.js

e-201609.js

49 ms

PersonalNavigators_Alternate.png

PersonalNavigators_Alternate.png

58 ms

DCLBlog_Porthole_Amazon.png

DCLBlog_Porthole_Amazon.png

58 ms

loading.gif

loading.gif

57 ms

collect

collect

589 ms

ads-common.js

ads-common.js

25 ms

Genericons.svg

Genericons.svg

422 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

13 ms

ca-pub-2088052768147510.js

ca-pub-2088052768147510.js

584 ms

zrt_lookup.html

zrt_lookup.html

576 ms

show_ads_impl.js

show_ads_impl.js

482 ms

cm

cm

464 ms

widgets.js

widgets.js

403 ms

hovercard.css

hovercard.css

148 ms

services.css

services.css

289 ms

share

share

298 ms

g.gif

g.gif

125 ms

count.json

count.json

135 ms

graph.facebook.com

graph.facebook.com

135 ms

share

share

311 ms

count.json

count.json

135 ms

graph.facebook.com

graph.facebook.com

275 ms

share

share

337 ms

count.json

count.json

133 ms

graph.facebook.com

graph.facebook.com

288 ms

share

share

418 ms

count.json

count.json

131 ms

graph.facebook.com

graph.facebook.com

271 ms

share

share

346 ms

count.json

count.json

130 ms

graph.facebook.com

graph.facebook.com

285 ms

g.gif

g.gif

100 ms

g.gif

g.gif

100 ms

g.gif

g.gif

98 ms

g.gif

g.gif

100 ms

g.gif

g.gif

100 ms

g.gif

g.gif

193 ms

g.gif

g.gif

111 ms

g.gif

g.gif

112 ms

g.gif

g.gif

111 ms

g.gif

g.gif

111 ms

g.gif

g.gif

110 ms

g.gif

g.gif

205 ms

g.gif

g.gif

207 ms

g.gif

g.gif

207 ms

g.gif

g.gif

196 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

219 ms

logo_bs_300x30.gif

logo_bs_300x30.gif

156 ms

169 ms

51ENctTSxaL._SX60_SY80_.jpg

51ENctTSxaL._SX60_SY80_.jpg

169 ms

41KqCrQ2fuL._SX60_SY80_.jpg

41KqCrQ2fuL._SX60_SY80_.jpg

168 ms

41uL4tOQsvL._SX60_SY80_.jpg

41uL4tOQsvL._SX60_SY80_.jpg

168 ms

51CtmBFO6uL._SX60_SY80_.jpg

51CtmBFO6uL._SX60_SY80_.jpg

170 ms

collect

collect

219 ms

ads

ads

206 ms

osd.js

osd.js

86 ms

ads

ads

246 ms

41uL4tOQsvL._OU01_SL80_PI47-percent,BottomRight,0,0_CR0,0,53,80_.jpg

41uL4tOQsvL._OU01_SL80_PI47-percent,BottomRight,0,0_CR0,0,53,80_.jpg

18 ms

ads

ads

231 ms

syndication

syndication

113 ms

345201287719170048

345201287719170048

208 ms

9543627242976437218

9543627242976437218

34 ms

abg.js

abg.js

37 ms

m_js_controller.js

m_js_controller.js

52 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

25 ms

x_button_blue2.png

x_button_blue2.png

7 ms

s

s

20 ms

10990795907302871027

10990795907302871027

38 ms

redir.html

redir.html

63 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

23 ms

favicon

favicon

52 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

29 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

8 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

9 ms

iframe.html

iframe.html

15 ms

ui

ui

50 ms

Accessibility Review

disneycruiselineblog.com accessibility score

86

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 do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

disneycruiselineblog.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

disneycruiselineblog.com SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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 Disneycruiselineblog.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 Disneycruiselineblog.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

disneycruiselineblog.com

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