Tools & Wizards About Us
captivatingworlds.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

captivatingworlds.com

Captivating Worlds - Immersive Adventures Open in Columbus

Page Load Speed

2 sec in total

First Response

69 ms

Resources Loaded

1.7 sec

Page Rendered

252 ms

captivatingworlds.com screenshot

About Website

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

Experience all new immersive adventures at Captivating Worlds now open in Columbus. The game has evolved! The future of escape rooms is here.

Visit captivatingworlds.com

Key Findings

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

captivatingworlds.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value4,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

captivatingworlds.com

69 ms

captivatingworlds.com

81 ms

js

151 ms

style.min.css

36 ms

d481824422c588b13454c4ba6ac407e0.css

108 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 75% of them (45 requests) were addressed to the original Captivatingworlds.com, 13% (8 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (688 ms) relates to the external source Unsplash.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 243.7 kB (35%)

Content Size

697.4 kB

After Optimization

453.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 242.5 kB

  • Original 273.4 kB
  • After minification 251.6 kB
  • After compression 30.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. 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 242.5 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 11.4 kB
  • After minification 11.4 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. Captivating Worlds images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

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

CSS Optimization

-0%

Potential reduce by 63 B

  • Original 260.9 kB
  • After minification 260.9 kB
  • After compression 260.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. Captivatingworlds.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (93%)

Requests Now

42

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Captivating Worlds. 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

captivatingworlds.com

captivatingworlds.com

69 ms

captivatingworlds.com

captivatingworlds.com

81 ms

js

js

151 ms

style.min.css

style.min.css

36 ms

d481824422c588b13454c4ba6ac407e0.css

d481824422c588b13454c4ba6ac407e0.css

108 ms

css

css

175 ms

0b8ff8b52fdc42cd67827f2b30282e26.css

0b8ff8b52fdc42cd67827f2b30282e26.css

97 ms

dashicons.min.css

dashicons.min.css

95 ms

wp-faqp-public.min.css

wp-faqp-public.min.css

75 ms

css

css

267 ms

7e833f88caae06a9c931006205d90251.css

7e833f88caae06a9c931006205d90251.css

96 ms

5edc1daf900216d5cd0fc81907d8ba4c.css

5edc1daf900216d5cd0fc81907d8ba4c.css

92 ms

765844e9d8eee2bf56b429db3ac89ece.css

765844e9d8eee2bf56b429db3ac89ece.css

172 ms

00744cceda771961e0641de150d53e3e.css

00744cceda771961e0641de150d53e3e.css

152 ms

email-decode.min.js

email-decode.min.js

154 ms

frontend.js

frontend.js

155 ms

frontend.js

frontend.js

153 ms

b5c960c4f313d62e217ae0df0ffa2939.js

b5c960c4f313d62e217ae0df0ffa2939.js

153 ms

frontend.js

frontend.js

247 ms

85c05554e84c31e47d0df7e263e0dc71.js

85c05554e84c31e47d0df7e263e0dc71.js

319 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

242 ms

b7cbe7d419ca4a292fe1c2c0019bb3a5.js

b7cbe7d419ca4a292fe1c2c0019bb3a5.js

245 ms

js.cookie.min.js

js.cookie.min.js

246 ms

809069452170d08f979ffa7c75fd7d80.js

809069452170d08f979ffa7c75fd7d80.js

243 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

318 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

321 ms

sticky-kit.min.js

sticky-kit.min.js

319 ms

functions.min.js

functions.min.js

320 ms

tooltipsy.min.js

tooltipsy.min.js

321 ms

jquery.bigtext.min.js

jquery.bigtext.min.js

321 ms

bigtext.min.js

bigtext.min.js

323 ms

carousels.min.js

carousels.min.js

322 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

326 ms

wp-embed.min.js

wp-embed.min.js

323 ms

js_composer_front.min.js

js_composer_front.min.js

326 ms

0d3924b0ec9633b8eb27ab1a620f4882.js

0d3924b0ec9633b8eb27ab1a620f4882.js

324 ms

loader.js

loader.js

151 ms

mailchimp.min.js

mailchimp.min.js

326 ms

rocket-loader.min.js

rocket-loader.min.js

323 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

241 ms

688 ms

main.js

main.js

18 ms

jizaRExUiTo99u79D0yEwA.ttf

jizaRExUiTo99u79D0yEwA.ttf

51 ms

jizfRExUiTo99u79B_mh0OCtKA.ttf

jizfRExUiTo99u79B_mh0OCtKA.ttf

138 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

168 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

171 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

169 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

171 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

171 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

167 ms

Linearicons-Free.woff

Linearicons-Free.woff

95 ms

linea-arrows-10.woff

linea-arrows-10.woff

18 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

89 ms

Linearicons-Free.ttf

Linearicons-Free.ttf

264 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

313 ms

Linearicons-Free.svg

Linearicons-Free.svg

52 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

573 ms

300.jpg

300.jpg

33 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

12 ms

frontend-gtag.min.js

frontend-gtag.min.js

11 ms

Accessibility Review

captivatingworlds.com accessibility score

97

Accessibility Issues

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

captivatingworlds.com best practices score

75

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

SEO Factors

captivatingworlds.com SEO score

100

Search Engine Optimization Advices

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

captivatingworlds.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: