Tools & Wizards About Us
duole.org screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

duole.org

多乐博客-Good Luck To You!

Page Load Speed

8.4 sec in total

First Response

61 ms

Resources Loaded

7.8 sec

Page Rendered

471 ms

duole.org screenshot

About Website

Welcome to duole.org homepage info - get ready to check Duole best content right away, or after learning these important things about duole.org

多乐博客提供各种资源共享，欢迎大家前来浏览和下载

Visit duole.org

Key Findings

We analyzed Duole.org page load time and found that the first response time was 61 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

duole.org performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

duole.org

61 ms

duole.org

622 ms

bootstrap.min.css

688 ms

font-awesome.min.css

481 ms

flexslider.css

484 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 91% of them (29 requests) were addressed to the original Duole.org, 6% (2 requests) were made to Hm.baidu.com and 3% (1 request) were made to Zz.bdstatic.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Duole.org.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 44.4 kB

  • Original 53.5 kB
  • After minification 53.5 kB
  • After compression 9.1 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 44.4 kB or 83% of the original size.

Image Optimization

-22%

Potential reduce by 298.2 kB

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

JavaScript Optimization

-10%

Potential reduce by 5.7 kB

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

-17%

Potential reduce by 6.0 kB

  • Original 35.4 kB
  • After minification 35.4 kB
  • After compression 29.3 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. Duole.org needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (41%)

Requests Now

29

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

duole.org

duole.org

61 ms

duole.org

duole.org

622 ms

bootstrap.min.css

bootstrap.min.css

688 ms

font-awesome.min.css

font-awesome.min.css

481 ms

flexslider.css

flexslider.css

484 ms

zan.css

zan.css

485 ms

common.js

common.js

491 ms

c_html_js_add.php

c_html_js_add.php

524 ms

bootstrap.min.js

bootstrap.min.js

939 ms

audio.min.js

audio.min.js

959 ms

zan.js

zan.js

957 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

685 ms

zblogphp.js

zblogphp.js

13 ms

logo.jpg

logo.jpg

470 ms

202403131647057448825.png

202403131647057448825.png

712 ms

202402241457495972123.png

202402241457495972123.png

3867 ms

202401091505045422732.png

202401091505045422732.png

902 ms

202208011702068584087.png

202208011702068584087.png

43 ms

202207052334382015340.png

202207052334382015340.png

3541 ms

202205201739205204429.png

202205201739205204429.png

44 ms

202111240844583656835.jpg

202111240844583656835.jpg

49 ms

20180108192355_21968.jpeg

20180108192355_21968.jpeg

68 ms

24.jpg

24.jpg

529 ms

201709091504955340570859.png

201709091504955340570859.png

5740 ms

0.png

0.png

539 ms

ghs.png

ghs.png

550 ms

ypy_logo6.png

ypy_logo6.png

563 ms

push.js

push.js

1137 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1667 ms

hm.js

hm.js

1181 ms

main.js

main.js

11 ms

hm.gif

hm.gif

307 ms

Accessibility Review

duole.org accessibility score

71

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.

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

Best Practices

duole.org 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

duole.org 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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duole.org 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 Duole.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

duole.org

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