Tools & Wizards About Us
dualog.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

dualog.com

Software made for shipping | Dualog

Page Load Speed

5.3 sec in total

First Response

110 ms

Resources Loaded

2.9 sec

Page Rendered

2.3 sec

dualog.com screenshot

About Website

Click here to check amazing Dualog content for Singapore. Otherwise, check out these important facts you probably never knew about dualog.com

Dualog delivers software made for the maritime industry. Solutions for data exchange, internet management, collaboration and cybersecurity. Learn more and get a free trial.

Visit dualog.com

Key Findings

We analyzed Dualog.com page load time and found that the first response time was 110 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

dualog.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

dualog.com

110 ms

dualog.com

1583 ms

89 ms

css

178 ms

jquery.min.js

58 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 51% of them (41 requests) were addressed to the original Dualog.com, 34% (27 requests) were made to Fonts.wp.com and 1% (1 request) were made to Fonts-api.wp.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Dualog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 974.3 kB (25%)

Content Size

4.0 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dualog.com main page is 4.0 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. 80% 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 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 193.0 kB

  • Original 225.8 kB
  • After minification 216.2 kB
  • After compression 32.8 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 193.0 kB or 85% of the original size.

Image Optimization

-21%

Potential reduce by 723.2 kB

  • Original 3.5 MB
  • After minification 2.7 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, Dualog needs image optimization as it can save up to 723.2 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 8.7 kB

  • Original 197.4 kB
  • After minification 197.4 kB
  • After compression 188.7 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

-81%

Potential reduce by 49.5 kB

  • Original 60.9 kB
  • After minification 60.8 kB
  • After compression 11.4 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. Dualog.com needs all CSS files to be minified and compressed as it can save up to 49.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (56%)

Requests Now

45

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dualog.com

dualog.com

110 ms

dualog.com

dualog.com

1583 ms

89 ms

css

css

178 ms

jquery.min.js

jquery.min.js

58 ms

65 ms

ct-bot-detector-wrapper.js

ct-bot-detector-wrapper.js

329 ms

js

js

169 ms

custom-pro-widget-mega-menu.min.css

custom-pro-widget-mega-menu.min.css

166 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

77 ms

widget-loop-builder.min.css

widget-loop-builder.min.css

76 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

162 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

162 ms

bilmur.min.js

bilmur.min.js

52 ms

165 ms

5540783.js

5540783.js

162 ms

hello-frontend.min.js

hello-frontend.min.js

166 ms

e-202431.js

e-202431.js

50 ms

165 ms

i18n.min.js

i18n.min.js

166 ms

frontend.min.js

frontend.min.js

165 ms

167 ms

frontend.min.js

frontend.min.js

166 ms

elements-handlers.min.js

elements-handlers.min.js

167 ms

Primary-logo.svg

Primary-logo.svg

321 ms

834ed6fafa3cac055ab7ca76eb863581.gif

834ed6fafa3cac055ab7ca76eb863581.gif

550 ms

Dualog_cargo_ship-2048x1416.png

Dualog_cargo_ship-2048x1416.png

145 ms

Dualog_Drive_cover.png

Dualog_Drive_cover.png

139 ms

Group-632-800x722.png

Group-632-800x722.png

138 ms

Dualog_Seafarer_cover5.png

Dualog_Seafarer_cover5.png

137 ms

Group-468-4.png

Group-468-4.png

139 ms

Dualog_Endpoint_cover1.png

Dualog_Endpoint_cover1.png

140 ms

Dualog_Protect_cover.png

Dualog_Protect_cover.png

142 ms

Dualog_Fetch_cover.png

Dualog_Fetch_cover.png

140 ms

Dualog_configuration7.png

Dualog_configuration7.png

598 ms

Dualog_automatisation2.png

Dualog_automatisation2.png

461 ms

Dualog_dashboars.png

Dualog_dashboars.png

141 ms

Group-597.png

Group-597.png

142 ms

Morten_Lind_Olsen__Dualog_CEO.png

Morten_Lind_Olsen__Dualog_CEO.png

161 ms

DD-vs-OD-1.jpg

DD-vs-OD-1.jpg

160 ms

Posidonia.jpg

Posidonia.jpg

595 ms

Dualog_Drive_5_use_cases_featured_image.webp

Dualog_Drive_5_use_cases_featured_image.webp

217 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

251 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

247 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

250 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf

250 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf

249 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

247 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

250 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf

250 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf

253 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

252 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

252 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

252 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

310 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

348 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

393 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

393 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

393 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

392 ms

fa-solid-900.woff

fa-solid-900.woff

132 ms

fa-regular-400.woff

fa-regular-400.woff

64 ms

MaterialIcons-Regular.woff

MaterialIcons-Regular.woff

205 ms

fa-brands-400.woff

fa-brands-400.woff

241 ms

themify.woff

themify.woff

347 ms

ElegantIcons.woff

ElegantIcons.woff

391 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rm.ttf

439 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

440 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

441 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISmb2Rm.ttf

440 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rm.ttf

444 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf

443 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

442 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOmb2Rm.ttf

443 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rm.ttf

443 ms

collectedforms.js

collectedforms.js

363 ms

banner.js

banner.js

314 ms

conversations-embed.js

conversations-embed.js

306 ms

5540783.js

5540783.js

367 ms

web-interactives-embed.js

web-interactives-embed.js

363 ms

Accessibility Review

dualog.com accessibility score

87

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.

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 IDs are not unique

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

Links do not have a discernible name

Best Practices

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

dualog.com SEO score

91

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

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

dualog.com

Open Graph data is detected on the main page of Dualog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: