Tools & Wizards About Us
dustnetworks.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

dustnetworks.com

Wireless Infrastructure Solutions | Analog Devices

Page Load Speed

23 sec in total

First Response

129 ms

Resources Loaded

21.2 sec

Page Rendered

1.7 sec

dustnetworks.com screenshot

About Website

Welcome to dustnetworks.com homepage info - get ready to check Dustnetworks best content right away, or after learning these important things about dustnetworks.com

Analog Devices cemented its reputation as a leader in wireless infrastructure by creating the technologies that enabled the first small cells and the roll out of 5G mMIMO. With technology solutions th...

Visit dustnetworks.com

Key Findings

We analyzed Dustnetworks.com page load time and found that the first response time was 129 ms and then it took 22.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

dustnetworks.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value19.9 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

smartmesh-pavilion-home.html

129 ms

wireless-infrastructure.html

120 ms

legacy-common.bundle.css

246 ms

legacy-applications.bundle.css

514 ms

error400page.bundle.css

191 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dustnetworks.com, 29% (17 requests) were made to Assets2.analog.com and 5% (3 requests) were made to Wcm2.cldnet.analog.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Wcm2.cldnet.analog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (39%)

Content Size

3.3 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dustnetworks.com main page is 3.3 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. 50% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 146.1 kB

  • Original 163.5 kB
  • After minification 120.5 kB
  • After compression 17.4 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 43.0 kB, which is 26% 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 146.1 kB or 89% of the original size.

Image Optimization

-7%

Potential reduce by 88.1 kB

  • Original 1.2 MB
  • After minification 1.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. Dustnetworks images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 1.1 MB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 773.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.1 MB or 58% of the original size.

CSS Optimization

-5%

Potential reduce by 7.0 kB

  • Original 150.6 kB
  • After minification 150.6 kB
  • After compression 143.5 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. Dustnetworks.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

53

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

smartmesh-pavilion-home.html

smartmesh-pavilion-home.html

129 ms

wireless-infrastructure.html

wireless-infrastructure.html

120 ms

legacy-common.bundle.css

legacy-common.bundle.css

246 ms

legacy-applications.bundle.css

legacy-applications.bundle.css

514 ms

error400page.bundle.css

error400page.bundle.css

191 ms

error500page.bundle.css

error500page.bundle.css

287 ms

analog-vendor.js

analog-vendor.js

315 ms

rte-editor-control.bundle.css

rte-editor-control.bundle.css

323 ms

index.js

index.js

285 ms

launch-715705770daf.min.js

launch-715705770daf.min.js

25 ms

index.min.js

index.min.js

32 ms

common.bundle.js

common.bundle.js

351 ms

rte-editor-control.bundle.js

rte-editor-control.bundle.js

315 ms

legacy-plugin.bundle.js

legacy-plugin.bundle.js

367 ms

bootstrap-slider.min.js

bootstrap-slider.min.js

458 ms

legacy-common.bundle.js

legacy-common.bundle.js

346 ms

legacy-page-applications.bundle.js

legacy-page-applications.bundle.js

490 ms

interactive-images.js

interactive-images.js

650 ms

solutionsl1page.bundle.js

solutionsl1page.bundle.js

479 ms

l2solutionspage.bundle.js

l2solutionspage.bundle.js

621 ms

l3solutionspage.bundle.js

l3solutionspage.bundle.js

622 ms

QARlk

QARlk

276 ms

chevron-left-s.png

chevron-left-s.png

38 ms

video-still-6335554958112.jpg

video-still-6335554958112.jpg

19993 ms

industry-solutions-l2-page_.png

industry-solutions-l2-page_.png

118 ms

chevron-down-white.svg

chevron-down-white.svg

120 ms

chevron-right-xs.svg

chevron-right-xs.svg

114 ms

wireless-infrastructure-4g-5g-radio-units.jpg

wireless-infrastructure-4g-5g-radio-units.jpg

138 ms

wireless-infrastructure-mmwave-communications.jpg

wireless-infrastructure-mmwave-communications.jpg

218 ms

wireless-infrastructure-e-band-radio-solutions.jpg

wireless-infrastructure-e-band-radio-solutions.jpg

115 ms

chevron-bottom-extra-small.svg

chevron-bottom-extra-small.svg

129 ms

wireless-infrastructure-4g-5g-radio-units.jpg

wireless-infrastructure-4g-5g-radio-units.jpg

173 ms

wireless-infrastructure-mmwave-communications.jpg

wireless-infrastructure-mmwave-communications.jpg

158 ms

wireless-infrastructure-e-band-radio-solutions.jpg

wireless-infrastructure-e-band-radio-solutions.jpg

219 ms

media-thumbnail.png

media-thumbnail.png

144 ms

link-pcp.svg

link-pcp.svg

259 ms

technical-documentation.svg

technical-documentation.svg

233 ms

play-icon.svg

play-icon.svg

253 ms

redirect-pcp.svg

redirect-pcp.svg

261 ms

video-still-6184075299001.jpg

video-still-6184075299001.jpg

303 ms

video-still-6046596190001.jpg

video-still-6046596190001.jpg

272 ms

video-still-6042788036001.jpg

video-still-6042788036001.jpg

253 ms

modal-close-icon.svg

modal-close-icon.svg

273 ms

arrow.svg

arrow.svg

300 ms

addtoanalog.svg

addtoanalog.svg

301 ms

share.svg

share.svg

274 ms

pdf-vector.svg

pdf-vector.svg

298 ms

icons_12px.svg

icons_12px.svg

313 ms

icon-left-(1).svg

icon-left-(1).svg

324 ms

support-bg.png

support-bg.png

340 ms

support-info.svg

support-info.svg

434 ms

part-updates-modal-bookmark.svg

part-updates-modal-bookmark.svg

404 ms

modal-close-icon.svg

modal-close-icon.svg

354 ms

arrowimg.svg

arrowimg.svg

338 ms

part-updates-modal-plus.svg

part-updates-modal-plus.svg

396 ms

add-to-myanalog-error.svg

add-to-myanalog-error.svg

413 ms

video-still-6335556409112.jpg

video-still-6335556409112.jpg

19971 ms

video-still-6257441448001.jpg

video-still-6257441448001.jpg

19970 ms

Accessibility Review

dustnetworks.com accessibility score

100

Accessibility Issues

Best Practices

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

Serves images with low resolution

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

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

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

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

dustnetworks.com

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