Tools & Wizards About Us
dostor.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

dostor.com

存储在线-存储专业媒体

Page Load Speed

6.4 sec in total

First Response

736 ms

Resources Loaded

5.3 sec

Page Rendered

377 ms

dostor.com screenshot

About Website

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

中国领先的数据存储专业服务平台，提供海量的存储资讯，以及存储学院和中国存储峰会等智能数据领域的知识服务。

Visit dostor.com

Key Findings

We analyzed Dostor.com page load time and found that the first response time was 736 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

dostor.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

dostor.com

736 ms

www.dostor.com

725 ms

bootstrap.min.css

481 ms

font-awesome.min.css

722 ms

main.css

726 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 45% of them (19 requests) were addressed to the original Dostor.com, 48% (20 requests) were made to Pic.doit.com.cn and 5% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Pic.doit.com.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 291.1 kB (10%)

Content Size

3.0 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 32.0 kB

  • Original 41.4 kB
  • After minification 39.9 kB
  • After compression 9.4 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 32.0 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 109.1 kB

  • Original 2.7 MB
  • After minification 2.6 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. Dostor images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 138.9 kB

  • Original 208.1 kB
  • After minification 202.2 kB
  • After compression 69.1 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 138.9 kB or 67% of the original size.

CSS Optimization

-19%

Potential reduce by 11.1 kB

  • Original 59.3 kB
  • After minification 59.3 kB
  • After compression 48.2 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. Dostor.com needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (27%)

Requests Now

37

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dostor.com

dostor.com

736 ms

www.dostor.com

www.dostor.com

725 ms

bootstrap.min.css

bootstrap.min.css

481 ms

font-awesome.min.css

font-awesome.min.css

722 ms

main.css

main.css

726 ms

jquery.min.js

jquery.min.js

1202 ms

ad.js

ad.js

486 ms

bootstrap.min.js

bootstrap.min.js

732 ms

loader.js

loader.js

718 ms

wp-embed.min.js

wp-embed.min.js

733 ms

dostor.png

dostor.png

1096 ms

126.jpg

126.jpg

1430 ms

DOIT-880_454.jpg

DOIT-880_454.jpg

1837 ms

226.jpg

226.jpg

1558 ms

101.jpg

101.jpg

1527 ms

148.jpg

148.jpg

1568 ms

f58e54e5013dd6e86b6e64e434769678.jpg

f58e54e5013dd6e86b6e64e434769678.jpg

1250 ms

0fca1025fca796cd48b7a733510f359b.jpg

0fca1025fca796cd48b7a733510f359b.jpg

1342 ms

d7fcd68e0b16d6c0b52fdaa07a8bf49d.jpg

d7fcd68e0b16d6c0b52fdaa07a8bf49d.jpg

1247 ms

265aaecb7c1fe93842f493cfb5a2748a.jpg

265aaecb7c1fe93842f493cfb5a2748a.jpg

1108 ms

thumbnail.png

thumbnail.png

240 ms

ad.png

ad.png

1273 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

729 ms

fa-regular-400.woff

fa-regular-400.woff

247 ms

hm.js

hm.js

1240 ms

index.php

index.php

1238 ms

main.js

main.js

481 ms

ad.png

ad.png

279 ms

hammer.min.js

hammer.min.js

481 ms

ias.min.js

ias.min.js

250 ms

lazyload.min.js

lazyload.min.js

241 ms

signpop.js

signpop.js

248 ms

345-1.jpg

345-1.jpg

770 ms

1234.webp_.jpg

1234.webp_.jpg

904 ms

147.jpg

147.jpg

1034 ms

2225.jpg

2225.jpg

1068 ms

111-1.jpg

111-1.jpg

1121 ms

hm.gif

hm.gif

306 ms

6cfec7f5f5a87391fb4d455a8299a258.jpg

6cfec7f5f5a87391fb4d455a8299a258.jpg

1292 ms

3f9eee4675c169836d3ea0d950c46a23.png

3f9eee4675c169836d3ea0d950c46a23.png

919 ms

67c2ceae194429252111af0b2e60bc6d.jpg

67c2ceae194429252111af0b2e60bc6d.jpg

1104 ms

0d8af37437e166c36e8e8df2ef0bee9e.jpg

0d8af37437e166c36e8e8df2ef0bee9e.jpg

1095 ms

Accessibility Review

dostor.com accessibility score

63

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

dostor.com 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

High

Page has valid source maps

SEO Factors

dostor.com SEO score

82

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

High

Tap targets are not sized appropriately

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

dostor.com

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