Tools & Wizards About Us
cultus.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

cultus.com

Destination Cultus - Two Great Parks, One Destination

Page Load Speed

2.9 sec in total

First Response

42 ms

Resources Loaded

2.8 sec

Page Rendered

76 ms

cultus.com screenshot

About Website

Click here to check amazing Cultus content for Canada. Otherwise, check out these important facts you probably never knew about cultus.com

var ssaUrl = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'pixel.sitescout.com/iap/9f1a5538becde3bd';new Image().src = ssaUrl; (function(...

Visit cultus.com

Key Findings

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

Performance Metrics

cultus.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value49.1 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,040 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.206

60/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

cultus.com

42 ms

cultus.com

301 ms

www.cultus.com

755 ms

dg-grid.css

250 ms

foobox.free.min.css

252 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 90% of them (102 requests) were addressed to the original Cultus.com, 3% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (755 ms) belongs to the original domain Cultus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (61%)

Content Size

2.5 MB

After Optimization

977.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 1.4 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 227.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. 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 1.4 MB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 194.6 kB
  • After minification 194.6 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. Cultus images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 892 B

  • Original 497.3 kB
  • After minification 497.3 kB
  • After compression 496.4 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

-58%

Potential reduce by 82.5 kB

  • Original 141.3 kB
  • After minification 141.2 kB
  • After compression 58.7 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. Cultus.com needs all CSS files to be minified and compressed as it can save up to 82.5 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 96 (91%)

Requests Now

106

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cultus.com

cultus.com

42 ms

cultus.com

cultus.com

301 ms

www.cultus.com

www.cultus.com

755 ms

dg-grid.css

dg-grid.css

250 ms

foobox.free.min.css

foobox.free.min.css

252 ms

comment-form.min.css

comment-form.min.css

256 ms

privacy.min.css

privacy.min.css

250 ms

faqs.min.css

faqs.min.css

254 ms

portfolio.min.css

portfolio.min.css

338 ms

style.min.css

style.min.css

341 ms

style.css

style.css

346 ms

gdpr-main.css

gdpr-main.css

348 ms

jquery.min.js

jquery.min.js

424 ms

jquery-migrate.min.js

jquery-migrate.min.js

439 ms

nfpluginsettings.js

nfpluginsettings.js

444 ms

nfpluginsettings.js

nfpluginsettings.js

443 ms

rbtools.min.js

rbtools.min.js

593 ms

rs6.min.js

rs6.min.js

485 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

509 ms

js.cookie.min.js

js.cookie.min.js

516 ms

woocommerce.min.js

woocommerce.min.js

517 ms

underscore.min.js

underscore.min.js

519 ms

wp-util.min.js

wp-util.min.js

574 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

621 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

622 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

624 ms

wp-polyfill.min.js

wp-polyfill.min.js

626 ms

hooks.min.js

hooks.min.js

662 ms

wpm-public.p1.min.js

wpm-public.p1.min.js

691 ms

foobox.free.min.js

foobox.free.min.js

683 ms

e743c210-4fe8-0137-5e03-067f653fa718

e743c210-4fe8-0137-5e03-067f653fa718

30 ms

css

css

36 ms

wc-blocks.css

wc-blocks.css

430 ms

style.min.css

style.min.css

433 ms

rs6.css

rs6.css

430 ms

sourcebuster.min.js

sourcebuster.min.js

431 ms

order-attribution.min.js

order-attribution.min.js

431 ms

main.js

main.js

435 ms

cssua.js

cssua.js

436 ms

fusion-animations.js

fusion-animations.js

436 ms

awb-tabs-widget.js

awb-tabs-widget.js

480 ms

awb-vertical-menu-widget.js

awb-vertical-menu-widget.js

480 ms

modernizr.js

modernizr.js

505 ms

fusion.js

fusion.js

567 ms

swiper.js

swiper.js

602 ms

bootstrap.transition.js

bootstrap.transition.js

566 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

600 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

600 ms

jquery.easing.js

jquery.easing.js

601 ms

jquery.fitvids.js

jquery.fitvids.js

601 ms

jquery.flexslider.js

jquery.flexslider.js

550 ms

jquery.ilightbox.js

jquery.ilightbox.js

597 ms

jquery.mousewheel.js

jquery.mousewheel.js

592 ms

jquery.placeholder.js

jquery.placeholder.js

618 ms

jquery.fade.js

jquery.fade.js

578 ms

imagesLoaded.js

imagesLoaded.js

556 ms

fusion-equal-heights.js

fusion-equal-heights.js

550 ms

fusion-parallax.js

fusion-parallax.js

667 ms

fusion-video-general.js

fusion-video-general.js

664 ms

fusion-video-bg.js

fusion-video-bg.js

613 ms

fusion-lightbox.js

fusion-lightbox.js

568 ms

fusion-tooltip.js

fusion-tooltip.js

566 ms

fusion-sharing-box.js

fusion-sharing-box.js

565 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

635 ms

fusion-youtube.js

fusion-youtube.js

636 ms

vimeoPlayer.js

vimeoPlayer.js

600 ms

avada-woo-variations.js

avada-woo-variations.js

580 ms

gtm.js

gtm.js

169 ms

avada-general-footer.js

avada-general-footer.js

459 ms

avada-quantity.js

avada-quantity.js

455 ms

avada-crossfade-images.js

avada-crossfade-images.js

545 ms

avada-select.js

avada-select.js

538 ms

avada-rev-styles.js

avada-rev-styles.js

544 ms

avada-live-search.js

avada-live-search.js

543 ms

fusion-alert.js

fusion-alert.js

536 ms

awb-off-canvas.js

awb-off-canvas.js

543 ms

fusion-flexslider.js

fusion-flexslider.js

615 ms

font

font

95 ms

fusion-column-legacy.js

fusion-column-legacy.js

576 ms

awb-background-slider.js

awb-background-slider.js

581 ms

fusion-container.js

fusion-container.js

490 ms

jquery.elasticslider.js

jquery.elasticslider.js

498 ms

avada-elastic-slider.js

avada-elastic-slider.js

496 ms

avada-drop-down.js

avada-drop-down.js

545 ms

avada-to-top.js

avada-to-top.js

537 ms

avada-header.js

avada-header.js

546 ms

avada-menu.js

avada-menu.js

545 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

550 ms

avada-scrollspy.js

avada-scrollspy.js

548 ms

js

js

63 ms

analytics.js

analytics.js

23 ms

destination

destination

160 ms

avada-woo-products.js

avada-woo-products.js

576 ms

avada-woocommerce.js

avada-woocommerce.js

577 ms

collect

collect

123 ms

avada-woo-product-images.js

avada-woo-product-images.js

550 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

554 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

550 ms

fusion-general-global.js

fusion-general-global.js

561 ms

collect

collect

99 ms

fusion-video.js

fusion-video.js

516 ms

fusion-column.js

fusion-column.js

514 ms

lazyload.min.js

lazyload.min.js

513 ms

fa-solid-900.woff

fa-solid-900.woff

619 ms

fa-regular-400.woff

fa-regular-400.woff

526 ms

venusgb-webfont-1.woff

venusgb-webfont-1.woff

458 ms

dummy.png

dummy.png

546 ms

ga-audiences

ga-audiences

42 ms

awb-icons.woff

awb-icons.woff

174 ms

fbevents.js

fbevents.js

86 ms

destination-cultus-logo.png

destination-cultus-logo.png

171 ms

mobile-logo.png

mobile-logo.png

100 ms

destination-cultus-logo-300x210.png

destination-cultus-logo-300x210.png

248 ms

Accessibility Review

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

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

Page has valid source maps

SEO Factors

cultus.com SEO score

93

Search Engine Optimization Advices

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

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

cultus.com

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