Tools & Wizards About Us
otto-comm.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

otto-comm.com

Manufacturer of Two-Way Radio Communications Accessories – OTTO Communications

Page Load Speed

3.1 sec in total

First Response

429 ms

Resources Loaded

2.1 sec

Page Rendered

560 ms

otto-comm.com screenshot

About Website

Click here to check amazing OTTO Comm content for United States. Otherwise, check out these important facts you probably never knew about otto-comm.com

OTTO communications designs and manufactures of communications accessories, specializing in mission-critical equipment for the two-way radio market premium quality of USA made.

Visit otto-comm.com

Key Findings

We analyzed Otto-comm.com page load time and found that the first response time was 429 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

otto-comm.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.453

20/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

otto-comm.com

429 ms

js

85 ms

css

107 ms

js_jquery_validation

129 ms

VisitorIdentification.js

167 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 90% of them (65 requests) were addressed to the original Otto-comm.com, 4% (3 requests) were made to Cdnjs.cloudflare.com and 3% (2 requests) were made to Pi.pardot.com. The less responsive or slowest element that took the longest time to load (668 ms) belongs to the original domain Otto-comm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (29%)

Content Size

7.9 MB

After Optimization

5.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Otto-comm.com main page is 7.9 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. Images take 7.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 156.3 kB

  • Original 179.9 kB
  • After minification 106.0 kB
  • After compression 23.6 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. This page needs HTML code to be minified as it can gain 73.9 kB, which is 41% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 156.3 kB or 87% of the original size.

Image Optimization

-28%

Potential reduce by 2.2 MB

  • Original 7.7 MB
  • After minification 5.6 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. Obviously, OTTO Comm needs image optimization as it can save up to 2.2 MB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 715 B

  • Original 4.7 kB
  • After minification 4.7 kB
  • After compression 4.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 715 B or 15% of the original size.

CSS Optimization

-24%

Potential reduce by 991 B

  • Original 4.1 kB
  • After minification 4.1 kB
  • After compression 3.1 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. Otto-comm.com needs all CSS files to be minified and compressed as it can save up to 991 B or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (28%)

Requests Now

65

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

otto-comm.com

otto-comm.com

429 ms

js

js

85 ms

css

css

107 ms

js_jquery_validation

js_jquery_validation

129 ms

VisitorIdentification.js

VisitorIdentification.js

167 ms

translateelement.css

translateelement.css

173 ms

element.js

element.js

169 ms

Js_menuheader

Js_menuheader

166 ms

jquery.cookie.min.js

jquery.cookie.min.js

30 ms

Js_footer

Js_footer

193 ms

js

js

214 ms

jquery.lazy.min.js

jquery.lazy.min.js

37 ms

jquery.lazy.plugins.min.js

jquery.lazy.plugins.min.js

42 ms

Js_communication

Js_communication

201 ms

logo.svg

logo.svg

65 ms

nbtac15249x272.ashx

nbtac15249x272.ashx

211 ms

revonc2_249x272.ashx

revonc2_249x272.ashx

210 ms

lynqpro_249x272.ashx

lynqpro_249x272.ashx

209 ms

multi-port-hub-ptt_249x272.ashx

multi-port-hub-ptt_249x272.ashx

210 ms

Covert_PTT.ashx

Covert_PTT.ashx

223 ms

Professional-Throat-Mic-Transparent.ashx

Professional-Throat-Mic-Transparent.ashx

211 ms

storm-picture-a-1000.ashx

storm-picture-a-1000.ashx

376 ms

otto_connect_front-left-249.ashx

otto_connect_front-left-249.ashx

210 ms

required-adapter-v1-10842-1000.ashx

required-adapter-v1-10842-1000.ashx

478 ms

open-ear-insert-clear-1000x1072.ashx

open-ear-insert-clear-1000x1072.ashx

353 ms

video-esp_80x60.ashx

video-esp_80x60.ashx

231 ms

lynqpro_video_thumbnail_80x60.ashx

lynqpro_video_thumbnail_80x60.ashx

229 ms

video-nbmicro_80x60.ashx

video-nbmicro_80x60.ashx

278 ms

video-nbtac_80x60.ashx

video-nbtac_80x60.ashx

277 ms

video-btrnc2_80x60.ashx

video-btrnc2_80x60.ashx

281 ms

insta_logo.ashx

insta_logo.ashx

566 ms

x_twitter_logo.ashx

x_twitter_logo.ashx

325 ms

icon-cart-black.svg

icon-cart-black.svg

317 ms

icon-close-black.svg

icon-close-black.svg

353 ms

main.js

main.js

28 ms

news-icon.svg

news-icon.svg

310 ms

lynqpro_wave_1400x403.ashx

lynqpro_wave_1400x403.ashx

448 ms

otto500_wave_1400x403.ashx

otto500_wave_1400x403.ashx

668 ms

nbtac_wave_1400x403.ashx

nbtac_wave_1400x403.ashx

478 ms

surveillence_wave_1400x403.ashx

surveillence_wave_1400x403.ashx

458 ms

blank.png

blank.png

469 ms

line.svg

line.svg

487 ms

icon-phone.svg

icon-phone.svg

493 ms

icon-email.svg

icon-email.svg

506 ms

social-media.svg

social-media.svg

520 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

379 ms

HelveticaNeue-Thin.woff

HelveticaNeue-Thin.woff

517 ms

HelveticaLTStd-LightCond.woff

HelveticaLTStd-LightCond.woff

517 ms

HelveticaLTStd-BoldCond.woff

HelveticaLTStd-BoldCond.woff

518 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

518 ms

GetGDPRBannerText

GetGDPRBannerText

126 ms

rs-default.png

rs-default.png

38 ms

video-esp_1140x570.ashx

video-esp_1140x570.ashx

119 ms

lynqpro_vdeo_1140x570.ashx

lynqpro_vdeo_1140x570.ashx

57 ms

video-nbmicro_1140x570.ashx

video-nbmicro_1140x570.ashx

115 ms

video-nbtac_1140x570.ashx

video-nbtac_1140x570.ashx

92 ms

preloader-white.gif

preloader-white.gif

40 ms

arrow-slider.svg

arrow-slider.svg

73 ms

arrow-slider-right.svg

arrow-slider-right.svg

77 ms

arrow-slider-slick.svg

arrow-slider-slick.svg

102 ms

arrow-slider-right-slick.svg

arrow-slider-right-slick.svg

114 ms

ajax-loader.gif

ajax-loader.gif

114 ms

OTTO_logo_WHT_Comm.png

OTTO_logo_WHT_Comm.png

128 ms

sound-bkgd_2560x1440.ashx

sound-bkgd_2560x1440.ashx

188 ms

slick.woff

slick.woff

150 ms

pd.js

pd.js

16 ms

blog-esp-cct_1000x500.ashx

blog-esp-cct_1000x500.ashx

114 ms

blog-lynqpro-indigenous_1000x500.ashx

blog-lynqpro-indigenous_1000x500.ashx

122 ms

NSCX0924_Logo.ashx

NSCX0924_Logo.ashx

104 ms

AUSA2024.ashx

AUSA2024.ashx

91 ms

IACP2024Logo.ashx

IACP2024Logo.ashx

68 ms

analytics

analytics

205 ms

Accessibility Review

otto-comm.com accessibility score

74

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 input fields do not have accessible names

High

ARIA IDs are not unique

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

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

Image elements do not have [alt] attributes

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

otto-comm.com best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

otto-comm.com SEO score

72

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

High

Image elements do not have [alt] attributes

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 Otto-comm.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 Otto-comm.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

otto-comm.com

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