Tools & Wizards About Us
caldyn.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

caldyn.com

California Dynamics Corporation – Vibration Isolation & Seismic Restraint Products

Page Load Speed

13.8 sec in total

First Response

193 ms

Resources Loaded

13.2 sec

Page Rendered

448 ms

caldyn.com screenshot

About Website

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

Visit caldyn.com

Key Findings

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

Performance Metrics

caldyn.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value23.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

caldyn.com

193 ms

caldyn.com

7407 ms

wp-emoji-release.min.js

155 ms

style.min.css

237 ms

wc-blocks-vendors-style.css

169 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 80% of them (78 requests) were addressed to the original Caldyn.com, 10% (10 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7.4 sec) belongs to the original domain Caldyn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 441.6 kB (16%)

Content Size

2.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Caldyn.com main page is 2.7 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 245.9 kB

  • Original 293.0 kB
  • After minification 289.7 kB
  • After compression 47.1 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 245.9 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 33.1 kB

  • Original 1.6 MB
  • After minification 1.5 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. Caldyn images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 109.9 kB

  • Original 602.9 kB
  • After minification 602.7 kB
  • After compression 492.9 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 109.9 kB or 18% of the original size.

CSS Optimization

-23%

Potential reduce by 52.7 kB

  • Original 232.3 kB
  • After minification 232.3 kB
  • After compression 179.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. Caldyn.com needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (84%)

Requests Now

83

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

caldyn.com

caldyn.com

193 ms

caldyn.com

caldyn.com

7407 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

155 ms

style.min.css

style.min.css

237 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

169 ms

wc-blocks-style.css

wc-blocks-style.css

544 ms

nectar-slider.css

nectar-slider.css

205 ms

woocommerce-layout.css

woocommerce-layout.css

235 ms

woocommerce.css

woocommerce.css

290 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

307 ms

grid-system.css

grid-system.css

320 ms

style.css

style.css

870 ms

header-layout-centered-menu.css

header-layout-centered-menu.css

370 ms

element-fancy-box.css

element-fancy-box.css

859 ms

css

css

30 ms

responsive.css

responsive.css

416 ms

product-style-material.css

product-style-material.css

399 ms

woocommerce.css

woocommerce.css

757 ms

select2.css

select2.css

711 ms

ascend.css

ascend.css

535 ms

menu-dynamic.css

menu-dynamic.css

771 ms

js_composer.min.css

js_composer.min.css

579 ms

css

css

22 ms

jquery.min.js

jquery.min.js

777 ms

jquery-migrate.min.js

jquery-migrate.min.js

736 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1007 ms

add-to-cart.min.js

add-to-cart.min.js

1050 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

854 ms

basic.min.css

basic.min.css

1123 ms

theme-ie11.min.css

theme-ie11.min.css

884 ms

theme.min.css

theme.min.css

955 ms

style-non-critical.css

style-non-critical.css

1210 ms

woocommerce-non-critical.css

woocommerce-non-critical.css

1211 ms

magnific.css

magnific.css

1039 ms

core.css

core.css

1122 ms

anime.min.js

anime.min.js

1140 ms

nectar-slider.js

nectar-slider.js

1331 ms

js.cookie.min.js

js.cookie.min.js

1211 ms

api.js

api.js

29 ms

woocommerce.min.js

woocommerce.min.js

1367 ms

jquery.easing.min.js

jquery.easing.min.js

1175 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

1181 ms

priority.js

priority.js

1141 ms

nectar-slider-priority.js

nectar-slider-priority.js

1131 ms

transit.min.js

transit.min.js

1174 ms

waypoints.js

waypoints.js

1143 ms

imagesLoaded.min.js

imagesLoaded.min.js

1125 ms

hoverintent.min.js

hoverintent.min.js

1114 ms

magnific.js

magnific.js

1151 ms

superfish.js

superfish.js

1151 ms

init.js

init.js

1263 ms

touchswipe.min.js

touchswipe.min.js

980 ms

select2.full.min.js

select2.full.min.js

1039 ms

quick_view_actions.js

quick_view_actions.js

1072 ms

flickity.js

flickity.js

961 ms

underscore.min.js

underscore.min.js

1144 ms

wp-util.min.js

wp-util.min.js

824 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

829 ms

js_composer_front.min.js

js_composer_front.min.js

870 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

887 ms

wp-polyfill.min.js

wp-polyfill.min.js

879 ms

dom-ready.min.js

dom-ready.min.js

841 ms

hooks.min.js

hooks.min.js

850 ms

i18n.min.js

i18n.min.js

916 ms

a11y.min.js

a11y.min.js

797 ms

jquery.json.min.js

jquery.json.min.js

768 ms

gravityforms.min.js

gravityforms.min.js

783 ms

gtm.js

gtm.js

74 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

997 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

921 ms

PNGCaldyn_onLightBG.onAlpha.png

PNGCaldyn_onLightBG.onAlpha.png

992 ms

PNGCaldyn_onDarkBG_onAlpha.png

PNGCaldyn_onDarkBG_onAlpha.png

2712 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

79 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

80 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

113 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

128 ms

w8gdH283Tvk__Lua32TysjIfp8uK.ttf

w8gdH283Tvk__Lua32TysjIfp8uK.ttf

129 ms

icomoon.woff

icomoon.woff

714 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

2042 ms

PNGCaldyn_onLightBG.onAlpha-1024x216.png

PNGCaldyn_onLightBG.onAlpha-1024x216.png

820 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

18 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

19 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

20 ms

image003-1.png

image003-1.png

939 ms

CoreSite-completed-SV8-Data-Center-in-Santa-Clara.jpg

CoreSite-completed-SV8-Data-Center-in-Santa-Clara.jpg

1159 ms

Madison_Center_1_966x668.jpg

Madison_Center_1_966x668.jpg

3995 ms

earthquake_survival_1_small.jpg

earthquake_survival_1_small.jpg

913 ms

ch_photo1.jpg

ch_photo1.jpg

1516 ms

recaptcha__en.js

recaptcha__en.js

22 ms

fallback

fallback

22 ms

fallback__ltr.css

fallback__ltr.css

3 ms

css

css

19 ms

logo_48.png

logo_48.png

4 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

3 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

831 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

288 ms

Accessibility Review

caldyn.com accessibility score

88

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

caldyn.com SEO score

86

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

caldyn.com

Open Graph description is not detected on the main page of Caldyn. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: