Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

wildernessprincess.net

The Wilderness Princess | Complete Guide to Enchanted Camping in Disney's Fort Wilderness + Florida

Page Load Speed

23.6 sec in total

First Response

204 ms

Resources Loaded

22.2 sec

Page Rendered

1.3 sec

wildernessprincess.net screenshot

About Website

Click here to check amazing Wilderness Princess content. Otherwise, check out these important facts you probably never knew about wildernessprincess.net

Ultimate everything guide to Disney's Fort Wilderness Campground with site details, gourmet camping recipes, latest discounts and much more by would-be princess who fled the Magic Kingdom for the...

Visit wildernessprincess.net

Key Findings

We analyzed Wildernessprincess.net page load time and found that the first response time was 204 ms and then it took 23.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.

Performance Metrics

wildernessprincess.net performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value4,690 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.319

36/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

wildernessprincess.net

204 ms

wildernessprincess.net

1345 ms

style.min.css

79 ms

mediaelementplayer-legacy.min.css

94 ms

wp-mediaelement.min.css

86 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 31% of them (50 requests) were addressed to the original Wildernessprincess.net, 20% (32 requests) were made to C0.wp.com and 15% (24 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Ir-na.amazon-adsystem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 307.6 kB (5%)

Content Size

6.1 MB

After Optimization

5.8 MB

In fact, the total size of Wildernessprincess.net main page is 6.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. 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 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 174.7 kB

  • Original 210.1 kB
  • After minification 205.7 kB
  • After compression 35.3 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 174.7 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 21 B

  • Original 5.3 MB
  • After minification 5.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. Wilderness Princess images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 95.8 kB

  • Original 430.4 kB
  • After minification 430.3 kB
  • After compression 334.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 95.8 kB or 22% of the original size.

CSS Optimization

-23%

Potential reduce by 37.0 kB

  • Original 163.1 kB
  • After minification 157.7 kB
  • After compression 126.1 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. Wildernessprincess.net needs all CSS files to be minified and compressed as it can save up to 37.0 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 107 (69%)

Requests Now

155

After Optimization

48

The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wilderness 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 66 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

wildernessprincess.net accessibility score

83

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-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

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

wildernessprincess.net best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wildernessprincess.net SEO score

77

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

High

Image elements do not have [alt] attributes

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 Wildernessprincess.net 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 Wildernessprincess.net 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

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