Tools & Wizards About Us
ripleyspei.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ripleyspei.com

Ripley's Believe It or Not! Cavendish | Tickets, Hours, Events

Page Load Speed

1.5 sec in total

First Response

15 ms

Resources Loaded

918 ms

Page Rendered

614 ms

ripleyspei.com screenshot

About Website

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

Explore Ripley's Believe It or Not! Cavendish, Canada. An attraction with hundreds of unbelievable but true artifacts, interactive games, and stories.

Visit ripleyspei.com

Key Findings

We analyzed Ripleyspei.com page load time and found that the first response time was 15 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

ripleyspei.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,440 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.039

99/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

ripleyspei.com

15 ms

ripleys-believe-it-or-not-cavendish-beach

409 ms

ad2a232467.js

124 ms

0.YOzQFZSs.css

25 ms

SocialIcon.TUx0ycm2.css

29 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ripleyspei.com, 71% (42 requests) were made to Ripleys.com and 10% (6 requests) were made to Ripleys.directus.app. The less responsive or slowest element that took the longest time to load (409 ms) relates to the external source Ripleys.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.5 kB (78%)

Content Size

237.5 kB

After Optimization

53.0 kB

  • HTML
  • JavaScript

In fact, the total size of Ripleyspei.com main page is 237.5 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. 25% of websites need less resources to load. HTML takes 232.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 184.5 kB

  • Original 232.4 kB
  • After minification 231.0 kB
  • After compression 47.9 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 184.5 kB or 79% of the original size.

JavaScript Optimization

-0%

Potential reduce by 7 B

  • Original 5.2 kB
  • After minification 5.2 kB
  • After compression 5.2 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 34 (81%)

Requests Now

42

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ripleyspei.com

ripleyspei.com

15 ms

ripleys-believe-it-or-not-cavendish-beach

ripleys-believe-it-or-not-cavendish-beach

409 ms

ad2a232467.js

ad2a232467.js

124 ms

0.YOzQFZSs.css

0.YOzQFZSs.css

25 ms

SocialIcon.TUx0ycm2.css

SocialIcon.TUx0ycm2.css

29 ms

Button.sqwr2u1V.css

Button.sqwr2u1V.css

30 ms

NavItem.4US0B8RQ.css

NavItem.4US0B8RQ.css

27 ms

ActionInput.i2SHuIFi.css

ActionInput.i2SHuIFi.css

28 ms

Sanitize.uygN9rXR.css

Sanitize.uygN9rXR.css

36 ms

1.l0ZAoBGg.css

1.l0ZAoBGg.css

41 ms

OverlayWrapper.u9LKNLAO.css

OverlayWrapper.u9LKNLAO.css

41 ms

SubmittingWrapper.tIDgbOlc.css

SubmittingWrapper.tIDgbOlc.css

43 ms

OverlayMultiControl.WqqaGWvz.css

OverlayMultiControl.WqqaGWvz.css

42 ms

14.6J66BOSd.css

14.6J66BOSd.css

48 ms

AttractionTypeSection.RNb8DrBZ.css

AttractionTypeSection.RNb8DrBZ.css

56 ms

validation.ac84i5dv.css

validation.ac84i5dv.css

55 ms

OverlayContentDropdown.nnVk_cox.css

OverlayContentDropdown.nnVk_cox.css

55 ms

FeatureCard.L6xnrMcI.css

FeatureCard.L6xnrMcI.css

57 ms

Embed.iKUVfq-p.css

Embed.iKUVfq-p.css

58 ms

StoryCard.wx5RPheV.css

StoryCard.wx5RPheV.css

66 ms

HeroContent.DB3xkcaq.css

HeroContent.DB3xkcaq.css

71 ms

VideoPlayer.yr9LOEEr.css

VideoPlayer.yr9LOEEr.css

98 ms

ResponsiveImage.wj2bZ255.css

ResponsiveImage.wj2bZ255.css

68 ms

WhatsInsideSection.fh-30i0N.css

WhatsInsideSection.fh-30i0N.css

75 ms

EventCard.IHFINqsk.css

EventCard.IHFINqsk.css

71 ms

DateInput.K5p5kMRK.css

DateInput.K5p5kMRK.css

79 ms

TabScroll.ExK3r8FQ.css

TabScroll.ExK3r8FQ.css

82 ms

Poster.H9bkfLIO.css

Poster.H9bkfLIO.css

96 ms

FlexibleEditorContent.5Xh_MXY-.css

FlexibleEditorContent.5Xh_MXY-.css

87 ms

SectionSelector.nqdss5gw.css

SectionSelector.nqdss5gw.css

91 ms

NotificationsStack.4mI5BK75.css

NotificationsStack.4mI5BK75.css

91 ms

Accordion.Xhbnnr7C.css

Accordion.Xhbnnr7C.css

97 ms

AccordionGrid.T2Uha1Qo.css

AccordionGrid.T2Uha1Qo.css

98 ms

NeedToKnow.iQ47bCkE.css

NeedToKnow.iQ47bCkE.css

105 ms

Map.O8fqah_r.css

Map.O8fqah_r.css

107 ms

17.-ROtnj4Z.css

17.-ROtnj4Z.css

107 ms

OverlayMultiSlide.RfkPtgyT.css

OverlayMultiSlide.RfkPtgyT.css

141 ms

api.js

api.js

11 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

46 ms

css2

css2

35 ms

e64fe823-a3b4-4ab0-b7ec-0a5cf548106b

e64fe823-a3b4-4ab0-b7ec-0a5cf548106b

16 ms

logo.svg

logo.svg

42 ms

logo-white.svg

logo-white.svg

57 ms

Swirly2.svg

Swirly2.svg

17 ms

3fe8422c-2d1e-4aae-95a0-2491d89ec1fc

3fe8422c-2d1e-4aae-95a0-2491d89ec1fc

11 ms

0c979f7c-d109-48dd-b24b-15513b0d5be7

0c979f7c-d109-48dd-b24b-15513b0d5be7

11 ms

26e3ce38-9939-4e9d-ae6c-ac00af279571

26e3ce38-9939-4e9d-ae6c-ac00af279571

11 ms

67d0709f-bcc3-4959-82c2-332301541aa8

67d0709f-bcc3-4959-82c2-332301541aa8

11 ms

0e20d436-5122-4f4a-887a-14645599527e

0e20d436-5122-4f4a-887a-14645599527e

11 ms

Swirly1.svg

Swirly1.svg

55 ms

MuseoSans_500.otf

MuseoSans_500.otf

67 ms

MuseoSans_700.otf

MuseoSans_700.otf

52 ms

MuseoSans_900.otf

MuseoSans_900.otf

78 ms

S6uyw4BMUTPHvxk6WQev.ttf

S6uyw4BMUTPHvxk6WQev.ttf

19 ms

S6u9w4BMUTPHh6UVew-FHi_o.ttf

S6u9w4BMUTPHh6UVew-FHi_o.ttf

31 ms

S6u9w4BMUTPHh50Xew-FHi_o.ttf

S6u9w4BMUTPHh50Xew-FHi_o.ttf

62 ms

S6u8w4BMUTPHjxswWyWtFCc.ttf

S6u8w4BMUTPHjxswWyWtFCc.ttf

66 ms

S6u_w4BMUTPHjxsI5wqPHA3q5d0.ttf

S6u_w4BMUTPHjxsI5wqPHA3q5d0.ttf

67 ms

S6u_w4BMUTPHjxsI3wiPHA3q5d0.ttf

S6u_w4BMUTPHjxsI3wiPHA3q5d0.ttf

67 ms

Accessibility Review

ripleyspei.com accessibility score

91

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

button, link, and menuitem elements do not have accessible names.

High

ARIA input fields do not have accessible names

High

ARIA meter elements do not have accessible names.

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

Links do not have a discernible name

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

ripleyspei.com SEO score

82

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

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

ripleyspei.com

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