Tools & Wizards About Us
d.io screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

d.io

Event Management App for Guest Lists, QR Check-In, Seating & Tables, Invitations & RSVPs, Ticketing & POS, with Full-Featured iPhone and iPad apps

Page Load Speed

1.6 sec in total

First Response

68 ms

Resources Loaded

875 ms

Page Rendered

691 ms

d.io screenshot

About Website

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

Diobox is the most advanced event platform app for guest lists, QR check-in, seating and table management, invitations and RSVPs, website publishing, ticketing and POS, with full-featured iPhone and i...

Visit d.io

Key Findings

We analyzed D.io page load time and found that the first response time was 68 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

d.io performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

d.io

68 ms

d.io

33 ms

home.d.io

399 ms

analytics.js

116 ms

fbevents.js

118 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original D.io, 77% (36 requests) were made to D33wubrfki0l68.cloudfront.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (399 ms) relates to the external source Home.d.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.4 kB (5%)

Content Size

1.1 MB

After Optimization

997.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of D.io main page is 1.1 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. 60% of websites need less resources to load. Images take 967.9 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 22.4 kB

  • Original 30.6 kB
  • After minification 30.6 kB
  • After compression 8.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 22.4 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 967.9 kB
  • After minification 967.9 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. D images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (9%)

Requests Now

43

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

d.io

d.io

68 ms

d.io

d.io

33 ms

home.d.io

home.d.io

399 ms

analytics.js

analytics.js

116 ms

fbevents.js

fbevents.js

118 ms

1133c4805f9c3692ea07cd8212d2c340fc508ba8.css

1133c4805f9c3692ea07cd8212d2c340fc508ba8.css

90 ms

css

css

137 ms

font-awesome.min.css

font-awesome.min.css

127 ms

8febaa4d01510c061af993d7c88205ebb0c756cc.js

8febaa4d01510c061af993d7c88205ebb0c756cc.js

111 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

266 ms

logo-colored.svg

logo-colored.svg

108 ms

logo.svg

logo.svg

111 ms

guests-title.svg

guests-title.svg

108 ms

check.svg

check.svg

109 ms

website.svg

website.svg

111 ms

ticketing.svg

ticketing.svg

113 ms

emails.svg

emails.svg

113 ms

tables-seating.svg

tables-seating.svg

115 ms

badges.svg

badges.svg

114 ms

download-app-store.svg

download-app-store.svg

117 ms

boy-scout.png

boy-scout.png

118 ms

dubri.png

dubri.png

121 ms

themet.png

themet.png

122 ms

tag-heuer.png

tag-heuer.png

123 ms

dashlane.png

dashlane.png

123 ms

ibm.png

ibm.png

125 ms

tiff.png

tiff.png

123 ms

america.png

america.png

125 ms

guests.png

guests.png

127 ms

qr-check.png

qr-check.png

126 ms

website.png

website.png

189 ms

ticketing-payments.png

ticketing-payments.png

158 ms

emails.png

emails.png

159 ms

tables-seating.png

tables-seating.png

126 ms

badge-printing.png

badge-printing.png

161 ms

download-app-store-black.svg

download-app-store-black.svg

159 ms

item-different-1.svg

item-different-1.svg

161 ms

item-different-2.svg

item-different-2.svg

177 ms

twitter.svg

twitter.svg

176 ms

facebook.svg

facebook.svg

185 ms

pinterest.svg

pinterest.svg

184 ms

instagram.svg

instagram.svg

186 ms

linked-in.svg

linked-in.svg

189 ms

medium.svg

medium.svg

188 ms

collect

collect

49 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

13 ms

js

js

66 ms

Accessibility Review

d.io accessibility score

82

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

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

Links do not have a discernible name

Best Practices

d.io best practices score

75

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

Browser errors were logged to the console

SEO Factors

d.io SEO score

81

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

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

d.io

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