Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 37

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

dionly.com

深圳市戴欧妮网络科技有限公司

Page Load Speed

74.4 sec in total

First Response

1.4 sec

Resources Loaded

72.4 sec

Page Rendered

571 ms

dionly.com screenshot

About Website

Visit dionly.com now to see the best up-to-date Dionly content for China and also check out these interesting facts you probably never knew about dionly.com

Zuva - Creative Personal Portfolio Html Template

Visit dionly.com

Key Findings

We analyzed Dionly.com page load time and found that the first response time was 1.4 sec and then it took 73 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 47 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

dionly.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

dionly.com

1376 ms

www.dionly.com

15567 ms

jquery.flexslider.css

2512 ms

jquery.slider.css

1046 ms

common.css

3189 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 84% of them (99 requests) were addressed to the original Dionly.com, 4% (5 requests) were made to Dl.ntalker.com and 2% (2 requests) were made to C.cnzz.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Dionly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 290.1 kB (21%)

Content Size

1.4 MB

After Optimization

1.1 MB

In fact, the total size of Dionly.com main page is 1.4 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. 20% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 40.6 kB

  • Original 51.3 kB
  • After minification 42.6 kB
  • After compression 10.7 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 8.7 kB, which is 17% 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 40.6 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 132.0 kB

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

JavaScript Optimization

-73%

Potential reduce by 84.8 kB

  • Original 116.8 kB
  • After minification 107.3 kB
  • After compression 32.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 84.8 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 32.7 kB

  • Original 39.4 kB
  • After minification 34.0 kB
  • After compression 6.6 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. Dionly.com needs all CSS files to be minified and compressed as it can save up to 32.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (39%)

Requests Now

67

After Optimization

41

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

Accessibility Review

dionly.com accessibility score

37

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

dionly.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dionly.com SEO score

83

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

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dionly.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Dionly.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

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