Tools & Wizards About Us
wickerman.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wickerman.com

Wicker Man Wooden Roller Coaster Ride | Alton Towers Resort

Page Load Speed

2.4 sec in total

First Response

416 ms

Resources Loaded

1.4 sec

Page Rendered

588 ms

wickerman.com screenshot

About Website

Click here to check amazing Wicker Man content for United Kingdom. Otherwise, check out these important facts you probably never knew about wickerman.com

Join the chosen ones and face Wicker Man. The Wicker Man ride is the world's most immersive roller coaster experience, fusing a wooden roller coaster with fire!

Visit wickerman.com

Key Findings

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

Performance Metrics

wickerman.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value5.9 s

47/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

416 ms

OtAutoBlock.js

63 ms

otSDKStub.js

74 ms

lazysizes.min.-v-2.0.0-hotfix.5063-v.js

36 ms

style.-v-2.0.0-hotfix.5063-v.css

91 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wickerman.com, 9% (5 requests) were made to Unpkg.com and 6% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (612 ms) relates to the external source Altontowers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 315.3 kB (37%)

Content Size

849.4 kB

After Optimization

534.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wickerman.com main page is 849.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 302.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 204.4 kB

  • Original 237.9 kB
  • After minification 177.2 kB
  • After compression 33.5 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 60.7 kB, which is 25% 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 204.4 kB or 86% of the original size.

Image Optimization

-17%

Potential reduce by 38.5 kB

  • Original 223.0 kB
  • After minification 184.5 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. Obviously, Wicker Man needs image optimization as it can save up to 38.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 50.9 kB

  • Original 302.5 kB
  • After minification 302.5 kB
  • After compression 251.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 50.9 kB or 17% of the original size.

CSS Optimization

-25%

Potential reduce by 21.5 kB

  • Original 86.0 kB
  • After minification 86.0 kB
  • After compression 64.5 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. Wickerman.com needs all CSS files to be minified and compressed as it can save up to 21.5 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (42%)

Requests Now

48

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

416 ms

OtAutoBlock.js

OtAutoBlock.js

63 ms

otSDKStub.js

otSDKStub.js

74 ms

lazysizes.min.-v-2.0.0-hotfix.5063-v.js

lazysizes.min.-v-2.0.0-hotfix.5063-v.js

36 ms

style.-v-2.0.0-hotfix.5063-v.css

style.-v-2.0.0-hotfix.5063-v.css

91 ms

tippy.js@6

tippy.js@6

72 ms

index.-v-2.0.0-hotfix.5063-v.js

index.-v-2.0.0-hotfix.5063-v.js

52 ms

jquery-3.6.0.min.-v-2.0.0-hotfix.5063-v.js

jquery-3.6.0.min.-v-2.0.0-hotfix.5063-v.js

76 ms

jquery.validate.min.-v-2.0.0-hotfix.5063-v.js

jquery.validate.min.-v-2.0.0-hotfix.5063-v.js

59 ms

jquery.validate.unobtrusive.-v-2.0.0-hotfix.5063-v.js

jquery.validate.unobtrusive.-v-2.0.0-hotfix.5063-v.js

72 ms

jquery.matchHeight.min.-v-2.0.0-hotfix.5063-v.js

jquery.matchHeight.min.-v-2.0.0-hotfix.5063-v.js

78 ms

core.-v-2.0.0-hotfix.5063-v.js

core.-v-2.0.0-hotfix.5063-v.js

121 ms

accesso.js

accesso.js

72 ms

merlin.owlCarousel.-v-2.0.0-hotfix.5063-v.js

merlin.owlCarousel.-v-2.0.0-hotfix.5063-v.js

73 ms

moment.-v-2.0.0-hotfix.5063-v.js

moment.-v-2.0.0-hotfix.5063-v.js

179 ms

zebra_datepicker.src.-v-2.0.0-hotfix.5063-v.js

zebra_datepicker.src.-v-2.0.0-hotfix.5063-v.js

120 ms

merlin.datepicker.-v-2.0.0-hotfix.5063-v.js

merlin.datepicker.-v-2.0.0-hotfix.5063-v.js

121 ms

merlin.guestincrementer.-v-2.0.0-hotfix.5063-v.js

merlin.guestincrementer.-v-2.0.0-hotfix.5063-v.js

118 ms

merlin.toolbarsutils.-v-2.0.0-hotfix.5063-v.js

merlin.toolbarsutils.-v-2.0.0-hotfix.5063-v.js

117 ms

merlin.newIsoBookingToolbar.-v-2.0.0-hotfix.5063-v.js

merlin.newIsoBookingToolbar.-v-2.0.0-hotfix.5063-v.js

177 ms

owl.carousel.min.js

owl.carousel.min.js

209 ms

core@2.11.8

core@2.11.8

29 ms

tippy.js@6.3.7

tippy.js@6.3.7

55 ms

b02df832-dd68-48c4-bb17-3100b6423fbb.json

b02df832-dd68-48c4-bb17-3100b6423fbb.json

53 ms

popper.min.js

popper.min.js

46 ms

tippy-bundle.umd.min.js

tippy-bundle.umd.min.js

44 ms

alton-towers-resort-logo.png

alton-towers-resort-logo.png

191 ms

wickerman.png

wickerman.png

550 ms

06_wickerman_theming.jpg

06_wickerman_theming.jpg

190 ms

01_wickerman_armsup.jpg

01_wickerman_armsup.jpg

134 ms

02_wickerman_structure.jpg

02_wickerman_structure.jpg

132 ms

03_wickerman_rideinthedark.jpg

03_wickerman_rideinthedark.jpg

189 ms

04_wickerman_structurewide.jpg

04_wickerman_structurewide.jpg

189 ms

05_wickerman_entrance.jpg

05_wickerman_entrance.jpg

189 ms

06_wickerman_theming.jpg

06_wickerman_theming.jpg

195 ms

03_wickerman_rideinthedark.jpg

03_wickerman_rideinthedark.jpg

253 ms

02_wickerman_structure.jpg

02_wickerman_structure.jpg

189 ms

link-aa-rectangle-purple-v2.png

link-aa-rectangle-purple-v2.png

194 ms

merlin_primary_logo.png

merlin_primary_logo.png

196 ms

tc_botb_mustard_bf-logo_ll_2024_rgb.png

tc_botb_mustard_bf-logo_ll_2024_rgb.png

196 ms

appstore.png

appstore.png

196 ms

google-play.png

google-play.png

199 ms

youtube.svg

youtube.svg

201 ms

instagram.svg

instagram.svg

197 ms

facebook.svg

facebook.svg

200 ms

twitter.svg

twitter.svg

203 ms

health.png

health.png

202 ms

location

location

185 ms

02_wickerman_structure.jpg

02_wickerman_structure.jpg

155 ms

wickerman-footer-v2.jpg

wickerman-footer-v2.jpg

188 ms

atr-pattern-repeat.png

atr-pattern-repeat.png

140 ms

shim.html

shim.html

89 ms

Aleo-Regular.ttf

Aleo-Regular.ttf

612 ms

LT-Funk.otf

LT-Funk.otf

466 ms

Accessibility Review

wickerman.com accessibility score

93

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

wickerman.com 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

wickerman.com SEO score

93

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

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

wickerman.com

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