Tools & Wizards About Us
dusky.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

dusky.com

Welcome to Dusky

Page Load Speed

1.2 sec in total

First Response

82 ms

Resources Loaded

780 ms

Page Rendered

331 ms

dusky.com screenshot

About Website

Visit dusky.com now to see the best up-to-date Dusky content for United States and also check out these interesting facts you probably never knew about dusky.com

Dusky Marine has been custom building center console and cuddy cabin offshore fishing boats and inshore bay and flats boats for more than 50 years.

Visit dusky.com

Key Findings

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

Performance Metrics

dusky.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value4.9 s

64/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

dusky.com

82 ms

www.dusky.com

245 ms

intlTelInput.css

25 ms

layout.css

48 ms

layout_index.css

72 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 84% of them (43 requests) were addressed to the original Dusky.com, 4% (2 requests) were made to Ssl.google-analytics.com and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (245 ms) belongs to the original domain Dusky.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 392.2 kB (8%)

Content Size

4.7 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dusky.com main page is 4.7 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 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 40.8 kB

  • Original 49.8 kB
  • After minification 45.0 kB
  • After compression 9.1 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 40.8 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 347.9 kB

  • Original 4.5 MB
  • After minification 4.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. Dusky images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

  • Original 173.3 kB
  • After minification 173.1 kB
  • After compression 171.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. This website has mostly compressed JavaScripts.

CSS Optimization

-17%

Potential reduce by 1.2 kB

  • Original 7.2 kB
  • After minification 7.2 kB
  • After compression 6.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. Dusky.com needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (48%)

Requests Now

42

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dusky.com

dusky.com

82 ms

www.dusky.com

www.dusky.com

245 ms

intlTelInput.css

intlTelInput.css

25 ms

layout.css

layout.css

48 ms

layout_index.css

layout_index.css

72 ms

jquery.mmenu.all.css

jquery.mmenu.all.css

43 ms

responsive.css

responsive.css

46 ms

jquery.migrate.js

jquery.migrate.js

69 ms

intlTelInput.js

intlTelInput.js

112 ms

en.js

en.js

65 ms

facebook.js

facebook.js

109 ms

twitter.js

twitter.js

109 ms

googleplus.js

googleplus.js

110 ms

layout.js

layout.js

110 ms

jquery.mmenu.js

jquery.mmenu.js

109 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

110 ms

custom.js

custom.js

110 ms

ga.js

ga.js

107 ms

app.js

app.js

158 ms

bg.png

bg.png

176 ms

innerbg.jpg

innerbg.jpg

89 ms

duskyfactorydirect.png

duskyfactorydirect.png

107 ms

sociallinks.png

sociallinks.png

89 ms

227V.jpg

227V.jpg

141 ms

banner-shadow.png

banner-shadow.png

88 ms

278T.jpg

278T.jpg

139 ms

252T_1.jpg

252T_1.jpg

156 ms

33TOWER_1.jpg

33TOWER_1.jpg

155 ms

IMG_4651CC.jpg

IMG_4651CC.jpg

157 ms

10.jpg

10.jpg

150 ms

4.jpg

4.jpg

167 ms

IMG_8488CC.jpg

IMG_8488CC.jpg

162 ms

700_58631_thumb.JPG

700_58631_thumb.JPG

169 ms

eventbg.jpg

eventbg.jpg

168 ms

event_fish.png

event_fish.png

169 ms

bg1.png

bg1.png

173 ms

bg2.png

bg2.png

178 ms

arrow-top.png

arrow-top.png

180 ms

lato-regular-webfont.woff

lato-regular-webfont.woff

179 ms

all.js

all.js

103 ms

widgets.js

widgets.js

100 ms

pinit.js

pinit.js

99 ms

lato-italic-webfont.woff

lato-italic-webfont.woff

102 ms

lato-bold-webfont.woff

lato-bold-webfont.woff

110 ms

lato-bolditalic-webfont.woff

lato-bolditalic-webfont.woff

109 ms

lato-light-webfont.woff

lato-light-webfont.woff

110 ms

lato-blackitalic-webfont.woff

lato-blackitalic-webfont.woff

110 ms

lato-black-webfont.woff

lato-black-webfont.woff

113 ms

__utm.gif

__utm.gif

38 ms

all.js

all.js

6 ms

pinit_main.js

pinit_main.js

10 ms

Accessibility Review

dusky.com accessibility score

73

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

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

dusky.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dusky.com SEO score

73

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dusky.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dusky.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

dusky.com

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