Tools & Wizards About Us
hub.digi.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

hub.digi.com

IIoT Devices and Services for M2M Networking | Digi International

Page Load Speed

1.6 sec in total

First Response

32 ms

Resources Loaded

555 ms

Page Rendered

1 sec

hub.digi.com screenshot

About Website

Click here to check amazing Hub Digi content for India. Otherwise, check out these important facts you probably never knew about hub.digi.com

Digi IIoT devices, software and services for enterprise, industrial and smart city IoT and M2M applications.

Visit hub.digi.com

Key Findings

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

Performance Metrics

hub.digi.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.245

51/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

hub.digi.com

32 ms

hub.digi.com

14 ms

www.digi.com

29 ms

GetResource.ashx

6 ms

GetResource.ashx

15 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Hub.digi.com, 96% (82 requests) were made to Digi.com and 1% (1 request) were made to Cdn.weglot.com. The less responsive or slowest element that took the longest time to load (186 ms) relates to the external source Digi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.6 kB (5%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hub.digi.com main page is 1.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. 75% 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.7 kB

  • Original 71.7 kB
  • After minification 55.1 kB
  • After compression 15.0 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 16.7 kB, which is 23% 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 56.7 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 11.2 kB

  • Original 1.3 MB
  • After minification 1.3 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. Hub Digi images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 664 B

  • Original 102.0 kB
  • After minification 102.0 kB
  • After compression 101.3 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.

Requests Breakdown

Number of requests can be reduced by 23 (35%)

Requests Now

66

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hub.digi.com

hub.digi.com

32 ms

hub.digi.com

hub.digi.com

14 ms

www.digi.com

www.digi.com

29 ms

GetResource.ashx

GetResource.ashx

6 ms

GetResource.ashx

GetResource.ashx

15 ms

GetResource.ashx

GetResource.ashx

24 ms

GetResource.ashx

GetResource.ashx

26 ms

GetResource.ashx

GetResource.ashx

26 ms

GetResource.ashx

GetResource.ashx

33 ms

main.js

main.js

26 ms

GetResource.ashx

GetResource.ashx

31 ms

nav.js

nav.js

31 ms

GetResource.ashx

GetResource.ashx

32 ms

weglot.min.js

weglot.min.js

88 ms

GetResource.ashx

GetResource.ashx

73 ms

GetResource.ashx

GetResource.ashx

72 ms

home.js

home.js

73 ms

ScriptResource.axd

ScriptResource.axd

73 ms

logo-digi-svg.svg

logo-digi-svg.svg

39 ms

select-background-arrow.svg

select-background-arrow.svg

8 ms

featured-dal-os.jpg

featured-dal-os.jpg

11 ms

featured-surelink.jpg

featured-surelink.jpg

12 ms

featured-trustfence.jpg

featured-trustfence.jpg

9 ms

featured-voicecontrol.jpg

featured-voicecontrol.jpg

11 ms

icon-external-link.svg

icon-external-link.svg

9 ms

background.jpg

background.jpg

14 ms

text-wedge.png

text-wedge.png

12 ms

corner-webinar.png

corner-webinar.png

13 ms

arrow-wcircle-grey-blue.png

arrow-wcircle-grey-blue.png

15 ms

ix40-background.jpg

ix40-background.jpg

14 ms

ix40-product.png

ix40-product.png

15 ms

mp13-background.jpg

mp13-background.jpg

17 ms

mp13-corner.png

mp13-corner.png

20 ms

digi-safe.jpg

digi-safe.jpg

17 ms

digi-safe-corner.png

digi-safe-corner.png

17 ms

background-embedded.png

background-embedded.png

18 ms

home-icon-embedded.png

home-icon-embedded.png

19 ms

home-arrow.png

home-arrow.png

22 ms

home-drm.png

home-drm.png

23 ms

background-networking.png

background-networking.png

21 ms

home-icon-networking.png

home-icon-networking.png

19 ms

home-icon-wds.png

home-icon-wds.png

20 ms

home-icon-ss.png

home-icon-ss.png

23 ms

icon-play.svg

icon-play.svg

23 ms

industry-background.png

industry-background.png

23 ms

offering-applications.png

offering-applications.png

25 ms

offering-technology.png

offering-technology.png

26 ms

offering-industries.png

offering-industries.png

25 ms

industrial-iot.jpg

industrial-iot.jpg

26 ms

firstnet.jpg

firstnet.jpg

27 ms

featured.jpg

featured.jpg

27 ms

out-of-band-management.jpg

out-of-band-management.jpg

153 ms

nyc-dot.png

nyc-dot.png

26 ms

electricities.png

electricities.png

27 ms

source-sans-3-v15-latin_latin-ext-regular.woff

source-sans-3-v15-latin_latin-ext-regular.woff

25 ms

source-sans-3-v15-latin_latin-ext-500.woff

source-sans-3-v15-latin_latin-ext-500.woff

48 ms

source-sans-3-v15-latin_latin-ext-300.woff

source-sans-3-v15-latin_latin-ext-300.woff

47 ms

source-sans-3-v15-latin_latin-ext-200.woff

source-sans-3-v15-latin_latin-ext-200.woff

47 ms

source-sans-3-v15-latin_latin-ext-600.woff

source-sans-3-v15-latin_latin-ext-600.woff

46 ms

source-sans-3-v15-latin_latin-ext-700.woff

source-sans-3-v15-latin_latin-ext-700.woff

45 ms

source-sans-3-v15-latin_latin-ext-800.woff

source-sans-3-v15-latin_latin-ext-800.woff

48 ms

source-sans-3-v15-latin_latin-ext-900.woff

source-sans-3-v15-latin_latin-ext-900.woff

46 ms

otis-logo.png

otis-logo.png

44 ms

biofeeder.png

biofeeder.png

44 ms

hero-opengear.jpg

hero-opengear.jpg

44 ms

icon-link-external-svg.svg

icon-link-external-svg.svg

45 ms

promo-smartsense.jpg

promo-smartsense.jpg

44 ms

promo-ventus.jpg

promo-ventus.jpg

45 ms

arrow-wcircle-blue-grey.png

arrow-wcircle-blue-grey.png

44 ms

arrow-next-grey.png

arrow-next-grey.png

47 ms

ecia-member-svg.svg

ecia-member-svg.svg

43 ms

footer-social-linked.png

footer-social-linked.png

44 ms

footer-social-facebook.png

footer-social-facebook.png

43 ms

footer-social-twitter.png

footer-social-twitter.png

44 ms

footer-social-youtube.png

footer-social-youtube.png

44 ms

footer-social-github.png

footer-social-github.png

43 ms

scroll-arrow-up.png

scroll-arrow-up.png

43 ms

source-sans-3-v15-latin_latin-ext-italic.woff

source-sans-3-v15-latin_latin-ext-italic.woff

4 ms

source-sans-3-v15-latin_latin-ext-500italic.woff

source-sans-3-v15-latin_latin-ext-500italic.woff

78 ms

source-sans-3-v15-latin_latin-ext-300italic.woff

source-sans-3-v15-latin_latin-ext-300italic.woff

24 ms

source-sans-3-v15-latin_latin-ext-200italic.woff

source-sans-3-v15-latin_latin-ext-200italic.woff

58 ms

source-sans-3-v15-latin_latin-ext-600italic.woff

source-sans-3-v15-latin_latin-ext-600italic.woff

186 ms

source-sans-3-v15-latin_latin-ext-700italic.woff

source-sans-3-v15-latin_latin-ext-700italic.woff

24 ms

source-sans-3-v15-latin_latin-ext-800italic.woff

source-sans-3-v15-latin_latin-ext-800italic.woff

24 ms

source-sans-3-v15-latin_latin-ext-900italic.woff

source-sans-3-v15-latin_latin-ext-900italic.woff

77 ms

Accessibility Review

hub.digi.com accessibility score

100

Accessibility Issues

Best Practices

hub.digi.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

hub.digi.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 Hub.digi.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 Hub.digi.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

hub.digi.com

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