Tools & Wizards About Us
dapperdox.io screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    83% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

dapperdox.io

DapperDox – Beautiful, integrated, OpenAPI documentation

Page Load Speed

360 ms in total

First Response

24 ms

Resources Loaded

194 ms

Page Rendered

142 ms

dapperdox.io screenshot

About Website

Welcome to dapperdox.io homepage info - get ready to check Dapper Dox best content for Bulgaria right away, or after learning these important things about dapperdox.io

Build the ultimate developer experience - Create rich, browsable reference documentation and guides for your APIs

Visit dapperdox.io

Key Findings

We analyzed Dapperdox.io page load time and found that the first response time was 24 ms and then it took 336 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

dapperdox.io performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

dapperdox.io

24 ms

bootstrap.min.css

36 ms

font-awesome.min.css

18 ms

css

21 ms

css

41 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 45% of them (13 requests) were addressed to the original Dapperdox.io, 24% (7 requests) were made to Fonts.gstatic.com and 14% (4 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (73 ms) relates to the external source Maxcdn.bootstrapcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.9 kB (29%)

Content Size

633.0 kB

After Optimization

451.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Dapperdox.io main page is 633.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 566.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 9.1 kB

  • Original 12.3 kB
  • After minification 10.3 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 2.0 kB, which is 16% 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 9.1 kB or 74% of the original size.

Image Optimization

-31%

Potential reduce by 172.7 kB

  • Original 566.3 kB
  • After minification 393.5 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. Obviously, Dapper Dox needs image optimization as it can save up to 172.7 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 54 B

  • Original 54.5 kB
  • After minification 54.5 kB
  • After compression 54.4 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 13 (65%)

Requests Now

20

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dapperdox.io

dapperdox.io

24 ms

bootstrap.min.css

bootstrap.min.css

36 ms

font-awesome.min.css

font-awesome.min.css

18 ms

css

css

21 ms

css

css

41 ms

css

css

40 ms

home.css

home.css

18 ms

footer.css

footer.css

18 ms

animate.css

animate.css

33 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

26 ms

jquery.min.js

jquery.min.js

24 ms

bootstrap.min.js

bootstrap.min.js

73 ms

script.js

script.js

14 ms

jquery.corner.js

jquery.corner.js

29 ms

wow.min.js

wow.min.js

30 ms

status.gif

status.gif

67 ms

hexagon-colour4.jpg

hexagon-colour4.jpg

64 ms

dapperdox_logo_circle.svg

dapperdox_logo_circle.svg

59 ms

swagger.png

swagger.png

63 ms

dapperdoxScreenshotRequest.png

dapperdoxScreenshotRequest.png

59 ms

analytics.js

analytics.js

59 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

24 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

24 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

25 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

25 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

26 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

25 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

26 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

25 ms

Accessibility Review

dapperdox.io accessibility score

50

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

dapperdox.io best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

dapperdox.io SEO score

89

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dapperdox.io 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 Dapperdox.io 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

dapperdox.io

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