8.7 sec in total
1.1 sec
7 sec
665 ms
Welcome to dug.com homepage info - get ready to check DUG best content right away, or after learning these important things about dug.com
DUG is a technology company at the forefront of high-performance computing with a strong foundation in applied physics. DUG’s innovative hardware and software solutions for the global technology and r...
Visit dug.comWe analyzed Dug.com page load time and found that the first response time was 1.1 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dug.com performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value15.8 s
0/100
25%
Value12.9 s
2/100
10%
Value380 ms
70/100
30%
Value0.028
100/100
15%
Value18.9 s
3/100
10%
1102 ms
877 ms
862 ms
862 ms
47 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 71% of them (77 requests) were addressed to the original Dug.com, 5% (5 requests) were made to Cdn.jsdelivr.net and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Dug.com.
Page size can be reduced by 222.9 kB (7%)
3.2 MB
3.0 MB
In fact, the total size of Dug.com main page is 3.2 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 82.2 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 82.2 kB or 82% of the original size.
Potential reduce by 58.2 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. DUG images are well optimized though.
Potential reduce by 39.5 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 39.5 kB or 29% of the original size.
Potential reduce by 43.0 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. Dug.com needs all CSS files to be minified and compressed as it can save up to 43.0 kB or 13% of the original size.
Number of requests can be reduced by 59 (66%)
89
30
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DUG. 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 28 to 1 for CSS and as a result speed up the page load time.
dug.com
1102 ms
quoteapi-loader.js
877 ms
quoteapi.js
862 ms
shareprice.css
862 ms
style.min.css
47 ms
irm-newsroom-public.css
47 ms
search_filter.css
86 ms
dashicons.min.css
87 ms
normalize.min.css
507 ms
slick.css
87 ms
slick.css
190 ms
animate.css
85 ms
gray.min.css
133 ms
twentytwenty.css
147 ms
zozo.tabs.min.css
132 ms
light.css
145 ms
lightgallery-bundle.min.css
202 ms
webflow.css
162 ms
custom.css
152 ms
theme.css
151 ms
fonts.css
975 ms
addtoany.min.css
150 ms
shiftnav.min.css
199 ms
ubermenu.min.css
198 ms
fontawesome-all.min.css
201 ms
font-awesome.min.css
216 ms
light.css
214 ms
conditionizr-4.3.0.min.js
216 ms
jquery-3.1.1.min.js
195 ms
jquery-migrate-3.0.0.min.js
213 ms
tippy.js
213 ms
webflow-blog.js
221 ms
addtoany.min.js
216 ms
irm-newsroom-public.js
220 ms
modernizr-2.8.3.js
63 ms
jquery.smooth-scroll.js
32 ms
slick.js
32 ms
slick.min.js
31 ms
wow.min.js
32 ms
jquery.gray.min.js
31 ms
jquery.popupoverlay.js
49 ms
jquery.event.move.js
34 ms
jquery.twentytwenty.js
44 ms
zozo.tabs.min.js
44 ms
scripts.js
49 ms
lightgallery.umd.min.js
36 ms
lg-video.umd.js
50 ms
ubermenu.min.js
47 ms
shiftnav.min.js
51 ms
wp-embed.min.js
47 ms
quoteapi.js
1256 ms
quoteapi.css
634 ms
52AEB3729E18B3EDD.css
24 ms
material-design-iconic-font.min.css
148 ms
css
154 ms
css
183 ms
page.js
461 ms
gtm.js
537 ms
insight.min.js
539 ms
dug-logo-white.png
386 ms
hero-bg.png
434 ms
bendy-tree.jpg
419 ms
ICRAR-blog-image.jpg
1302 ms
medical-research.jpg
1089 ms
fire-fighters.jpg
1311 ms
Webp.net-resizeimage-79.jpg
502 ms
Austal-resized.jpg
2086 ms
hpc-icon.png
502 ms
services-icon.png
504 ms
software-icon.png
505 ms
dugmcclound-icon2x_2.png
506 ms
hero-overlay-grey.png
506 ms
DUG_career_0221.jpg
507 ms
DUG_wfh_0320.jpg
508 ms
world-map@2x.png
510 ms
dug-logo-orange.png
512 ms
ISO-9001.png
511 ms
ISO-27001.png
587 ms
363CD4_0_0.woff
607 ms
363CD4_1_0.woff
607 ms
Gotham-Book.otf
1074 ms
Gotham-Medium.otf
1060 ms
Gotham-Light.otf
1136 ms
Gotham-Bold.otf
1953 ms
FontFont---DINPro.otf
1341 ms
FontFont---DINPro-Light.otf
1123 ms
fontawesome-webfont.woff
2149 ms
fa-regular-400.ttf
1132 ms
fa-light-300.ttf
1135 ms
fa-solid-900.ttf
1584 ms
fa-brands-400.woff
2010 ms
fa-brands-400.woff
2219 ms
9BAAAAAQAAAAFtwAAAAAAAAAKABQAHgAyAEYAjACiAL4BFgE2AY4AAAABAAAADAA8AAMAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADQAAAAEAAAAAAAIABwCWAAEAAAAAAAMADQBIAAEAAAAAAAQADQCrAAEAAAAAAAUACwAnAAEAAAAAAAYADQBvAAEAAAAAAAoAGgDSAAMAAQQJAAEAGgANAAMAAQQJAAIADgCdAAMAAQQJAAMAGgBVAAMAAQQJAAQAGgC4AAMAAQQJAAUAFgAyAAMAAQQJAAYAGgB8AAMAAQQJAAoANADsd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzUmVndWxhcgBSAGUAZwB1AGwAYQByd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
7 ms
fa-light-300.woff
2489 ms
fa-solid-900.woff
2558 ms
eso.e18d3993.js
108 ms
sm.23.html
108 ms
dug-logo-orange.png
2032 ms
analytics.js
188 ms
komito.js
241 ms
js
45 ms
collect
24 ms
komito.js
58 ms
collect
53 ms
ga-audiences
57 ms
20 ms
collect
9 ms
CheckCookie
67 ms
collect
13 ms
dug.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
dug.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
dug.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dug.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 Dug.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.
dug.com
Open Graph data is detected on the main page of DUG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: