Tools & Wizards About Us
can-technologies.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

can-technologies.com

An innovative Engineering Company

Page Load Speed

3.7 sec in total

First Response

476 ms

Resources Loaded

2.3 sec

Page Rendered

979 ms

can-technologies.com screenshot

About Website

Welcome to can-technologies.com homepage info - get ready to check Can Technologies best content right away, or after learning these important things about can-technologies.com

Safety systems, Arc Flash, LOTO, Patient monitoring. We help organizations better manage health and safety of employees and patients. Book a free demo now!

Visit can-technologies.com

Key Findings

We analyzed Can-technologies.com page load time and found that the first response time was 476 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

can-technologies.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value29.3 s

0/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.161

73/100

15%

TTI (Time to Interactive)

Value29.4 s

0/100

10%

Network Requests Diagram

www.can-technologies.com

476 ms

slick.css

14 ms

slick-theme.css

20 ms

sweetalert.css

27 ms

style.css

28 ms

Our browser made a total of 159 requests to load all elements on the main page. We found that 86% of them (137 requests) were addressed to the original Can-technologies.com, 9% (15 requests) were made to Fonts.gstatic.com and 4% (6 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (962 ms) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 427.8 kB (6%)

Content Size

6.8 MB

After Optimization

6.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Can-technologies.com main page is 6.8 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. Only a small number of websites need less resources to load. Images take 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 165.9 kB

  • Original 188.8 kB
  • After minification 175.6 kB
  • After compression 22.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 165.9 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 259.0 kB

  • Original 6.3 MB
  • After minification 6.1 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. Can Technologies images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 389 B

  • Original 159.6 kB
  • After minification 159.6 kB
  • After compression 159.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.

CSS Optimization

-2%

Potential reduce by 2.5 kB

  • Original 105.7 kB
  • After minification 105.7 kB
  • After compression 103.2 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. Can-technologies.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (24%)

Requests Now

136

After Optimization

103

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.can-technologies.com

www.can-technologies.com

476 ms

slick.css

slick.css

14 ms

slick-theme.css

slick-theme.css

20 ms

sweetalert.css

sweetalert.css

27 ms

style.css

style.css

28 ms

elementor-icons.min.css

elementor-icons.min.css

35 ms

frontend.min.css

frontend.min.css

38 ms

swiper.min.css

swiper.min.css

46 ms

post-9.css

post-9.css

47 ms

frontend.min.css

frontend.min.css

68 ms

post-92.css

post-92.css

55 ms

post-30.css

post-30.css

63 ms

post-69.css

post-69.css

80 ms

css

css

31 ms

fontawesome.min.css

fontawesome.min.css

80 ms

solid.min.css

solid.min.css

83 ms

brands.min.css

brands.min.css

86 ms

jquery.min.js

jquery.min.js

90 ms

custom.js

custom.js

101 ms

slick.min.js

slick.min.js

124 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

133 ms

comment-reply.min.js

comment-reply.min.js

135 ms

imagesloaded.min.js

imagesloaded.min.js

134 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

135 ms

webpack.runtime.min.js

webpack.runtime.min.js

137 ms

frontend-modules.min.js

frontend-modules.min.js

138 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

146 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

147 ms

wp-polyfill.min.js

wp-polyfill.min.js

158 ms

hooks.min.js

hooks.min.js

155 ms

i18n.min.js

i18n.min.js

171 ms

frontend.min.js

frontend.min.js

171 ms

waypoints.min.js

waypoints.min.js

172 ms

core.min.js

core.min.js

176 ms

frontend.min.js

frontend.min.js

182 ms

elements-handlers.min.js

elements-handlers.min.js

184 ms

video-asset.png

video-asset.png

747 ms

logo-1.png

logo-1.png

307 ms

Vision_Final-1.jpg

Vision_Final-1.jpg

309 ms

Mission_Final-1.jpg

Mission_Final-1.jpg

312 ms

Values_Final-1.jpg

Values_Final-1.jpg

311 ms

Integrity_Final-1.jpg

Integrity_Final-1.jpg

315 ms

Outstanding_Final.jpg

Outstanding_Final.jpg

313 ms

Innovation_Final-1.jpg

Innovation_Final-1.jpg

317 ms

Shneider_GreenBar2-1.png

Shneider_GreenBar2-1.png

316 ms

Picture1-2.png

Picture1-2.png

319 ms

Picture2-2.png

Picture2-2.png

320 ms

Picture3-2.png

Picture3-2.png

321 ms

Picture4-2.png

Picture4-2.png

322 ms

Picture5-2.png

Picture5-2.png

322 ms

Picture6-2.png

Picture6-2.png

323 ms

Picture7-2.png

Picture7-2.png

324 ms

Picture8-1.png

Picture8-1.png

325 ms

Picture9-1.png

Picture9-1.png

326 ms

Picture10-1.png

Picture10-1.png

328 ms

shape-8-1.png

shape-8-1.png

778 ms

shape-6-1.png

shape-6-1.png

833 ms

testi-back-4.jpg

testi-back-4.jpg

962 ms

shape-7-1.png

shape-7-1.png

853 ms

home-back.jpg

home-back.jpg

820 ms

Picture11-1.png

Picture11-1.png

325 ms

Picture12-1.png

Picture12-1.png

318 ms

Picture13-1.png

Picture13-1.png

316 ms

Picture14-1.png

Picture14-1.png

316 ms

Picture15-1.png

Picture15-1.png

316 ms

Picture16-1.png

Picture16-1.png

316 ms

Picture17-2.png

Picture17-2.png

315 ms

Picture18-1.png

Picture18-1.png

319 ms

Picture19-1.png

Picture19-1.png

307 ms

Picture20-1.png

Picture20-1.png

366 ms

Picture21-1.png

Picture21-1.png

312 ms

Picture22-1.png

Picture22-1.png

297 ms

Picture23-1.png

Picture23-1.png

294 ms

Picture24-1.png

Picture24-1.png

320 ms

Picture25-1.png

Picture25-1.png

317 ms

Picture26-1.png

Picture26-1.png

431 ms

Picture27-1.png

Picture27-1.png

332 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

52 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

94 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

117 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

116 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

119 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

119 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

117 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

119 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

120 ms

fa-solid-900.woff

fa-solid-900.woff

93 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

119 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

124 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

125 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

123 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

123 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

126 ms

eicons.woff

eicons.woff

185 ms

fa-brands-400.woff

fa-brands-400.woff

181 ms

slick.woff

slick.woff

265 ms

Picture28-1.png

Picture28-1.png

116 ms

Picture29-1.png

Picture29-1.png

112 ms

Picture30-1.png

Picture30-1.png

116 ms

Picture31-1.png

Picture31-1.png

113 ms

Picture32-1.png

Picture32-1.png

173 ms

Picture33-1.png

Picture33-1.png

173 ms

Picture34-1.png

Picture34-1.png

173 ms

Picture35-2.png

Picture35-2.png

173 ms

Picture36-1.png

Picture36-1.png

173 ms

Picture37-1.png

Picture37-1.png

172 ms

Picture38-1.png

Picture38-1.png

172 ms

Picture39-1.png

Picture39-1.png

172 ms

Picture40-1.png

Picture40-1.png

172 ms

Picture41-1.png

Picture41-1.png

170 ms

Picture42-1.png

Picture42-1.png

171 ms

Picture43-1.png

Picture43-1.png

171 ms

Picture44-1.png

Picture44-1.png

172 ms

Picture45-1.png

Picture45-1.png

172 ms

Picture46-1.png

Picture46-1.png

172 ms

Picture47-1.png

Picture47-1.png

173 ms

Picture70-1.png

Picture70-1.png

173 ms

Picture67-2.png

Picture67-2.png

172 ms

Picture68-1.png

Picture68-1.png

171 ms

Picture69-1.png

Picture69-1.png

171 ms

waterloo.jpg

waterloo.jpg

160 ms

Picture50-1.png

Picture50-1.png

161 ms

Picture51.png

Picture51.png

162 ms

Picture52.png

Picture52.png

138 ms

Picture53.png

Picture53.png

124 ms

Picture54.png

Picture54.png

117 ms

Picture55.png

Picture55.png

116 ms

Picture56.png

Picture56.png

97 ms

Picture57.png

Picture57.png

87 ms

Picture58.png

Picture58.png

84 ms

Picture59.png

Picture59.png

82 ms

Picture60.png

Picture60.png

40 ms

Picture66-1.png

Picture66-1.png

39 ms

Picture61-2.png

Picture61-2.png

39 ms

Picture62-1.png

Picture62-1.png

38 ms

Picture63-1.png

Picture63-1.png

38 ms

Picture64-1.png

Picture64-1.png

40 ms

Picture65-1.png

Picture65-1.png

38 ms

Picture49-1.png

Picture49-1.png

38 ms

Picture48-2.png

Picture48-2.png

39 ms

Picture71-1.png

Picture71-1.png

39 ms

Picture72-1.png

Picture72-1.png

39 ms

Picture73-1.png

Picture73-1.png

39 ms

Picture74-1.png

Picture74-1.png

38 ms

Picture75-1.png

Picture75-1.png

39 ms

Picture76-1.png

Picture76-1.png

39 ms

Picture77-1.png

Picture77-1.png

38 ms

Picture78-1.png

Picture78-1.png

37 ms

Picture79-1.png

Picture79-1.png

37 ms

hamilton-1.png

hamilton-1.png

36 ms

download.png

download.png

36 ms

video-thumb.jpg

video-thumb.jpg

57 ms

play-circle-solid.png

play-circle-solid.png

55 ms

round-ball.png

round-ball.png

55 ms

Can_Teh_Footer2.png

Can_Teh_Footer2.png

55 ms

Alliance_Footer2.png

Alliance_Footer2.png

55 ms

ajax-loader.gif

ajax-loader.gif

267 ms

slick.ttf

slick.ttf

156 ms

slick.svg

slick.svg

153 ms

Accessibility Review

can-technologies.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

[aria-hidden="true"] elements contain focusable descendents

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

[id] attributes on active, focusable elements are not unique

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

Best Practices

can-technologies.com best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

can-technologies.com SEO score

99

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

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 Can-technologies.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 Can-technologies.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

can-technologies.com

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