Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

deepin.org

deepin - deepin Linux Operating System

Page Load Speed

7.1 sec in total

First Response

518 ms

Resources Loaded

6.2 sec

Page Rendered

461 ms

deepin.org screenshot

About Website

Click here to check amazing Deepin content for China. Otherwise, check out these important facts you probably never knew about deepin.org

Provide a safe, reliable, beautiful and easy-to-use operating system to meet the different usage scenarios of global users and provide a better choose.

Visit deepin.org

Key Findings

We analyzed Deepin.org page load time and found that the first response time was 518 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

deepin.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value25.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.407

24/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

deepin.org

518 ms

214 ms

zh

268 ms

main.css

1314 ms

main.js

1340 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 91% of them (51 requests) were addressed to the original Deepin.org, 4% (2 requests) were made to Cdn-nu-common.uniontech.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Storage.deepin.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 482.1 kB (24%)

Content Size

2.0 MB

After Optimization

1.6 MB

In fact, the total size of Deepin.org main page is 2.0 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. 30% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 33.3 kB

  • Original 41.3 kB
  • After minification 39.9 kB
  • After compression 8.0 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 33.3 kB or 81% of the original size.

Image Optimization

-23%

Potential reduce by 448.8 kB

  • Original 1.9 MB
  • After minification 1.5 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, Deepin needs image optimization as it can save up to 448.8 kB or 23% 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 0 B

  • Original 54.3 kB
  • After minification 54.3 kB
  • After compression 54.3 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

-2%

Potential reduce by 20 B

  • Original 805 B
  • After minification 805 B
  • After compression 785 B

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. Deepin.org has all CSS files already compressed.

Requests Breakdown

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

Requests Now

53

After Optimization

48

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Deepin. 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

deepin.org accessibility score

90

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.

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

deepin.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

deepin.org SEO score

89

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

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

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Deepin.org can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Deepin.org 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 Deepin. 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: