Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

dyte.in

Build powerful live experiences with Dyte's SDKs

Page Load Speed

6.6 sec in total

First Response

11 ms

Resources Loaded

3.3 sec

Page Rendered

3.2 sec

About Website

Click here to check amazing Dyte content for India. Otherwise, check out these important facts you probably never knew about dyte.in

Dyte provides everything you need to create immersive live experiences in a single scalable SDK.

Visit dyte.in

Key Findings

We analyzed Dyte.in page load time and found that the first response time was 11 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

dyte.in performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value20.9 s

1/100

10%

Network Requests Diagram

dyte.in

11 ms

dyte.io

1333 ms

dyte.webflow.de2c164ce.min.css

76 ms

uc.js

33 ms

jquery-3.5.1.min.dc5e7f18c8.js

29 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dyte.in, 90% (81 requests) were made to Assets-global.website-files.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Dyte.io.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

799.0 kB

In fact, the total size of Dyte.in 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 429.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 155.0 kB

  • Original 218.3 kB
  • After minification 217.4 kB
  • After compression 63.3 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 155.0 kB or 71% of the original size.

Image Optimization

-6%

Potential reduce by 26.7 kB

  • Original 429.5 kB
  • After minification 402.8 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. Dyte images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 87.9 kB

  • Original 353.0 kB
  • After minification 353.0 kB
  • After compression 265.2 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 87.9 kB or 25% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 67.7 kB
  • After minification 67.7 kB
  • After compression 67.7 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. Dyte.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (18%)

Requests Now

87

After Optimization

71

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

Accessibility Review

dyte.in accessibility score

89

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

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best Practices

dyte.in best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

dyte.in SEO score

93

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

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 Dyte.in 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 Dyte.in 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

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