Tools & Wizards About Us
critical2way.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

critical2way.com

Industrial Communication Solutions

Page Load Speed

1.3 sec in total

First Response

21 ms

Resources Loaded

919 ms

Page Rendered

390 ms

critical2way.com screenshot

About Website

Welcome to critical2way.com homepage info - get ready to check Critical 2 Way best content right away, or after learning these important things about critical2way.com

Code Red provides seamless-integration radio communication service for a wide variety of industries including construction, industrial and more.

Visit critical2way.com

Key Findings

We analyzed Critical2way.com page load time and found that the first response time was 21 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

critical2way.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.197

63/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

critical2way.com

21 ms

communications-solutions

84 ms

gtm.js

87 ms

ajax-progress.module.css

11 ms

align.module.css

14 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Critical2way.com, 85% (111 requests) were made to Coderedsafety.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (308 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.4 kB (7%)

Content Size

1.1 MB

After Optimization

990.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Critical2way.com main page is 1.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 793.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 49.6 kB

  • Original 62.3 kB
  • After minification 57.9 kB
  • After compression 12.7 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 49.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 2.3 kB

  • Original 793.2 kB
  • After minification 790.9 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. Critical 2 Way images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 10.1 kB

  • Original 136.0 kB
  • After minification 135.8 kB
  • After compression 126.0 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

-15%

Potential reduce by 10.4 kB

  • Original 71.7 kB
  • After minification 69.3 kB
  • After compression 61.3 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. Critical2way.com needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 15% of the original size.

Requests Breakdown

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

Requests Now

124

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

critical2way.com

critical2way.com

21 ms

communications-solutions

communications-solutions

84 ms

gtm.js

gtm.js

87 ms

ajax-progress.module.css

ajax-progress.module.css

11 ms

align.module.css

align.module.css

14 ms

autocomplete-loading.module.css

autocomplete-loading.module.css

17 ms

fieldgroup.module.css

fieldgroup.module.css

17 ms

container-inline.module.css

container-inline.module.css

18 ms

clearfix.module.css

clearfix.module.css

17 ms

details.module.css

details.module.css

18 ms

hidden.module.css

hidden.module.css

26 ms

item-list.module.css

item-list.module.css

25 ms

js.module.css

js.module.css

25 ms

nowrap.module.css

nowrap.module.css

25 ms

position-container.module.css

position-container.module.css

26 ms

progress.module.css

progress.module.css

24 ms

reset-appearance.module.css

reset-appearance.module.css

28 ms

resize.module.css

resize.module.css

26 ms

sticky-header.module.css

sticky-header.module.css

27 ms

system-status-counter.css

system-status-counter.css

28 ms

system-status-report-counters.css

system-status-report-counters.css

28 ms

system-status-report-general-info.css

system-status-report-general-info.css

25 ms

tabledrag.module.css

tabledrag.module.css

37 ms

tablesort.module.css

tablesort.module.css

37 ms

tree-child.module.css

tree-child.module.css

37 ms

paragraphs.unpublished.css

paragraphs.unpublished.css

36 ms

bootstrap.min.css

bootstrap.min.css

30 ms

we_megamenu_backend.css

we_megamenu_backend.css

37 ms

normalize.css

normalize.css

45 ms

normalize-fixes.css

normalize-fixes.css

45 ms

action-links.css

action-links.css

45 ms

breadcrumb.css

breadcrumb.css

44 ms

button.css

button.css

45 ms

collapse-processed.css

collapse-processed.css

46 ms

container-inline.css

container-inline.css

49 ms

details.css

details.css

49 ms

exposed-filters.css

exposed-filters.css

49 ms

field.css

field.css

45 ms

8474150.js

8474150.js

78 ms

v2.js

v2.js

77 ms

form.css

form.css

41 ms

icons.css

icons.css

42 ms

inline-form.css

inline-form.css

43 ms

item-list.css

item-list.css

40 ms

link.css

link.css

40 ms

links.css

links.css

40 ms

menu.css

menu.css

41 ms

more-link.css

more-link.css

41 ms

pager.css

pager.css

36 ms

tabledrag.css

tabledrag.css

34 ms

tableselect.css

tableselect.css

37 ms

tablesort.css

tablesort.css

34 ms

tabs.css

tabs.css

36 ms

textarea.css

textarea.css

35 ms

ui-dialog.css

ui-dialog.css

36 ms

messages.css

messages.css

38 ms

progress.css

progress.css

37 ms

slick.css

slick.css

38 ms

main.css

main.css

33 ms

sub-page.css

sub-page.css

38 ms

contact.css

contact.css

34 ms

dev.css

dev.css

30 ms

projects.css

projects.css

31 ms

jquery.min.js

jquery.min.js

32 ms

nodelist.foreach.js

nodelist.foreach.js

31 ms

element.matches.js

element.matches.js

28 ms

object.assign.js

object.assign.js

24 ms

css.escape.js

css.escape.js

24 ms

once.min.js

once.min.js

26 ms

jquery.once.min.js

jquery.once.min.js

27 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

28 ms

drupal.js

drupal.js

27 ms

drupal.init.js

drupal.init.js

26 ms

index.umd.min.js

index.umd.min.js

25 ms

progress.js

progress.js

26 ms

jquery.once.bc.js

jquery.once.bc.js

26 ms

ajax.js

ajax.js

26 ms

ajax.js

ajax.js

25 ms

slick.min.js

slick.min.js

25 ms

contact.js

contact.js

25 ms

general.js

general.js

25 ms

we_mobile_menu.js

we_mobile_menu.js

24 ms

we_megamenu_frontend.js

we_megamenu_frontend.js

24 ms

code-red-logo.png

code-red-logo.png

23 ms

css2

css2

70 ms

css2

css2

73 ms

banner.js

banner.js

243 ms

fb.js

fb.js

108 ms

8474150.js

8474150.js

106 ms

js

js

96 ms

analytics.js

analytics.js

235 ms

insight.min.js

insight.min.js

259 ms

swap.js

swap.js

248 ms

fbevents.js

fbevents.js

308 ms

events.js

events.js

220 ms

ico-arrow.png

ico-arrow.png

144 ms

ico-arrow-white.png

ico-arrow-white.png

100 ms

CRS_MegaMenu%20CTA_Infographic.jpg

CRS_MegaMenu%20CTA_Infographic.jpg

160 ms

CRS_MegaMenu%20CTA_RescueGuide.jpg

CRS_MegaMenu%20CTA_RescueGuide.jpg

160 ms

CRS_MegaMenu%20CTA_Turnaround.jpg

CRS_MegaMenu%20CTA_Turnaround.jpg

155 ms

CRS_MegaMenu%20CTA_Blog.jpg

CRS_MegaMenu%20CTA_Blog.jpg

160 ms

CRS_Side%20CTA_Code%20Red%20Stands%20for_0.jpg

CRS_Side%20CTA_Code%20Red%20Stands%20for_0.jpg

161 ms

CR-SubPage-Banner-Communications_.jpg

CR-SubPage-Banner-Communications_.jpg

198 ms

CRS_Side%20CTA_Equipment.jpg

CRS_Side%20CTA_Equipment.jpg

173 ms

CRS_Side%20CTA_Code%20Red%20Stands%20for_1.jpg

CRS_Side%20CTA_Code%20Red%20Stands%20for_1.jpg

173 ms

Comms-Slider%201.jpg

Comms-Slider%201.jpg

197 ms

Comms-Slider%202.jpg

Comms-Slider%202.jpg

200 ms

Comms-Slider%203.jpg

Comms-Slider%203.jpg

198 ms

linkedin.svg

linkedin.svg

199 ms

facebook.svg

facebook.svg

198 ms

instagram.svg

instagram.svg

226 ms

twitter.svg

twitter.svg

226 ms

youtube.svg

youtube.svg

224 ms

linkedin.svg

linkedin.svg

216 ms

facebook.svg

facebook.svg

193 ms

instagram.svg

instagram.svg

215 ms

twitter.svg

twitter.svg

217 ms

youtube.svg

youtube.svg

219 ms

RobotoCondensed-Bold.svg

RobotoCondensed-Bold.svg

81 ms

Roboto-Regular.svg

Roboto-Regular.svg

98 ms

Roboto-Medium.svg

Roboto-Medium.svg

95 ms

quicksand-v6-latin-regular.woff

quicksand-v6-latin-regular.woff

78 ms

quicksand-v6-latin-500.woff

quicksand-v6-latin-500.woff

79 ms

quicksand-v6-latin-300.woff

quicksand-v6-latin-300.woff

93 ms

quicksand-v6-latin-700.woff

quicksand-v6-latin-700.woff

95 ms

RobotoCondensed-Light.svg

RobotoCondensed-Light.svg

98 ms

saq_pxl

saq_pxl

32 ms

collect

collect

39 ms

insight.old.min.js

insight.old.min.js

17 ms

collect

collect

27 ms

Accessibility Review

critical2way.com accessibility score

96

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

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

critical2way.com SEO score

84

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

critical2way.com

Open Graph description is not detected on the main page of Critical 2 Way. 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: